Microsoft Dynamics AX (Archived)

Move .xpo file to new Environmen

(0) Share

Report

Posted on by Community Member

Hi all friends, and Experts,

I have to two environment 1 for DEV, 1 for TEST.

Info DEV : Using SQL 2008R2.

Infor Test : Using SQL 2014

When my developer he finished coding. He want to export .xpo from DEV and import .xpo to Test. I don't know DEV in SQL 2008 can compatibility with SQL 2014 ??

Any comments for my before i process this Task ?

Thanks all friends, and Experts so much!!

*This post is locked for comments

I have the same question (0)

All responses (14)

Answers (0)

Suggested answer

syed baber 11,633 on at

Like (1)

Report

Hi Lee,

You can move X++ code from one environment to another and it does not depend upon SQL server versions unless you are using some functionality or feature specific to any version of SQL server. If the AOSes for both DEV and TEST are running fine, then the imported code will run without any issues if there are no compile errors.

Thanks,

Baber.

Was this reply helpful? Yes No
Suggested answer

Faisal Fareed 10,796 User Group Leader on at

Like (0)

Report

Hi Lee,

I wonder you are using AX 2012 then the best way to move your code across environment is through model deployment. Have a look on this white paper technet.microsoft.com/.../hh292604.aspx it gives you better way to handle your customization.

Yes, you can export and import .xop file from dev to test environment. You need to make sure on which layer you are connected on DEV environemt (it can be USR or CUS or VAR layer) if you have changes on multiple layers then you need to export you changes from every layer seperately and import them to TEST environment.

1. I would suggest you always create a model into your environemt

2. Make that model a default model and make all changes within that model

3. once you are done you can only export that model and import into your new environment

Last but important point you also need to take care of object IDs while exporting and importing .xpo files across environment.

Shoudl you have any confusion please do let me know

Was this reply helpful? Yes No
Suggested answer

Faisal Fareed 10,796 User Group Leader on at

Like (0)

Report

Also your customization does not depend on SQL server version unless your both DEV and TEST environments are working fine.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Lee,

As Faisal said, using Model deployment is the best practice for deploying AX2012 customization between environments. Moreover, model deployment is independent to SQL version. You can deploy model from SQL2008 environment to SQL2014 environment.

Was this reply helpful? Yes No
syed baber 11,633 on at

Like (1)

Report

Hi Lee,

Although model store deployment is a best practice, but be aware that model store deployment is going to move the whole code changes exist in the model store and not just the changes in your XPO.

Thanks,

Baber.

Was this reply helpful? Yes No
Suggested answer

Faisal Fareed 10,796 User Group Leader on at

Like (0)

Report

This is why I mentioned model deployment not MODEL STORE. These are two different things when comes to moving customization across envvironments. Mostly you use model stores when you want to changes from UAT to PROD as you compile application in UAT. This saves PROD downtime as model store is a compiled version you don't need to compile application again in PROD.

However, If you have small changes you should always use models so you can easily install/deploy models across any environment.

For more information about element IDs please have a look here blogs.msdn.com/.../the-solution-to-the-element-id-problem.aspx

Hope it clears the confusion why models are best approch then .xpo imports.

Was this reply helpful? Yes No
Suggested answer

Faisal Fareed 10,796 User Group Leader on at

Like (0)

Report

Here are more strict suggestions from MVPs on using .xpo file for code move.

community.dynamics.com/.../327091

Was this reply helpful? Yes No
syed baber 11,633 on at

Like (0)

Report

Hi Faisal,

But what happen if you have a shared development workspace where two or more developers are using the same environment to make changes in the code? Is every developer has to make a new model containing their code changes, so that they can export and import model ?

Thanks,

Baber.

Was this reply helpful? Yes No
Faisal Fareed 10,796 User Group Leader on at

Like (0)

Report

Hi Baber,

If two developers are working on same project then create one model and when they finish export that model only. In case they are working on different tasks in different areas then creating two models would be any issue providing you can export each model when you want to move to next environment.

You can also enable version controls and use TFS in case your environment is shared across multiple developers.

Mulitple developers working on same enviornment does not force that .xpo import/export would be better option. For example; two developers can be working on salesTable form for two different requirements then .xpo file will also not work.

Was this reply helpful? Yes No
syed baber 11,633 on at

Like (0)

Report

Hi Faisal,

Let say there are 10 developers working on 10 different requirements in a single development environment, then should they create 10 separate models for their code changes?

I didn't get you when you said in case two developers are working on salesTable form, XPO would not work. Why? I can easily merge my changes only in TEST when importing salesTable form or I misunderstood your question?

Thanks,

Baber.

Was this reply helpful? Yes No