Dynamics AX Blog - Posts from April 2019
Impact Analysis Tool fails when deleting the baseline databaseRecently when running the Impact Analysis Tool I had the problem that the installer seemed to have a problem deleting the baseline database and stopped/handled at this point. By the way, there was no entry in the event log. Interestingly, I also couldn't see the properties of the baseline database via SQL Server Management Studio, and the following error occurred:
So I have suspected that the database is broken in some way. Therefore I simply tried to re-initialize the baseline database via AXUTIL, which finally fixed my bug: axutil schema /DB:AX2012R3_Baseline /S:MyServerName After initializing the database I was able to start the Impact Analysis Tool without any problems. |
SysOperation-Framework: Usage data per MenuItemImagine you have a function build using the SysOperation framework that can be called at different places in the system, and you want to make sure that these calls do not share the same usage data. In such a case you could create two (or more) MenuItems and override the method lastValueDesignName() of the controller as follows. This will store separate usage data for each MenuItem. protected IdentifierName lastValueDesignName() { IdentifierName ret; ret = super(); if (this.parmArgs() && this.parmArgs().menuItemName()) { ret = this.parmArgs().menuItemName(); } return ret; } |
|
|
|
|
|
|
To pick the quantities already reserved from an sales order item by code, you can use codes such as the following: