A good and often used trick to use when hunting down bugs is putting a break point in the info class in the method add() and examining the call stack when an error is thrown causing the add method in the info class to be called for updating the infolog. However sometimes when you are debugging in Visual Studio the debugger will not load the symbols needed to debug in the info class. In the old days you had to resort to the very slow "Load all modules, unless excluded" under Debugging / Symbols / Automatic symbol loading preference, which would load symbols for ALL modules. A neat addition that Microsoft has added to the Dynamics 365 FO/SCM extension for Visual Studio (can't remember from what version at the moment), is that you can now debug with "Load only specified modules". So when you encouter that the debugger will not load symbols for the info class do this: 1. Choose Options in the 365 Visual Studio extension 2. Go to Dynamics 365 / Debugging 3. Put a ch
My thoughts on Dynamics AX application development. I have been working as a consultant with Microsoft ERP-technology since 1994. Currently I work at Optimate A/S. My main focus is customization and application development. This blog is merely my place to put stuff that I want to remember. If anybody can benefit from reading this, that's great :0). Feel free to use any code snippets posted - but accept that you do this at your own risk!!!