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) / Managing customizations
Microsoft Dynamics AX (Archived)

Managing customizations

(0) ShareShare
ReportReport
Posted on by Joanna Demetriou 355

Good afternoon all

Earlier versions of AX forced us to maintain in house a separate development AOS for each customer/project as customizations could not co-exist in the same installation (customizations of different customers affecting the same application elements).

Does AX 2012 offer any solutions to this problem? 
I cannot see how model architecture can be used to overcome this..

I would really appreciate your comments on this, and would like to hear how you are dealing with this within your development teams.

Thanks!

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Martin Dráb Profile Picture
    Martin Dráb 239,040 Most Valuable Professional on at

    No, it doesn't. You still have exactly one application in each environment.

    If you put modifications for multiple customers to the same application and later split it to parts belonging to individual customers, you wouldn't be able to test anything in such an environment, because you would have a mix of changes for completely different customers. And you would run into conflicting modifications very soon.

    Note that each model element can exist in a single model only (in each layer).

  • Joanna Demetriou Profile Picture
    Joanna Demetriou 355 on at

    Hi there Martin

    Thanks a lot for your prompt response.

    I assume this is how you also work then.

    How do you deal with situations where a bug is found in the core product (which is common for all customers)? 
    You just fix it in all development servers?

    This is the kind of thing which is very impractical and prone to errors - it's fairly easy to miss updating an instance and then you end up with different versions in no time..

  • Suggested answer
    Andrew Xu Profile Picture
    Andrew Xu 3,877 on at

    Hi Joanna,

    In my view, development AOS is just an AOS used for development purpose, nothing special compared to any regular customer AOS. As we won't expect to put customizations for different customers to one AOS, we have to create different environments for different customers' customizations. Otherwise, like Martin said 'you would run into conflicting modifications'.

  • Martin Dráb Profile Picture
    Martin Dráb 239,040 Most Valuable Professional on at

    If you have a core product, keep it in a lower layer than customer-specific changes. When you create a new version of your product, install it into customer-specific development environments and resolve possible conflicts. Then ship two models to your customers: one with the core product (the same for all customers, if they're all using the same version) and the model with customizations (unique for each customer).

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
Joris dG Profile Picture

Joris dG 5

#2
Andrew Jones a1x Profile Picture

Andrew Jones a1x 2

#3
GL-01081504-0 Profile Picture

GL-01081504-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans