Hello,
I'm doing developments in our AX 2012 environments in three different models in one layer. From time to time objects are moved at random to a different model on the same layer (e.g. I've added a new field X to table InventTable in model A. Without me touching neither the field nor the table field X suddenly is in model B). That either causes conflicts when importing the model in the Test-application, what is a nuisance especially because of the very "userfriendly" handling of these conflicts by the import-AXModel cmdlet. Today I had a variant I didn't have before. Several table fields were moved from model A to model B in the development application. As a result they were removed in the test application. Fortunately during the synchronization of the database there is a warning for the fields to be deleted, so I could stop this and then I can move the table fields to the right model in the development application. Has anyone encountered this problem also? If yes: what did you do? Open a call at MS? Of course I could open a call at MS, but as this happens at random and I don't know when/how it can't be reproduced so I'm afraid such a call would end without result.
Regards
Patrick