This could be caused by ID conflict between the 2 AX. So you must keep the ID sync between the 2 AX in order for the data to be sync. So one system must be the place for all the objects to be created, the other system must be the receiving one.
Thursday, October 1, 2015
Object ID conflict and data synchronization between AX databases
You must have noticed that when you have 2 AX environments, one for development and one for Live. If you have the issue where you make a whole DB copied from LIVE to DEV to get test data in the development environment, you notice that some of added custom fields do not get the data.
This could be caused by ID conflict between the 2 AX. So you must keep the ID sync between the 2 AX in order for the data to be sync. So one system must be the place for all the objects to be created, the other system must be the receiving one.
This could be caused by ID conflict between the 2 AX. So you must keep the ID sync between the 2 AX in order for the data to be sync. So one system must be the place for all the objects to be created, the other system must be the receiving one.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment