web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

D365 Code upgrade - The Model specified on the project cannot be found

(0) ShareShare
ReportReport
Posted on by 70

I've seen an earlier thread discussing the same error, one suggesting that the absence of a model descriptor folder can be an issue, and the apparent MS issue thread, but I don't think I'm encountering either of the first two, so hope someone could please offer guidance.  Example of models that can't be found: (1) "ApplicationSuite.VAR Model" (2) "ApplicationFoundation.VAR Model".

Having gone through the AX 2012 > D365 code upgrade & configured my mappings, I'm at the point of attempting to load the CodeMergeSolution or UpgradedSolution VS projects from the Relase folder created in Azure DevOps.  When I get latest on the Metadata folder, the Visual Studio output window shows that it's getting objects such as AosService\PackagesLocalDirectory\ApplicationFoundation\ApplicationFoundation.VAR Model\AxTable\Delta\PrintMgmtReportFormat.xml  or AOSService\PackagesLocalDirectory\ApplicationSuite\ApplicationSuite.VAR Model\AxTable\Delta\VendTable.xml which suggests to me that the code upgrade has created "sub models" within the standard Application Suite or Application Foundation models.  Should I be trying to merge these change 'down' to the standard models somehow?  I'm pretty confident this isn't yet at the point of merging into the Main branch, though the instruction "If you are migrating from Dynamics AX 2012 R3 or earlier, you will be mapping to the metadata folder under the Main branch." within Configure VSO solution mapping section leaves an element of doubt.

I have the same question (0)
  • RichHims Profile Picture
    70 on at
    RE: D365 Code upgrade - The Model specified on the project cannot be found

    Thanks Nikolaos, Sukrut.  The disappointment of not being given more assistance by the code analysis/upgrade tools is somewhat offset by your reassurance that I'd correctly decided how much is down to the developer...  After my previous reply, I did find this blog series that discusses the conflict resolution option, but since that leads to overlaying, I think that's somewhat outdated.

  • Suggested answer
    Sukrut Parab Profile Picture
    71,699 Moderator on at
    RE: D365 Code upgrade - The Model specified on the project cannot be found

    Resolving conflicts  has to be done manually using  compare tool . No external tool is going to help you with that . For creating extensions and other development task you can quickly perform using below tool

    github.com/.../TRUDUtilsD365

  • nmaenpaa Profile Picture
    101,160 Moderator on at
    RE: D365 Code upgrade - The Model specified on the project cannot be found

    Hi Rich,

    unfortunately this is practically entirely manual work.

  • RichHims Profile Picture
    70 on at
    RE: D365 Code upgrade - The Model specified on the project cannot be found

    Thanks for correcting my wording Nikolaos: having done some extension development in a greenfield D365 instance, I could have phrased that better & appreciate your specifically pointing to extensions. I'd tried refreshing the models from the Dynamics 365Model management menu item, but was hitting the invalid reference/circular dependency issue others have discussed & resolved by editing the descriptor xml for the "submodels".  Mentioning that in my first post may have been helpful...

    I can now open my projects and am starting to work my way through conflicts & merges. Feel like I'm probably not making best use of the automated tools Microsoft provide, so if anyone has read any good material on resolving conflicts & merging code, I'd gladly accept any pointers.

  • Verified answer
    nmaenpaa Profile Picture
    101,160 Moderator on at
    RE: D365 Code upgrade - The Model specified on the project cannot be found

    First of all, Refresh models in Visual Studio. Then VS refreshes it's knowledge of your models, based on what was fetched from source control.

    And yes, the upgrade moved your overlayerings into submodels that are inside the standard packages.

    You can't change the standard modelsx so "down" is not the right direction or your code. Instead, reimplement all overlayerings (which is in Delta folders) into extensions. Then move these extensions to a new package / model. Eventually all your elements must be in your own packages, not in models inside standard packages such as ApplicationSuite.

  • Suggested answer
    Sukrut Parab Profile Picture
    71,699 Moderator on at
    RE: D365 Code upgrade - The Model specified on the project cannot be found

    The models you are referring are created because you have overlayering in those objects. When you run upgrade tool  from LCS after all migrations steps are done finally all code is brought at overlayered code  and different models are created within those packages , during model split.

    Your next task is to start your  work in your Main  branch to resolve the conflicts and removed code from these standard packages and move it as a extension. Once you are ready with all your code in your  own packages and application is error free , you can rename this branch to dev branch and  work on your branching strategy.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Andrés Arias – Community Spotlight

We are honored to recognize Andrés Arias as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Sohaib Cheema Profile Picture

Sohaib Cheema 745 User Group Leader

#2
Martin Dráb Profile Picture

Martin Dráb 597 Most Valuable Professional

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 580 Super User 2025 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans