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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Migrate ALL CUS & ...
Microsoft Dynamics AX (Archived)

Migrate ALL CUS & USER layer changes from AX 2012 R2 CU7 to AX 2012 R3 CU11

(0) ShareShare
ReportReport
Posted on by Muneeb 895

Hi,

Currently we are working on AX 2012 R2 CU7. I have a below scenario,

We have got customizations present on 3 layers,

1. VAR (Done by the Vendor)

2. CUS (Done by In-House Team)

3. USR (Done by In-House Team)

Now we are planning to migrate from AX 2012 R2 CU7 to AX 2012 R3 CU11. Vendors will take care of VAR layer.

Now I have to move all the changes present in CUS & USR layer. Now the changes were done by myself + changes were also done by previous employees who are no more associate with us.

My query is, what is the BEST possible way to take care to move ALL the changes done so far on CUS & USR layer and migrate it to AX 2012 R3 CU11 environment as I am not sure what changes were done by the previous employees.

Would appreciate for some guidance.

Sincerely,

Muneeb

*This post is locked for comments

I have the same question (0)
  • Martin Dráb Profile Picture
    Martin Dráb 237,880 Most Valuable Professional on at

    First of all, download Cumulative Update 11 Installation Guide.

    Code upgrade is done as a part of the software update checklist, mentioned an page 12.

  • Muneeb Profile Picture
    Muneeb 895 on at

    Thank you Martin,

    I understand what you are saying and I went through the upgrade guide you shared. I assume what you shared is for Upgrading R3 to R3 CU11.

    Since I am new to this area, I just wanted to know like what will be the steps that would be repeated for each layer as part of Code Upgrade i.e. first for VAR followed by CUS and then followed by USR if any.

    - My resposibility would be for CUS & USR layer once vendor would be done for VAR layer,

    (A) would it be performed for code upgrade using XPO containing all the changes from LIVE for the corresponding layer?

    OR

    (B) from AX client, would it be performed using “Code upgrade checklist for in-place upgrade” - Code upgrade (layer specific, required for each customized layer)?

    Would appreciate for some guidance as I am new to this area.

    Sincerely,

    Muneeb

  • Martin Dráb Profile Picture
    Martin Dráb 237,880 Most Valuable Professional on at

    I'm sorry, but I understand what you're saying. If A means that you don't have any environment with the code for upgrade, and you don't use version control (!!!), then you can take code from LIVE. But never use .xpo files for such things; export the modelstore instead. Nevertheless this is not a part of upgrade; you shouldn't ever need to do this.

    Regarding B, yes, you upgrade a single layer at time.

  • Muneeb Profile Picture
    Muneeb 895 on at

    Hi Martin,

    Thank you for your response.

    Yes you are right the version control is NOT used for now.

    Just for more clarifications, we have already created a TEST environment which is replica of LIVE (AX 2012 R2 CU7). Now on that TEST environment, we would be starting with the code upgrade layer wise (Upgrade to AX 2012 R3 CU11)

    As per your response above, is it like I need to perform (B) as mentioned above?

    Would appreciate if you can help me with the steps.

    Sincerely,

    Muneeb

  • Martin Dráb Profile Picture
    Martin Dráb 237,880 Most Valuable Professional on at

    Yes, you need to upgrade your code using the process explained above.

    Which steps in the installation guide is clear to you?

  • Muneeb Profile Picture
    Muneeb 895 on at

    I was getting confused by the Installation Guide and hence I am here for some guidance so that I don't end up with some blunder.

    And here too I am getting confused for the simple Query I am asking!

    I should simply proceed with the “Code upgrade checklist for in-place upgrade” - Code upgrade (layer specific, required for each customized layer)? first for CUS layer and then for USR layer on my TEST Server.

    Can you please confirm so that I can proceed? OR correct me if I again misunderstood something.

    -Muneeb

  • Martin Dráb Profile Picture
    Martin Dráb 237,880 Most Valuable Professional on at

    Yes, you need to perform code upgrade.

    Yes, you'll use the checklist, as explained in the guide.

    Yes, it clearly says it's "required for each customized layer". You can't upgrade multiple layers at once, although you could merge code to a single layer before upgrading, to make the upgrade easier.

    Yes, you need to upgrade CUS layer before upgrading USR layer. You can't start upgrading USR while still having old code in CUS.

  • Muneeb Profile Picture
    Muneeb 895 on at

    Hi,

    I did additional research yesterday and followed the Installation Guide and below are the steps I have listed down based on my research along with few queries.

    I would appreciate if someone can comment or give suggestions if the below steps are in the right direction or if there is anything which i have understood wrongly and needs a correction.

    The TEST environment is the Exact Replica of LIVE. Once the vendor would be done with the VAR layer upgrade, I would be performing the below steps.

    Would appreciate if you can respond to 5 queries I have listed below.

    Please find the steps that I will perform in detail as below,

    1. Query-1: All the Customizations are stored in the default Model, so no need to push anything into CUS Model or USR Model as that’s the only MODEL present on CUS Layer or USR Model.

    2. The Actual Upgrade Steps in brief are as below,

    a. Run client in CUS layer.

    b. Delete USR Model

    c. Perform  all the steps from --> Code upgrade checklist for in-place upgrade” - Code upgrade (layer specific, required for each customized layer)

    d. Export the Upgraded CUS layer.

    Command: AxUtil export /model:""CUS Model"  /file:E:<modelfile>

    e. Restore the backup of the modelstore that was taken before starting of the Upgrading Activity.

    Command: AxUtil importstore /file:<modelstorefile> /idconflict:overwrite

    Query-2: Is the command correct? Just wanted to verify in order to avoid any blunders with IDs.

    f. Import VAR Model and then CUS Model before starting with the upgrade activity for USR layer. (Which of the following would suit in our scenario)

    Query-3: Which of the following command to be used for this step?

    Command: AxUtil import /file:<modelfile>

    OR

    AxUtil import /file:<modelfile> /replace:"Model Name"

    OR

    AxUtil import /file:<modelfile> /conflict:overwrite /replace:"Model Name"

    g. For last layer i.e. USR layer, we just need to perform step - ( c)

    3. Query-4: After Restoring backup ModelStore, when we will import the Upgraded Models over Customized Models, is there any precaution that we should take in order to avoid any issues for ID-Conflict or any other issues.

    4. Query-5: We don’t need to export the Project OR Model containing all the customizations from LIVE in order to import it on TEST.

    Would appreciate for some help.

    Sincerely,

    Muneeb

  • Muneeb Profile Picture
    Muneeb 895 on at

    Hi,

    Can someone please verify the steps and respond to the above queries if the sequence is fine as per my research.

    Thanks in advance.

    Sincerely,

    Muneeb

  • Martin Dráb Profile Picture
    Martin Dráb 237,880 Most Valuable Professional on at

    Looking at the first query, I can only say I don't understand what it means. Can you please elaborate it?

    For reference, here is the original formulation: All the Customizations are stored in the default Model, so no need to push anything into CUS Model or USR Model as that’s the only MODEL present on CUS Layer or USR Model.

    It seems that you're saying that you have all code in default models, but I have no idea why do you mention pushing something somewhere.

    I strongly recommend never using default models for any development - your models should have descriptive and unique names, a version etc. But it's off-topic - the upgrade process doesn't care about names of your models.

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

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