Microsoft Dynamics AX (Archived)

Recreate development environment from stage

(0) Share

Report

Posted on by Hariharans87

Hi,

I am facing some issue in the development.

1. Some hotfixes are directly installed in stage environment

2. We are having different id conflict issue between stage and development

I need to make sure that development and stage having same version (no difference in objects)

Could you please guide me that how to recreate the development from stage?

Which id conflict option can i use for model store move if model store is a solution?

Thanks,

Hari

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (2)

Sort by

Verified answer

Martin Dráb 239,632 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

If you're talking about the application, copy the whole modelstore (to get all code) together with the business database (which should be compatible with the modelstore you're copying). Make sure that there is no development in progress (which would be lost).

Of course, if you want identical environments, you also need the same kernel (the same AOS and client executables, the same DLLs etc.).

Was this reply helpful? Yes No
Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report
Copy link

Link copied!

To do this the correct way:

1) Backup in progress code and setup from dev/staging/test.

2) Restore a fresh copy of the Production AX database in a fast single box temporary environment preferably with SSD RAID storage

3) Apply compression on the temporary box on data/indexes on the full database to save space

4) Take the compressed backup and restore it on your Test, Staging and Development boxes to make sure they are matching

5) Reimport in progress code and test setup to dev

When you promote code from development, have a build environment for each target (test/staging/prod). Only release code through a build AX AOS by the means of a full AXModelStore, which will ensure your developers are not throwing OriginIDs around left and right and applications will stay consistent. (Yes, that means no manual XPO import anywhere).

This way ID conflicts can only happen if you rename and/or delete objects ie. fields. I typically release the modelstore with -IDConflict:Overwrite -Details -Verbose flags, and if it shows any Metadata element conflicts, I run a script in AX that cleans up broken references in the SQLDictionary table.

Was this reply helpful? Yes No
Hariharans87 36 on at

Like (0)

Report
Copy link

Link copied!

If i do the stage business database restore in development, i need to work on the settings like reporting configuration, SSAS settings, etc. I don't have the list that what are the settings are there in AX.

Was this reply helpful? Yes No
Suggested answer

Mea_ 60,286 on at

Like (0)

Report
Copy link

Link copied!

Hi Hariharan S,

You can check this blog post from MS support blogs.msdn.microsoft.com/.../moving-between-microsoft-dynamics-ax-2012-environments

It has a document describing some steps you need to do after DB restore.

Was this reply helpful? Yes No
Verified answer

Hariharans87 36 on at

Like (0)

Report
Copy link

Link copied!

I thought database restore process will take more time. I expect only that objects should be same not considering data loss. So I did the model store move with idconflict overwrite option and resolved the id conflict issue by updating id value in SQLDictionary table. It is working fine for me.

Thanks all for your reply.

Was this reply helpful? Yes No