Overview
When importing and deleting objects into M-Files via External connections, it may have more than one object with the same ID but only one remains undeleted.When a mapping has been set up using the ID, M-Files will always use the deleted object on the mapping instead of using the undeleted object with the same ID.
Solution
There are two workarounds:- First, when the duplicate ID is for a deleted object, you can destroy the deleted object. This fixes the issue.
- Second, if you don’t want to destroy, you can use an SQL stored procedure that adds unique External IDs to the objects in question. Then map the External ID to the Object in the External Connection.
