We have concurrent API calls to import salaryjournallines to Business Central in a performant way.

The "autosplitkey" is turned on.

But we have noticed a "Internal_EntityWithSameKeyExists" Error. ( in rare cases ).

""The record in table Salary Journal Line already exists. Identification fields and values: Journal Batch Name='SP-MA',Line No.='4140000' CorrelationId: fed691b4-fd8c-4013-bd39-2d73b3b31398."

After analyzing the case, I am pretty sure, that two customes tried to import a record a the same time to the same Journal Batch Name.

LineNo is auto-incremented. The number 4140000 was inserted already by an other customer.

Could you make "autosplitkey" threadsafe?

As a consequence I have to process in sequence, to avoid this error, which lowers our performance.

Best,

Michael

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-autosplitkey-property