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 :
Microsoft Dynamics AX (Archived)

Is it wrong to develop in system models (USR model, CUS model)?

(0) ShareShare
ReportReport
Posted on by

Hi guys,

In a TechNet article it says: "A default model owned by Microsoft exists in each layer. Default models cannot be modified."

But why actually you can't use it? I understand this model is generated by the system automatiocally. But you can still develop on this model. What is meant by "Default models cannot be modified"? What kind of issues you might experience if you use the default models like the USR model or CUS model?

Thanks,

Waldemar

*This post is locked for comments

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    304,272 Super User 2026 Season 1 on at

    Hi Waldemar,

    Can you share a link to this technet article? Perhaps the context might be relevant.

  • Suggested answer
    Martin Dráb Profile Picture
    239,223 Most Valuable Professional on at

    Nothing prevents you from developing in default models. But is your product really called something like "USR Model"? Wouldn't it be better if you actually use a proper name, owner and version number? What if everybody used the default model and you would like to install several such solutions into the same system (which is - or should be - one of benefits of using models)?

    I consider it bad practice.

  • Community Member Profile Picture
    on at

    Sure, it does make sense and would definitely use this as an argument against developing in the system models.

    But just for my understanding, are there any actual technical problems or limitations? Like for example, are you able to change the version number?

  • Community Member Profile Picture
    on at

    Hi André,

    Sure:

    technet.microsoft.com/.../hh335184.aspx

    It is a general article about models and layers in AX 2012.

  • André Arnaud de Calavon Profile Picture
    304,272 Super User 2026 Season 1 on at

    Hi Waldemar,

    I have read the contents around your mentioned phrase. I think Microsoft means that you cannot change the name of the models. But like Martin mentioned it is possible to create customizations in these models. I'm not sure if you can change he model properties like version number, I have never tried it.

  • Verified answer
    Tommy Skaue Profile Picture
    Microsoft Employee on at

    Given the fact that any element in any application layer MUST reside inside of a model, there HAS to be at least one model in each customized application layer. In other words, the minute you customize an element in CUS, it immediately needs to be within a specific model. So the system will automatically generate at least a "default" model named "CUS Model" for the CUS layer, and this model can't be changed in regards of name, version, publisher, and so on.

    Obviously, you can put changes in that model, but you cannot change its metainformation. You won't even see the "CUS Model" when listing out models from the Help dialog. :-)

    It is up to you if you want to organize your customizations inside a named model or use the one created by the system. So you can either put most, if not all, changes in one single model, or spread it over multiple models.

  • Jonathan  Halland Profile Picture
    11,310 on at

    I was curious, so I tried this Andre says and can confirm you cannot rename the system models or change the version numbers. AXUtil allows the request and says it was successful, but nothing actually happens.

  • Jonathan  Halland Profile Picture
    11,310 on at

    Apart from our products that we role out to various clients we make use of 3-4 models on the CUS layer per client. This allows us finer grained control over what we deploy and when to live.

    1. Reporting Model

    2. General Customisations

    3. Securities

    4. Workflow Model

  • Community Member Profile Picture
    on at

    Jonathan, but doesn't it increase the development (management) effort?

    (I ma talking about 3-4 models on CUS per client. Obviously you develop and test the "product-models" in an isolated environment I guess.)

    I mean, you have to make sure you develop the right objects in the right model all the time. How do you deal with the dependencies between models? I assume since you have this separation, you plan to deploy the models separately at some point. Do you have separate environments where you develop and test let's say 2. + 3. or 2 + 4. or 2. on it's own?

  • Community Member Profile Picture
    on at

    Tommy, thanks for the reply. This is actually what I needed to know: what are the actual limitations (like changing the version etc.)

    Well, I don't think there HAS to be a model. Ideally the system would simply prevent you from changing any objects as long as you are logged in to a "bad" model or even better not having a custom model at all.

    Small correction: I think by

    "and this layer can't be changed in regards of name, version, publisher, and so on"

    you mean

    "and this model can't be changed in regards of name, version, publisher, and so on"

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 26

#2
imran ul haq Profile Picture

imran ul haq 8

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 4 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans