You’re offline. This is a read only version of the page.
Hello guys,
my project has model that extends Application Suite package, but in the same solution I have to customize different package, so I created a project with different model that extends that Directory package. The problem is that this second project has table (DirPerson) that references to other (CustomMade) table, but DirPerson cannot see it as I build the solution and throws an error. Do I have to deploy it in someway or what? Thanks in advance for your ideas.
*This post is locked for comments
Thank you for the explanation. Talking about creating a new model inside a package as "extending a package" is confusing, because that's a customization - an extension is the other approach (creating a separate package and create a reference).
So you have Model1 inside Application Suite package and Model2 inside Directory package. Now you want refer from the Directory package to a table defined in Application Suite package.
If you look at references between those packages, you'll find that Application Suite depends on Directory, therefore Application Suite can use all objects from Directory, but not the other way around. The Directory packages knows nothing about existence of Application Suite and can't access anything defined there.
You can't solve it by changing references between packages. Now they're logically correct, so there is nothing to fix, and if VS allowed you to add the circular reference, the solution couldn't ever be built (compiling Directory would require compiling Application Suite first, which would require compiling Directory first, which would require compiling Application Suite...).
What you have to fix is the flaw in your architecture. If you need accessing objects from the Application Suite package, you can't ever do it from the Directory package. Move your code to a custom package referring to Application Suite or (if necessary) to Application Suite package itself.
Martin, yes these are customizations, I just don't know how its properly called, the first model is in Application Suite package
:) but I have already referenced Directory from Application Suite model. And both models are the same layer VAR if it matters.
I have just noticed that in Directory package model there is even no reference to Application Suite package available
Reason could be you are trying to access model elements from higher package in model present in lower package.
Please refer ax.help.dynamics.com/.../understanding-the-model-split
community.dynamics.com/.../ax-7-breaking-dependencies-part-1
I have a solution with 2 projects: first one uses a model that extends Application Suite package, the other project uses a model that extends Directory package.
The model name in your last reply suggests that it's a customization. I'll call it Model2 - it's inside the Directory package, correct?
What about your first model?
I'm struggling to understand how your packages look like. When you say that you extended a package because you need a customization, it sounds like a contradiction to me.
Do you have separate packages with references to standard packages (extensions) or did you put your models to existing packages (customization)?
Path: [AxEdtInt64/ASC_HcmEmployeePFA_DOS/ReferenceTable]:Table 'ASC_EmployeesPFA_DOS' does not exist. HDD_FieldsMappingProjectsDir_DOS (VAR) [Overlaying Package HRMFDD Directory]
It seems that it tries to look only in the Directory model, doesn't find it and throws it.
#1
Mohamed Amine Mahmoudi
100
Super User 2025 Season 1
#2
Community Member
48
#3
shanawaz davood basha
6
Share
Report
All responses (
Answers (
