Skip to main content

Mental note to self - disabling upgrade check list

Today I experienced that the Administration menu in AX 3.0 was very limited.
This was due to a previous upgrade of the Payroll module, resulting in the upgrade check list was to be run.
However the upgrade had been done in a dev/test- environment and been moved to a test/live environment.

Thus the need to complete the full upgrade check list was nonscence.
However we couldn't deactivate the upgrade check list via the menu, because the administration menu was limited to showing the Periodic menu node only.

However we could access the AOT :).

Mental note to self:
If you want to disable the upgrade check list but for some reasone you have no access to the Administration menu item Administration/Setup/System/Checklists/Prevent startup of list you can activate the Action menu item SysCheckList_InitNoUpdate. :)

Restart the AX client, and the Administration menu should be complete :).
That was what I experienced anyhow.

20\01\2010 - UPDATE
Well one more thing to mention about this little problem. Today we encountered the problem at a customer site, but with an additional twist. The twist being that we were not able to run the menuitem from the AOT, because of insufficient rights !!!

Ouch ... then what to do ?

Well I examined the class hierachy that among other things runs the upgrade check list and found the static method

SysChecklist::initNoUpdate

I copied the code in this method to a job (remembering the macro #SysCheckList in classdeclation of SysChecklist

static void Job10(Args _args)
{
#SysCheckList

ttsbegin;
SysSetupLog::saveEx(classstr(SysCheckListItem_Synchronize), ''); //Do not run Synchronize
SysSetupLog::saveEx(classstr(SysCheckListItem_SynchronizeUpgrade), ''); //same
SysSetupLog::saveEx(classstr(SysCheckList_Upgrade), #CheckListFinished); //Do not run upgrade
SysSetupLog::saveEx(classstr(SysCheckListItem_Compile), ''); //Do not run compile
SysSetupLog::saveEx(classstr(SysCheckList_Setup), #CheckListFinished); //Do not run setup
ttscommit;
}

Ran that and the check upgrade list didn't start up any more :)

Comments

Post a Comment

Popular posts from this blog

Suppressing the infolog

Supressing the infolog is often useful in D365FO when augmenting code. When augmenting code using COC (Chain Of Command), you can have new code run either before or after the code you are augmenting. This means that any infolog-messages that the standard application code does, will be shown to the user, even if your augmentation supports a scenario where there must be no infolog-messages. How do you avoid the standard application infolog-messages ? To the rescue comes temporary supression of the infolog. The suppression consists of: 1) Saving the current infologLevel 2) Setting the infologLevel to SysInfologLevel::None 3) Run your code 4) Restoring the saved infologLevel to the infolog For example a table could have a validatewrite-method that validates that you are only allowed to use 3 out of 6 options in an enum-field, and you need to allow for a fourth one. Table a - validateWrite method: boolean validateWrite() {     Switch (this.enumField)     {     ...
Post a Comment
Read more

Dynamics AX 2012 ValidTimeState tables and form changing view from current to all

Valid Time State tables are new i AX 2012 a gives the developer the possibility to easily create tables that hold e.g. current setup data for various purposes, and at the same time keeping a "history" of the changes of the data in the table. For more reading: http://msdn.microsoft.com/en-us/library/gg861781.aspx I was tasked with doing a setup table with rates for calculating Vendor Bonus and I chose to base this a valid time state table. The customer asked for a button on the form, where you maintain the vendor bonus calculation setup data, so you could toggle viewing "Current setup" or "All setup" records (changing the view from actual to all records and vice versa in the form). I found that you can not change the ValidTimeStateAutoQuery property on the form data source in a form at run-time. It simply does not change anything, so I came up with the following solution: A boolean class member in the classdeclation method of the form: boolean ...
Post a Comment
Read more

Subtle but important difference between _ds.executeQuery() and ds.Research()

This is actually an old entry. Been tumbling with a problem for the last few days. A form in our Dynamics AX module for Preventive Maintenance Control was not behaving. The form has "explicit" filter fields that the user can see without having to activate the form filter (CTRL+F3), for setting up filters most commonly used in an easy way. And this is working ok. However at this customer site, the form has been adjusted so that the user can have the form refreshed automatically periodically, and when the users at the customer site were making use of the "explicit" filter combined with the AX's normal filtering (CTRL+F3), the form simply threw away the normal form filtering. I discovered a subtle but very important difference between writing _ds.executeQuery(); (which was the way our code was doing it) and _ds.Research(); The difference is that _ds.Research() will retain the filter ranges in the forms query as they are right now. _ds.executeQuery() will NOT. It ...
Post a Comment
Read more