How to move AOS Test environment to Staging environment in ax 2012 r3

(0) Share

Report

Posted on by sivakumar moorthy

260

I am new in ax 2012 r3 developer I want to move all data as well as customize table and form from the test environment to staging environment, any one give some idea to how to move.

Regards

siva kumar

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

Suggested answer

Jonathan Halland 11,310 on at

Like (1)

Report

Hi Sivakumar. I would recommend speaking to the technical architect involved in your project to find out the exact process that they make use of for code and data migration between environments. From a purely technical side though you can transfer your code by either

1. XPOs (right click on your objects or projects and choose "Export"). - This would not be recommended between Test and Stage

2. Models - technet.microsoft.com/.../hh352314.aspx - This can move just the model that your code relates to. If you don't know about models yet, it is very important to become acquainted with what they are and how they are used.

3. Model Store - technet.microsoft.com/.../hh433530.aspx - This will move your entire code base from Test to Stage

Was this reply helpful? Yes No
Suggested answer

Rohin 4,624 on at

Like (1)

Report

I would go for Database Restore/import from test Environment to staging environment if you want to copy all data + customization .

Was this reply helpful? Yes No
sivakumar moorthy 260 on at

Like (0)

Report

Hi Visvash Walia

Thank for replying I need to export all customization table and form

Was this reply helpful? Yes No
Rohin 4,624 on at

Like (0)

Report

what about Data you mentioned in your 1st comment?

Was this reply helpful? Yes No
Suggested answer

Vilmos Kintera 46,149 on at

Like (1)

Report

I think you seriously need to learn about AOT Object and Origin IDs if you are asking about such task.

If the Staging AX environment is used as the source for Production code deployment, it is not advised to move all code together from Test with a modelstore/model, since it will have potentially different IDs from Production and will cause synchronization issues when that modelstore is getting deployed to Prod.

A Staging environment is initially created from Production to have matching IDs and avoid Data dictionary synchronization issues. After it is initially created, it must be under Version Control as well, connected to your Production TFS/VSTS branch. Code should come in with TFS/VSTS synchronization (that is essentially XPO import).

There should be no data in a staging environment, since that is only used for code build, and the created modelstore then could be deployed to a QA system to verify it with data.

Was this reply helpful? Yes No
Zain Bokhari 3,208 Moderator on at

Like (0)

Report

You should work on what Johnathan and Vilmos suggested.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Hi,

why you wanted to move data from test environment to staging environment? Is there any specific reason behind in that? please explore.

If you know import model store you can do this for your customization. and for data you should restore database.

if you wanted to do it simply, then you need to restore database.

Was this reply helpful? Yes No