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

Indicating mandatory field in a dialog (RunBase) class.

A classical problem is indicating that a field is mandatory in a dialog, when the field is not bound to a datasource/field in a datasource. Normally fellow developers will tell you that, that is not possible. I found a way to do this. In your Runbase-based class you can implement the putToDialog-method e.g like this: protected void putToDialog() { super(); fieldMask.fieldControl().mandatory(true); } where fieldMask is a DialogField object in your dialog. This will make the field act like it was a mandatory field from a datasource in a form, showing a red-wavy line under the field, and requiring the field to have a value. Attention: Your class has to run on the client.If you set your class to run on the server, you get a run-time error, when the fieldMask.FieldControl()-call is made.
1 comment
Read more

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

ProcessGuide framework

I was tasked with developing a custom "process" for printing ad hoc labels in the Dynamics 365SCM WHS app. WHS process guide - development docs Reading the great articles from 1clickfactory (starting point  https://www.1clickfactory.com/blog/advanced-whs-mobile-device-development-part-1-process-guide-framework/) gives a good starting point. Especially Edgaras' tip on running  SysExtensionCache::clearAllScopes();  in a runnable class after introducing a new step/pagebuilder class combination  is VERY useful. And of course Microsoft's own documentation ( https://docs.microsoft.com/en-us/dynamics365/supply-chain/warehousing/process-guide-framework ) also helps. However, I wanted to chip in with a couple of things. Extending WHS base enums If you extend the WHSActivity, WHSWorkExecuteMode or WHSWorktransType base enums with new options it is a good idea to run a database synchronization when you are done with extending them. Otherwise you might be frustrated to find, th...
1 comment
Read more