Nov 9, 2009 - Monday, November 9, 2009. Ax does not support multiple, successive calls to assert in the same calling code. You either have to use the. There are several places within the application in which the use of Debug::assert validates access to code – an example is attached and the validations more or less indicates as follows. “you should not be here if the criteria is not met”. Theses kinds of errors can sometimes be experienced from within Dynamics Ax or least AX2009.
When printing a report, Ax sets the used language automatically based on the user's settings. The selection of available languages for the client interface depends on the installed language license keys.But sometimes, it may be necessary to change the default settings for reports. With reports needed for external use for example. Like invoices and packings slips you send to your customers. These documents require to be made up in the language of your customer. Ax is designed with this scenario in mind.
The language to use in the report can be set with following command:
element.design().languageID();
So for example:
element.design().languageID('en-us');
Place the code in the init method of your report, or in the fetch method.
You can use this in your own custom reports as well, with no limitation regarding the language license keys you bought. All you need are the appropriate label files. (Otherwise you get error messages like 'label @SYS123 not found in language xyz'.)
Got some time to spare? It can be fun to see how your documents look like in he - Hebrew, with its right to left printing.Issue:
When generating a YTD Balance sheet in Management Reporter (MR) for AX 2012, we were seeing an error being thrown and the report did not run.
The error: “The request for data from Microsoft Dynamics AX failed. Provider query name: LedgerMRBalanceRequestQueryBuilder.”
We checked the appropriate permissions to all folders that MR must access but we were still getting the issue.
The error was isolated to that one specific report as we could run other reports without issue.
Cause:
The report had a significant amount of data in it and it was causing the query to fail.
Workaround:
Breaking down the report into smaller sections allow the users to run the report without hitting this issue.
Resolution:
This was an MS product issue. Thankfully, the helpful staff in Fargo was able to resolve it and push out the resolution out in the new AX2012 MR provider Service pack. Download it from customersource/partnersource to resolve this issue. The name of the update is
'Microsoft Dynamics AX 2012 Provider for Service Pack 2'
Name of the file you will be downloading: AX2012Provider.zip
Hope this helps!!