CU7 CustTable Synchronization Error

This weekend I had to upgrade a client’s server to CU7 and many sync errors has shown up as expected. One of them has rendered CustTable useless and the reason is because there’s two versions of CustTable, one with eight new columns on AX and the old CustTable on MSSQL. When AX tries to replicate the changes on MSSQL it causes Index violation.

To fix it, do a manual backup of CustTable, synchronize the table, and then manually insert the data.
If you don’t know how to do it, follow the steps below.

1. Open Microsoft SQL Server Management Studio, select the business database (The database which contains all AX tables) and click on New Query. I’m using the demo data for my example, which means I will be using the MicrosoftDynamicsAX database.

2. Do a manual backup of CustTable using the following SQL syntax:

SELECT * INTO CUSTTABLE_BKP FROM CUSTTABLE

Press F5 to execute. This will create an exact copy of CustTable with all data included.

3. Delete the old CustTable:

DROP TABLE CUSTTABLE

4. On AX, synchronize the CustTable to duplicate it on MSSQL.

5. Check if the CustTable is back, if not, select the database and refresh it.

6. Time to put the data back to the new CustTable, since it has different column numbers we must specify which columns we want to insert.

CustTable has over 170+ columns, so it’s impossible to copy/paste it to my blog. Instead I will leave the link to download it.

http://goo.gl/qj9D3Z

IMPORTANT: Remember to change the database name at the beginning and at the end of the file to your Business Database name.

7. Now, synchronize the CustTable again and see if the error persists.