So you would like to create a custom lookup for the inventory table (Inventtable). As part of your design you include itemId and the display method ItemName. When you run the lookup you find the item name column is blank.
When dealing with performance, there is a new control under the AX query system called Query::Insert_Recordset. This allows mutliple records to be inserted into a table, with a single SQL call, in the same way the insert_recordset command works.
While this command is great for performance, there is a problem with the standard crosscompany control when using the query::Insert_recrodset comamnd. The crosscompany controls only build the extended select statement to include the comapny control (dataareaid) when the queryrun class is used. If since the query::insert_recordset does not use the the queryrun class, the crosscompany control does not work, and will not filter the data across companies based on any rules you apply. It will however extract data for all companies.
The only work around that I have found is to add the dataareaid into the query, selecting the companies you want to use, this then includes the company control into the SQL statement ensuring only the companies you are interested in are processed.
Recently encountered a problem with the payment journal payment report. When the report was run the report loading screen would be displayed and nothing else would happen.
When trying to deploy a service group or activate an AIF service you may receive the error: ‘The schema was not found for the document ‘AifEntityKeyPage’ in port XXXXX‘
After an in place upgrade from AX2012R2 to AX2012R3, I was receiving lots of error messages when CIL compiling or dealing with the AIF.
Cannot create temporrary file c:\program files (x86)\Microsoft Dynamics AX\60\Client\app\standard\temp\$tmp0003ffff.$$$. The disk may be full
There are times when you need to run the systems internal consistency check for an item to ensure the inventsum (Inventory levels) are correct. The below code will allow you to ensure the inventory levels are correct for an item.
A useful script to see which index the system thinks should be the clustered index, based on query history. This is just providing information as part of a performance review.