Skip to main content

Dynamics 365 for Finance and Operations - [ERROR] Cannot edit a record in Customer cross references (TCCustomerLevelXRef). An update conflict occurred due to another user process deleting the record or changing one or more fields in the record.

Written by Skylar Nguyen

Product: Dynamics 365 for Finance and Operations

Error: Cannot edit a record in Customer cross references (TCCustomerLevelXRef). An update conflict occurred due to another user process deleting the record or changing one or more fields in the record.


Issue: When changing the configuration for the Advance Ship Notice (AR 856) within the TrueCommerce Cross References (System/Company/Customer), you receive the following error: "Cannot edit a record in Customer cross references (TCCustomerLevelXRef). An update conflict occurred due to another user process deleting the record or changing one or more fields in the record."

Reason: The error occurs because these two tables are out of sync — specifically, a record exists in TCCustomerLevelXRef for a customer, but a corresponding record in TCShipmentCreationSettings does not. When the system tries to edit or act on the cross reference record and can't find its matching shipment settings record, it throws a conflict error, presenting it as if another process deleted or modified the record.

Solution - Verifying the records


To verify the records, you will want to use the TCTableBrowser and compare the two tables to ensure the amount of customer records match.

  • TCCustomerLevelXRef

  • TCShipmentCreationSettings

If there is not a record in the TCShipmentCreationSettings for a specific customer cross reference in the TCCustomerLevelXRef then that will need to be created, which should correct the error.

Solution - Creating the record in TCShipmentCreationSettings


To create the record, go to that specific customer cross reference – Outbound Tab – Advance Ship Notices – and if there are any options that are blank, they should be changed to “Default”. Then hit Save.

rev 08/28/2026

Did this answer your question?