Microsoft Dynamics 365 and Power Platform Library

This post outlines the steps how to debug an issue which is happening in non-development or non-production environments e.g. UAT environment. 1.     RDP to your environment where you want to debug the issue, with this example I am connecting to UAT (Sandbox).  2.     Connect to SQL server a.      Get the server name from LCS database accounts b.     Use .database.windows.net to connect to database 3.     Create a new SQL sign-in that the developer can use. This step lets the system administrator maintain the security of the sandbox environment. The developer will have access to one database for only a limited time. Use the following code to create the new SQL sign-in. CREATE USER devtempuser WITH PASSWORD = 'pass@word1' EXEC sp_addrolemember 'db_owner' , 'devtempuser' 4.     Stop following services in development box a.      ...

When you are developing X++ code for Dynamics AX over the time you will run into a situation where the below Tips & Tricks can make your debugging live easier. The informations are very rare to find at one place. Since I was also once in the situation needing to find them, I thought it maybe a good idea to collect the most useful ones I'm using day to day... The most oblivious one: Interrupting the code execution When you have written some code that is causing an endless loop (or a very long execution) and you want to know what code is currently keeping the client busy. The easiest way is pressing [Ctrl] + [Break] on the keyboard. This will stop the code execution and show up a message box: Are you sure that you want to cancel this operation? If you hold down the [Shift] button on the keyboard while you click at the No button of the message box, the AX Debugger will be launched exactly at the line of code that was about to be executed. From here ...