This appears to affect many-to-many relation tables when Entities share same EntityID and have a common association.
Simple example based on EntityTeam: if Account and Contact share the same Entity ID and are associated with the same Team then the import task will treat these as identical records and only one of these EntityTeam records will end up in the database:
EntityTeam.json:
[
{"id":"1","entityType":"Account","entityId":"10000000000000000","teamId":"20000000000000000"},
{"id":"2","entityType":"Contact","entityId":"10000000000000000","teamId":"20000000000000000"}
]
This appears to affect many-to-many relation tables when Entities share same EntityID and have a common association.
Simple example based on
EntityTeam: ifAccountandContactshare the same Entity ID and are associated with the same Team then the import task will treat these as identical records and only one of these EntityTeam records will end up in the database:EntityTeam.json:[ {"id":"1","entityType":"Account","entityId":"10000000000000000","teamId":"20000000000000000"}, {"id":"2","entityType":"Contact","entityId":"10000000000000000","teamId":"20000000000000000"} ]