Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
I am not sure about AX4, but in AX2009 ReleaseUpdateDB is in the sys layer. I had a similar error during my AX2009 to AX2012 upgrade because there were modifications to the releaseUpdateDB classes leftover from the AX3 to AX2009 upgrade. I removed the mods and reimported the XPO.
Yeah you are correct, ReleaseUpdateDB does exist in version 4 in the Sys layer. As instructed, I import the AX4 upgrade XPO from the 2012 R2 CD and then compile the AOT afterwards.
I have debugged the code and I cannot see the exact error - this is causing me major issues - can anyone else shed some light on this towards a solution?
Update: If I manually assign the enum value inside the parmScriptStage method - I can access the form options - the values are not being passed correctly into the parmScriptStage method, I appear to be able to work around this, however it must be Microsoft issue, I am amazed there are not more AX4 users that have experienced this in their upgrade attempt.
You don't mention if you are slipstreaming an update along with AX2012 R2. There is an upgradeax4.xpo file dated 10/31/2013 in the CU7 DatabaseUpgrade directory, so perhaps the problem was fixed with an update.
We had exactly the same error.
We solved it by running "Compile forward" on the ReleaseUpdateDB class.
Hope that helps!
Do Compile forward...
I can't see the option Compile forward in AX4.0. How to go about this???
Right click on the class and choose Add-Ins -> Compile Forward.
I'm getting the same error as mentioned above by Kauto. IS this something wrong with AX4.0 ? Any patches released for this issue?? or is it wrong with the UpgradeAX4.xpo file we are importing ???
I have tried compile forward on ReleaseupdateDB but no luck
Manish - this is not something that is wrong with the AX 4.0 upgrade process, it is simply a requirement that you must perform the Compile Forward option on the ReleaseUpdateDB class by choosing Add-Ins->Compile Forward and allowing the compile to finish. This is documented in the upgrade guide as being a requirement because the importing of the XPO in version AX 4.0 was a single pass compiler.
If you have performed the CompileForward on the ReleaseUpdateDB class (and make sure you chose that class and not one of the similarly named ones like I do by accident sometimes) then you should not be seeing the error that was listed at the beginning of this string. The only reason I can think of why you may be seeing this is if your AX 4.0 environment does not have the X++ development license enabled which would prevent the Compile Forward from working correctly. We would require a developer license to run through the upgrade processes.
If that doesn't address it, then I would recommend opening a support request for an engineer to look into the issue further.
Thanks a lot for your suggestion!!! It seems to be the issue with the developer license. Any other work around for this ?
For compile forward can I do - Syscompileroutput::CompileForward(Classname2Id('ReleaseUpdateDB'));