Finding out which tables were updated by an operation in AX

Hi All,

At times when troubleshooting Microsoft Dynamics AX you need to know which tables were updated by a particular operation, for example after performing a posting. This could be if you want to be sure that all the right tables are updated correctly after an upgrade, if you have unexpected results on one customer/vendor etc or if you have made an update the system and you want to be sure that everything is ok.

Click Here to continue to the post.

Happy Daxing,
AX Dude

Comments

Using File path on a form getting Error in Axapta

Hi Folks, After a long time am coming back to posting few new things here for AX Developer... When we want to select the file path in form level. Normally what we will do create one EDT and extends with filepath (EDT), but that time when you are trying to select the path we will get error like stack-trace/Error message .Don’t worry there is no problem with your ax application. Simple we need to provide the method to the form like filepathLookUpTitle (). Below method we need to add it into form level methods, i.e. str filePathLookupTitle() { return "Select document folder"; } Thanks Happy Daxing....

Convert word Documents into PDF report [using X++ in Dynamics AX 2009]

Hi Friends, This is the way we can convert word format report into PDF in ax2009 static void dsiple_PDS(Args _args) { Args args; ReportRun rr; str reportName = "ReportName"; PurchRFQLine rfqLineTable; str myPath; str pdfFileName; int i; COM wordApplication; COM wordDocuments; COM wordDocument; COM wordRange; str a[]; str path; str pdfPath; str finalPath; int length; int minus; ; i = 1; myPath = winApi::getTempPath(); info(myPath); args = new Args(reportName); args.caller(rr); //rr =...

AIF (Endpoint) Error : The user is not authorized to perform this action.

"The user is not authorized to perform this action." We started getting this error message in our AX 2009 System, when ever we try to consume an XML file using an Endpoint thru a File System Channel to create a Sales Order. We did not made any code changes / setup changes, but all of the sudden started getting this error. Solutions : 1. Validate the "SourceEndpointUser". in inbound XML The User ID should be a valid user Id in DAX, in GNS Active Directory and the "\" should be back slash in the XML file or where you use this combination in entire process or setup. ex : Domain \ User Id. In our case when we had the above error, the SourceEndPointUser user id was deleted from the Active Directory in GNS, so we added it back to Active Directory then it solved the problem. NOTE : If nothing wrong with the User ID, try to add the user id in "Users" tab in Endpoints form for that End Point used by the process. 2. Verify th...

AX HELPDESK

Search This Blog