web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

AX 2012 feature pack to AX 2012 R3 upgrade

(0) ShareShare
ReportReport
Posted on by 11,633

Hi,

I am in the process of doing upgrade from AX 2012 feature pack to AX 2012 R3. Following the steps mentioned in the below link and creating the development system for code upgrade:

https://technet.microsoft.com/en-us/library/jj733502.aspx

Under code upgrade checklist for in-place upgrade, there are steps to compile the application and full CIL before detecting code upgrade conflicts and resolving them. Now during compilation and CIL, I am getting errors in code which are related to SYS changes conflicting with VAR layer changes. I thought, I have to resolve these after detect code upgrade conflict step.

Can anyone please let me know if I need to ignore compile time errors at this stage and move to next step or am I missing something?

Thanks,

Baber.

*This post is locked for comments

I have the same question (0)
  • Tommy Skaue Profile Picture
    Moderator on at

    Does these conflicts cause compilation errors? And by compilation errors, I refer to X++ and metadata, not CIL.

    CIL can only be successfully generated if there are no application compilation issues.

  • syed baber Profile Picture
    11,633 on at

    Hi Tommy,

    Yes, as a result of full application compile, I am getting compile errors. For instance, I am getting errors in TradeTotals class, so I had to export the class, delete var layer changes and then import the changes back in to remove errors from that. But there are too many errors like this in other classes. So I am wondering when I can get to the detect code upgrade conflict step. Do I need to resolve all the conflicts before getting to that step?

    I am getting other errors like an enum element does not exist in DocumentStatus enum and it is being referred in X++ code. So, I had to do the same thing which is deleting the enum from var layer and then missing enum element appears on sys layer and lastly importing the var layer changes back from XPO.

    Thanks,

    Baber.

  • Verified answer
    Tommy Skaue Profile Picture
    Moderator on at

    In the code upgrade phase, you will "rinse and repeat" the code upgrade each layer at a time, until all layers are compiling successfully. And you will not be able to complete this phase without resolving and removing any compilation errors.

    If you have x++ references in VAR dependent on elements which no longer exist in SYS/SYP, then that code needs to be refactored/rewritten. If you have references in VAR that dependes on layers above VAR  (like CUS or USR), then that code does not belong in VAR to begin with. ;-)

    The more customizations, the more code upgrade you may have to work through. Good luck!

  • syed baber Profile Picture
    11,633 on at

    Hi Tommy,

    I tried to create the conflict project by clicking on detect code upgrade conflicts step and the system created the conflict project for var layer. So, now I can go and resolve the conflicts and compile the code again.

    Thanks for your help and responses related to this issue.

  • Tommy Skaue Profile Picture
    Moderator on at

    Glad I could help. Good luck with the continued upgrade. :-)

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans