Hello AX community,
Im facing the issue that after the DataUpgrade (10.0.20 - 10.0.22 versions tested) via LCS, the Project module is not upgraded.
Everything else is.
This only started happening after we upgraded from 10.0.19. In 10.0.19 we did multiple DataUpgrades and the Project module was upgraded as expected.
I currently have a MS Ticket open, they are currenlty reproducing it with the data and code base I have.
Anyway, what i observed is, that in the source AX2012 the Project (I -III) config keys are all activated.
After the DataUpgrade took place, the config key 'Project' is deactivated. I dont know why.
I assume the ReleaseUpdateDB72_Project class is thus not executed (guarded by UpgradeScriptConfigKeyAttribute(configurationKeyStr(Project))).
I have made some customizations now to the ReleaseUpdate process, which now should ignore the if the Project config key is set or not (always returns true).
But that doesnt get me far, since the DB sync is done in kernel.
So my questions:
- Anyone have had a similiar issue?
- Is there any way I could activate the Config Key out of AX - thinking of a powershell script triggered via runbook, something like
Microsoft.Dynamics.AX.Deployment.Setup.exe --setupmode runstaticxppmethod --classname CustomConfigKeyHelper --methodname EnableProjConfigKey
Any help is much appreciated
Thanks!
