In one of the applications I found that the ID's are conflicting (data sync wouldnt work. It gave errors regarding the field already exists). Turned out that the field that existed had an ID in SQL dictionary which was of the new field in the model.
Only a model was imported, so the model store and database wasnt changed
The error was fixed by deleting the already existing field from the database, as there was no data in the table.
Environment: AX 2012 R2
Now, in another environment (AX 2012 R2 CU6), i found a similar issue while synchronizing, it was trying to rename a field to another which already existed. turns out there were ID issues again. the ID's in SQL dictionary were different to that in the model. Thankfully there were only about 7 - 8 such errors, and i manually fixed it in the database.
The thing that baffled me in this case was that all these fields belonged to a hotfix.
So my questions are:
What is the use of initialize model store?
Will it help if i have different ID's in the database vs the model?
Has anyone come across ID conflict issues in 2012 (We thought this was a thing of the past)