web
You’re offline. This is a read only version of the page.
close
Skip to main content

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) / Import XPO to producti...
Microsoft Dynamics AX (Archived)

Import XPO to production environment conflict //down AOS intermittent

(0) ShareShare
ReportReport
Posted on by Community Member

Hi, Somebody can help us?

I have a customer, with 9 AOS to Production Enviroment, 2 AOS batch, 7 AOS to production, also have 1 TEST enviroment, and DEV enviroment.

We do Customization in DEV Envoroment, later test ok... import XPO to TEST Enviroment, Test again and when is ok, import XPO TEST Enviroment to Production Enviroment.

But, in many occasions, I have many problems,in this ocassion, the all AOS they are continually and intermittently fall

We synchronize, compile, Full Cil, etc...

Any idea?

I have and other question.... this issue could be generate by number secuence continuos in my base?

I appreciate your help !

*This post is locked for comments

I have the same question (0)
  • Mea_ Profile Picture
    Mea_ 60,286 on at

    First of all if you have 2 questions, create 2 threads for them!

    Regarding XPO deployment, that's the worst way to go. Instead of moving XPOs, model store is a recommended way.

    Do XPO from dev to test and then, export model store from test - > import it to production. All steps are well described in Microsoft white paper go.microsoft.com/fwlink also you can find various blogs with step by step descriptions.

    When you move model store, you do not need to compile anything, including CIL. You have to only do DB sync and deploy new reports if any. So in this way you want have any compile issues across multiple AOSes.

  • Anton Venter Profile Picture
    Anton Venter 20,678 Super User 2026 Season 1 on at

    I fully agree with Ievgen, never deploy xpo files to production. If you do, you will always get strange issue which can then only be solved by doing a full compile/ CIL compile so that the AOSes can synchronise the CIL properly. So, save yourself all that down time and trouble and release the model store to production. The model store can be imported into another database schema while the AOSes are running, during the release when the AOSes are down, you can simply apply the newest model store and delete the old one.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 16

#2
GiacomoRovai Profile Picture

GiacomoRovai 4

#3
Douglas Noel Profile Picture

Douglas Noel 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans