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)

Cannot Duplicate UAT to Production without copying UAT transaction data and reset number sequence on same server..

(0) ShareShare
ReportReport
Posted on by


Seeking references or configuration help for making 2 environments on 1 machine. uat and production.
I have searched technet/ blogs / dlp but could not find even a close solution where we could work up.We r using AX R3 CU9. 

Issue 1. Uat and production. Everything has been configed in uat and test runs done and all master exist. Now when we try to copy to prod and delete the transaction and reset the number sequence . there are only errors even the num seq is already reset back to 1. But when a new doc is created it starts running from the previous no. 47. of the existing UAT, eventhough production has been reset to 1. Be it PO or SO etc. There is even some issues that we cannot make clean data the system keeps on remembering values from UAT eventhough we re at production.  We tried with delete db and make new prod but still somehow its not working.

Does ax have some utility to help on this. We cannot always request customer side to provide 2 physical servers to cater to diff env.

The current alternative method that we have devised is when create UAT create CLEAN UAT ie no transaction and then duplicate to prod. And evertime there is some change in UAT manually enter configure the same in PRODUCTION. This is too much duplication of effort and time consuming. 


Issue 2. MR. reporter the same if we create a new env on same physical server the system keeps on referring to the legal entity that exists in prev env. Eventhough new entity is created and configed.
This is creating a lot of unnecessary duplication of effort and time when team should be focusing on other imp tasks to go live.

I am sure that ax must be having some workarounds for coexistence bc any new mods will take place in uat and moved to prod.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    on at

    Installing AX UAT and Prod on 1 machine is possible. But not preferable. I'd rather install DEV and UAT at 1 machine and have Prod on it's own machine.

    You should install :

    SQL Server.

    2 AOS's on the same machine and give them different names and different service accounts to run the services, and create databases with different names as well.

    Check if the correct service account has access to the right database.

    After restore of database check all server related parameters: Server configuration, cluster configuration, SSRS, SSAS, SharePoint etc.

    Normal procedure would be replicating the parameters by hand from UAT to Prod to insure you only get the parameters you need in Prod not the ones you just tested in UAT.

  • Suggested answer
    Denis Macchinetti Profile Picture
    16,444 on at

    Hi

    About Data Migration, take a look at technet.microsoft.com/.../aa548629.aspx

    In order to manage the Setup I suggest to create a Configuration Environment with only Setup and so without Transactions.

    Now, starting from this, you can create Others Envs like Production.

    After Live, the configuration in the Production env will be managed manually or you could use MDM, technet.microsoft.com/.../dn720451.aspx

    Finally, for update the Non production Envs, you can use the Test Data Transfer Tool that is very Fast.

  • Community Member Profile Picture
    on at

    Thanks Denis,

        I will follow the links, the approach to create a fresh UAT and duplicate to PROD we are following that, but in large omnichannel implementations UAT is quite extended and we have some tunings to parameters and other masters. Therefore we were seeking a more effective approach to do the same duplication but without the necessity to reconfig There were ofcourse issues with Management reporter 2 instance on same machine. Somehow MR always runs with the orginal config eventhough seperate configs have been made. 

    If you do have some further inputs then please do forward. 

  • Community Member Profile Picture
    on at

    I do understand the approach of having UAT and prod on seperate servers, however for some of our medium target clients there is only 1 server and after live on prod there are phase 2 modifications which are also taken in UAT. In this case of phase 2 following LIVE it is the key approach to manually config to avoid taking unwanted, that we have been following.  Will have the tech team to further double check the settings as per your feedback, as normally this is part of their regular routine on deployments.

    Best Regards,

    Deepesh J.

    Senior Proj. Mgr.

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