Errors when importing solution to Visual Studio

(0) Share

Report

Posted on by Community Member

I want to move a project that I have been working on from one VM to another. I tried to do this by doing the export/import that Dynamics provides, following this link: https://community.dynamics.com/ax/b/axilitynet/archive/2016/05/19/project-export-and-import

When I imported the project, I selected the axpp file which was located on the VM desktop for the file name. I entered C:\Users\sovos1\Documents\Visual Studio 2015\Projects for the project file location. I selected "new solution" to open the project in (since this is a new VM I didnt have any solutions). I also checked the overwrite solution.

The project was imported with no errors. Then I ran a build of the project. The build finished stating that the build completed. Then it prompted me that I had 50 errors. these errors were caused by classes that had _packageSlip appended to them. How can I resolve these errors? There is a screenshot below of the build and the errors.

7462.Capture.PNG 1185.Capture1.PNG

None of these errors exist in the VM that I exported the solution from to generate the axpp file. How can I fix these errors?

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

Martin Dráb 237,948 Most Valuable Professional on at

Like (0)

Report

What's the version of your application? Is it the same in both of your environments?

It seems that your target application doesn't contain the Indian localization.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

The version that I am moving to is the platform 3 version. The version I exported from was an older version, the platform 1 version.

blogs.msdn.microsoft.com/.../overview-of-microsoft-dynamics-ax-build-numbers

Was this reply helpful? Yes No
Martin Dráb 237,948 Most Valuable Professional on at

Like (0)

Report

You're talking about the platform, but what's the version of the application. You clearly have a problem with the application, i.e. things like tables and forms.

You can't simply import code from another version; you have to upgrade it to work with the new application.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

On the same link that I provided above, there is a section called application updates. The one running on platform 3 is application version 1611

The platform 1 version is running application version 7.01

Is this what you are referring to? If not ill try to locate the information if it will help solve the issue. How can I go about upgrading the code to work with the new application? And by that I mean, is it just simply a manual process where I go back and alter my code, or does Dynamics have a feature to automatically adjust according to the application version?

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

Like (0)

Report

Try building ApplicationSuite package instead of building your solution alone. And also other packages if they have any customization.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Building the ApplicationSuite did not solve remove any of the errors, but thank you for the suggestion.

Although I still have 1 error remaining at this point, I have fixed the other 49. I had copies of tables, forms and classes in my debug folder(they had "copy" appended to the end of the name or [c] after the name). This code was copied over to my solution from the older version of AX, which was conflicting with the new version of those same classes. None of my tables, forms, or classes that I created from scratch were throwing any errors. Upon removing these copies from my solution the errors went away.

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 237,948 Most Valuable Professional on at

Like (0)

Report

You can apply platform and application updates independently, therefore an environment with Platform Update 3 doesn't necessarily have to have Application version 1611.

Regrading upgrade, you'll use the code upgrade service. Please refer to Overview of moving to the latest update of Microsoft Dynamics 365 for Operations on the wiki for details.

Was this reply helpful? Yes No