Model precedence / order within a package

(0) Share

Report

Posted on by ThomasWilke

766

Hi all,

can someone explain how the new AX (D365 for Operations) defines the order of models within a package. We have some 3rd party modules that still use overlayering to overlayer the application suite. They are located in VAR-Layer. But as I unserstood layers don't matter at all.

We try to customize them in another model which should be above them. So we created a new one in CUS layer. This seems to be underneath the VAR models ???

We get the following message when trying to customize: "Table XYZ is defined or customized in model 'Application Suite xyz' which has higher precedence than the model 'OurNewCusLayerModel' of the current project Project1. It cannot be customized in this project/model"

So we tried several other options creating a model in the same package in the USR or even in VAR layer is working fine.

Is there a possibility to define the precedence of models?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Martin Dráb 239,022 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

What's the layer of 'Application Suite xyz'?

Layers do matter; if it doesn't work in your case, it's a bug. Inside a single layer, the model ID is used for ordering (you can see it model descriptor files).

Was this reply helpful? Yes No
Gergely Balog on at

Like (0)

Report
Copy link

Link copied!

Did you add a model dependency from OurNewCusLayerModel to ApplicationSuite.XYZ?

If you don't tell D365O that your own model depends on the ApplicationSuite.XYZ objects existing, then it won't be aware of them.

You can do so in visual studio, choose the Dynamics 365 menu/Model Management/Update model parameters.

You can see current model dependencies under Model management/View all package dependencies, which will generate a nice tree for you from the models in the system.

Was this reply helpful? Yes No
ThomasWilke 766 on at

Like (0)

Report
Copy link

Link copied!

Hi Gregerly,

it's all overlayering of applicationSuite so there is no dependence. It is just the reference to the other models. But yes they are defined.

Hi Martin,

thanks for the fast reply. The scenario looks like this:

Class in ApplicationSuite (SYS)

Overlayered in ApplicationSuite.XYZ (VAR)

We want to overlayer in ApplicationSuite.OurModel (CUS)

It is working if our model is in USR, USP, VAR, VAP but not in CUS or CUP.

So yes, it looks like a bug.

Was this reply helpful? Yes No
Basheer17 2,720 on at

Like (0)

Report
Copy link

Link copied!

Does your NewCusLayerModel belongs to Applicate Suite package? You should create a new model in the same package in order make customizations.

Was this reply helpful? Yes No