The main purpose of this question is to identify if there can be some concurrency issues resulting from how SysRowIDs are generated.
What we are doing:
We are running multiple concurrent vendor DMTs for a system migration.
What we are running up against:
When running the DMT we get ‘This is a duplicate entry of an existing record’, reviewing the records in the database it is not a duplicate and reprocessing the error works fine.
Presumed cause:
Concurrency issue with SysRowIDs causing a ‘duplicate entry’.
If it runs into a duplicate SysRowID, it would give you a different error. More likely is that it’s the incremental Vendor Number (Vendor.VendorNum). These are created when a new vendor is saved, and it’s just the next number available from the previously used vendor number. If you’re running multiple at the same time for the same company, that seems like it could definitely happen.