We have a duplication script takes a single record and duplicates it (plus all related records) around 50 to 100 times. We are using get(UUID) as the auto entered calculation of the pk.

 

Maybe once in one hundred times or less, MS reports a duplicate pk. When we check the database where the record was created (Hub), there is no duplicate key. The duplicate is only on the spoke database, ie in a record created completely by MS. (For this test we created all records on the Hub only).    So this means that MS is creating a record in the spoke database but using the wrong primary key for that record, presumably the pk from the record that was duplicated.

 

We observed that this only happens when the duplication script runs while MS is actively syncing.

 

So, we are wondering if it's possible that MS is somehow able to capture the primary key of the original record just as it is in the process of being duplicated? Is it possible that when FM makes a duplicate record, the record is published to the database first, then the auto enter pk calculation updates the record with the new pk , and in that millisecond window, MS has grabbed the old pk ? 

 

 

Turns out this was just in the field definitions.

UNCHECK : Do not replace existing value of field

UNCHECK : Prohibit modification of value during data entry

CHECK  : Data validation, unique values only, Validate always

UNCHECK : Data validation, allow user to override during data entry