You’re offline. This is a read only version of the page.
641
Has anyone encountered this issue and how did you handle it?
I am upgrading from AX 2012 FPK + CU5 to AX 2012 R3 Cu12. I see the "Preserve legacy IDs" as one of the steps in my code in-place checklist.
According to AX 2012 upgrade install guide (pg 57 & 58) and this https://technet.microsoft.com/en-us/library/jj733496.aspx , this steps is for when you are upgrading for AX 2009 or AX 4.0.
Why am I seeing this in the code in-place checklist?
I marked it as complete. Hope this is the correct thing to do!
Thanks,
Jackie
*This post is locked for comments
I have the same question (0)
It is always there as a task for in-place upgrades independent from your source environments' version.
I did run the steps outlined for Customers to preserve IDs in the documentation anyway for our code upgrade from AX 2012 RTM CU7 to R3 CU11, but previously we were upgrading from earlier versions of AX from 3.0, 4.0 and 2009 in the TAP program, so I wanted my IDs to be in order. Skipping the step will most likely not cause any harm to your environment, however, it does not hurt to run it just in case. To be sure, you could try to duplicate your _model DB, and compare it post-execution to see if there is any noticable difference on tables/fields/objects, which do use legacy IDs.
Share
Report
All responses (
Answers (
