While performing Workflow Infrastructure Configuration, you might face the following exception: Exception: The user account entered for the workflow execution account is not valid. Confirm that the account exists and is enabled. Resolution: Please perform the following steps to resolve the issue: 1. Click System administration > Setup > System > System service accounts. 2. Specify […]
Open command prompt and run the following command to get the SID of the current logged-in user:
Recently I came across the following exception while executing a batch job via a menu item. The batch job has been written using the SysOperation Framework. Exception: Resolution: To fix this, please follow the steps below: Create Code Permission Link it with the menu item Code Permission: Create a new code permission under AOT >
All the batch jobs and service operations now run in the managed code (IL) and therefore breakpoints set in x++ do not get hit as expected! Instead you should be setting breakpoints in the IL code in Visual Studio. Here are the steps you would be following to do so: 1. Open Visual Studio as
If you are working on objects (Tables or Classes) you haven’t designed then it is quite possible you could have an insight about these objects by reverse engineering them to either data model or object model. I came to know about an excellent reverse engineering tool in AX 2012, that’s why sharing here for others.
If you are not hitting the breakpoints you set in X++ code as expected then make sure that your code isn’t executed by the SysOperation Framework (formerly known as Business Operations Framework – BOF). If this is the case then you can force the AOS to debug your code in Dynamics AX Debugger by CLEARING