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) / Modelstore Release
Microsoft Dynamics AX (Archived)

Modelstore Release

(0) ShareShare
ReportReport
Posted on by LeeJames

Good Morning I have a question I have been using Microsoft Dynamics AX 2012R3 for just a little over 1 year now we have been implementing it as part of a 3 phased project the 1st project has only affected the Manufacturing area and the 2nd part will be the majority of the other business areas for example Finance, Merchandising, CallCentre etc

the question I have is that we have released 4 model store releases since we went live in November 2017 and to apply a model store to Production we need to have all users out of the AX application to do this sometimes up to 4 hours and testing- now although very challenging to do this when your you work for a business that is a 24 operation we found the time

my concern is when the rest of the business comes online with AX2012 - do we really have to have everyone out to apply a model store as I am thinking this is going to cause us significant disruption while this takes place making it almost impossible to implement change

obviously I understand the risks with XPOs and understand why we wouldn't  choose and XPO release over a Model store - I am just wondering if there's anyway to deploy change without taking everyone out the system for so long

*This post is locked for comments

  • LeeJames Profile Picture
    LeeJames on at
    RE: Modelstore Release

    Thank you for all your replies I will look at this - just tpo be clear we never develop directly in out production environment we have a development environment for this and then we promote to a UAT Environment it here where the Model store is created and then again promoted to another Business testing Environment before promoting to live - it just it appear that the promoting to live can take up to 4 hours so we have been told meaning that we could be down for that time - plus longer if we do some initial testing in production.

    I am keen to try an reduce this time so just understanding the best ways -

    thank you all

  • nmaenpaa Profile Picture
    nmaenpaa 101,156 Moderator on at
    RE: Modelstore Release

    Your process is basically developing directly in production (separately on each running node) and hoping that it works. I highly discourage such process and eventually it will lead to issues.

    If you have a 24/7 business you have to accept that you can't update the system whenever you want. But with the modelstore delivery you should be able to squeeze the downtime to 30-60 min and maybe you can find / agree on such usage breaks every now and then.

  • Community Member Profile Picture
    Community Member on at
    RE: Modelstore Release

    Not a supported and recommended approach (ideally without any data dictionary changes in the XPO)

    1. On 1st AOS, drain users from AOS, import XPO, compile, incremental CIL. Accepting new users

    2. On 2nd AOS drain users from AOS ...

    The key assumption - no data synchronization required, no compilation forward required, only for simple changes (one or two lines code updates).

  • Suggested answer
    nmaenpaa Profile Picture
    nmaenpaa 101,156 Moderator on at
    RE: Modelstore Release

    What is your process for xpo import if you say it's faster than modelstore deployment?

    Modelstore deployment is the fastest and safest way of importing code to production, since you don't need to do x++ compile or CIL generation at all (it was done already in your staging environment). 

    If you import the modelstore to a temporary schema, the system can run during the import process, saving you about 30 minutes of downtime. Then the only complete downtime would be the time that it takes to do start first AOS and do database synchronization. After the db sync you can start the other AOS services.

    Please see the product documentation to see how you can import the modelstore to a temporary schema: docs.microsoft.com/.../how-to-export-and-import-a-model-store

  • Martin Dráb Profile Picture
    Martin Dráb 231,723 Most Valuable Professional on at
    RE: Modelstore Release

    Importing XPOs takes actually much more time, because you must compile X++ and generate CIL.

  • Vasudev Kochuveettil Profile Picture
    Vasudev Kochuveettil 310 on at
    RE: Microsoft AX 2012, Modelstore Release

    yes we need to stop the AX AOS Services and this is needed to make sure when modelstore is pushed into DB, latest/newer code is properly moved without any hiccups, else you will see strange issues coming up.

    to reduce the downtime is you have the temp db schema created when ever modelstore is deployed. so actually without taking down the aos services you can complete all this steps and then stop ax aos service and push the temp schema to database in matter of seconds.

    actual time is taken at DB Sync.

    this will reduce the time for outage.

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

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,850 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,723 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans