![]() This process compromised the integrity of the other person's synchronization of the system. Imagine if one person was doing a full synchronization and another user came in during that process, added a table and some EDTs and was able to sync them and move on. This is all by design and it makes total sense. The question 'Is this a bug? Why does this happen' is a fair one. People can still compile code and other objects but doing actions like creating a table or changing an EDT would result in a total lock up of the system. From what I could see, when a synchronization occurs, the entire database will lock up from any table Id or sync related problems. One of the developers in the system was doing an unintentional full database sync. Issue was with the database doing an entire system synchronization. The clients would crash and all sorts of nasty things. We had an issue with AX 2012 R2 freezing up and stopping anyone from doing anything in the system. There can be some issues with people modifying the same base objects of course but when doing training and creating new processes, everything should be good. I've had up to ten people in a single instance creating all sorts of stuff. Set the switchValue node value to 'All' in the '' file in the C:\Program Files (x86)\Microsoft Dynamics AX\60\Retail Transaction Service folder.ĪX allows multiple developers to exist in an AX environment without any issues. I've highlighted the change that needs to be set below. Step 1 - Set the RetailTransactionService XML config file to allow tracing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |