Microsoft Dynamics AX (Archived)

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

(0) Share

Report

Posted on by Martín Flores

Hi guys!

I'm trying to upgrade a custom solution from AX 2012 R3 CU10 to AX 7

I've already done the code upgrade process on LCS and the checked in the code to a VSTS project.

I'm using a local VM as development enviroment.

I already mapped the metadata folders and refreshed the models.

I can't open any of the vs solutions I downloaded. It raises an error saying:

"One or more projects in the solution were not loaded correctly. Please see the Output Windows for details"

In the output windows there are multiple messages saying:

The model <ModelName> specified on the project cannot be found.

I don't know what is missing, as a I said I refreshed the models after getting thr files from VSTS.

Any ideas?

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (1)

Martin Dráb 235,876 Most Valuable Professional on at

Like (0)

Report

RE: AX7 Code upgrade - The Model specified on the project cannot be found

It's all covered in documentation: Configure the Azure DevOps mapping during code migration.

Was this reply helpful? Yes No
Ajit Kumar Singh on at

Like (0)

Report

RE: AX7 Code upgrade - The Model specified on the project cannot be found

Hi Martin,

Can you please tell me that in which folder you had done mapping and please share screen shots as i am facing same issue.

Thanks

Was this reply helpful? Yes No
Upgrade from AX 3.0... 40 on at

Like (0)

Report

RE: AX7 Code upgrade - The Model specified on the project cannot be found

Hi Martin,

I am facing the same issue while trying to open solution files in visual studio. I have checked in PackagesLocalDirectory path and able to see Projects and Metadata created for Release and Trunk folders. However, when I try to open solution file, it is throwing the same above error you have mentioned.

Can you please help ?

Regards

Ana

Was this reply helpful? Yes No
Suggested answer

Iulian Cordobin 8,201 on at

Like (0)

Report

RE: AX7 Code upgrade - The Model specified on the project cannot be found

Thought to also share my fix to the exact same problem (description accurate in the initial post). So, after upgrading the code though LCS, when I was trying to open the solution (UpgradedSolution.sln) I was getting the model not found. I thought initially I had to manually create from Visual Studio the models, but they also has a "." in their name and I was getting an error that the name was invalid.

Then I realized (reading this post) that the Metadata folder was in my repository folder but not in the AOSPackages folder. So, copying its content to the Packages folder (next to the other Packages, like ApplicationFoundation, Suite, etc) the solution loaded properly.

Was this reply helpful? Yes No
Martín Flores on at

Like (0)

Report

RE: AX7 Code upgrade - The Model specified on the project cannot be found

Hi Hichem, in Source Control Tab, right click on the folder you want to fix, then advanced and remove mapping.

There you can update your mapping or remove it.

Hope it helps!

Regards

Martín

Was this reply helpful? Yes No
Hichem.Chekebkeb 3,371 on at

Like (0)

Report

RE: AX7 Code upgrade - The Model specified on the project cannot be found

Hi Martin,

I am facing the same issue. Could you tell us how you fixed the mapping?

Was this reply helpful? Yes No
Verified answer

Martín Flores on at

Like (0)

Report

RE: AX7 Code upgrade - The Model specified on the project cannot be found

Thanks for your answer Ievgen.

This was my fault, I didn't realized that the metadata directory was wrongly mapped, visual studio created a metadata directory inside my local package directory. I fixed the mapping and started working

Thank you!

Was this reply helpful? Yes No
Mea_ 60,284 on at

Like (1)

Report

RE: AX7 Code upgrade - The Model specified on the project cannot be found

Hi Martin Flores,

Usually you can see this error when descriptor folder for this model was not synchronized from version control.

Was this reply helpful? Yes No