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

(0) Share

Report

Posted on by Community Member

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)

All responses (12)

Answers (1)

Community Member on at

Like (0)

Report

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

Jonathan, this is a good idea. I would like to share the thoughts about this too. I have opened a new question to avoid off-topic: community.dynamics.com/.../140382.aspx

I think this question is solved.

Was this reply helpful? Yes No
Jonathan Halland 11,310 on at

Like (0)

Report

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

Hi Waldemar.

There are some inter-dependencies between the models and these either just need to be considered or may need to be tested as you suggest.

E.G. Our Securities model is mostly a standalone model and can be frequently deployed on its own as we add and adjust roles.

It does contain some references to menu-items in the Customisations model. This just means that we need to be aware if a new menu-item has been added to the customisations model and the securities model has been adjusted to handle this menuitem we will need to deploy both models. However if only the securities model has changed then we can deploy it on its own. Also if we just change some code in the customisations model we can deploy it without having to redeploy everything else.

It does have a certain management effort associated with it, however so does deploying code via other means such as XPOs. One can't deploy a role via XPO if it is dependant on something that is not in the XPO.

I'd be very interested to get some of the other guys in this conversation perspective on this.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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

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"

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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

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?

Was this reply helpful? Yes No
Jonathan Halland 11,310 on at

Like (0)

Report

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

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

Was this reply helpful? Yes No
Jonathan Halland 11,310 on at

Like (1)

Report

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

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.

Was this reply helpful? Yes No
Verified answer

Tommy Skaue Moderator on at

Like (2)

Report

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

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.

Was this reply helpful? Yes No
André Arnaud de Cal... 299,024 Super User 2025 Season 2 on at

Like (1)

Report

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

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.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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

Hi André,

Sure:

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

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

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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

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?

Was this reply helpful? Yes No