From the Microsoft Dynamics 365/AX Blogs: Debugging; Financial dimensions; Test automation code; Translation

This week on the 365/AX blog roundup:

• Debug a Dynamics 365 for Finance and Operations on-premises instance without Visual Studio
• Import financials dimensions set by default on the main accounts via add-in Office Excel in Dynamics for Finance & Operations
• Performance improvements that may affect test automation code
• Trade documents translation in foreign language

Debug a Dynamics 365 for Finance and Operations on-premises instance without Visual Studio

On the Microsoft Dynamics AX Solution Architecture team blog, Tariq Bell explained how to debug an error in Microsoft Dynamics 365 for Finance and Operation on-premises directly in the on-premises environment, where Visual Studio isn't available, by using a free tool called WinDbg.

This approach gives a fast way to catch exceptions occurring in the environment and identify the call stack, more detailed error message (for example to see inner exceptions) and to see values for running variables at the time of the exception.

Bell said that in addition to debugging the application object server itself, you can also use this approach for any component in Windows running a .NET-type code. For instance, if SSRS was throwing an exception, you could do the same thing to debug SSRS itself.

However, this tool does not provide a full X++ debugging experience, as you would normally have using Visual Studio with the Dynamics dev tools installed, according to Bell.

You can read about using WinDbg here.

Import financials dimensions set by default on the main accounts via add-in Office Excel in Dynamics for Finance & Operations

On the D365 Tour blog, Catherine Guibert looked into the ...