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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Deployable Package Issue
Microsoft Dynamics AX (Archived)

Deployable Package Issue

(0) ShareShare
ReportReport
Posted on by Community Member

Hi,

We have done customizations in old version of AX 7 and we are migrating same developments to platform update 3 (product version : 1611). To move the customizations I have deployed package from my old VM and trying to import in new VM. I have developed elements in new model under Application Suite. While deploying I am getting below error Runtime Metadata Invalid conflict. 2577.Error1.PNG

Can anyone help how to resolve below error? Or from where to see metadata events?

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Martin Dráb Profile Picture
    Martin Dráb 237,965 Most Valuable Professional on at

    Could you give us more information, please? For instance, what's the source and target version of application? You've mentioned only the target platform version and nothing else. It seems that you're trying to import code from one version to another without upgrading it, which would be incorrect - you should use the code upgrade service. Refer to Overview of moving to the latest update of Microsoft Dynamics 365 for Operations for details.

  • Verified answer
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 301,109 Super User 2025 Season 2 on at

    Hi Smit,

    The link provided by Martin is the best resource to do the proper upgrade. A deployable package should be created from a machine with the same version as the target system. So you cannot use a deployable package from e.g. AX RTW and use it on 1611. Use the correct prodecure for your upgrade.

    There are some metadata elements from the standard application moved from one model to another. This this the reason for your error message.

    Just curious? Did you create customizations as a customization model or are you using extension models only?

  • Community Member Profile Picture
    Community Member on at

    Hi Andre/Martin,

    Thanks for the reply. Yes I was trying to upgrade deployable package created on 7.0.1265.23020(RTW) to 1611. I have created extension model referencing Application suite model.

    So which would be best way to manage the scenario? I should first upgrade platform where I have done development and then get package and move it to other environment? or I should use axpps to move development in new environment. We do not have any scenario like production environment or development environment.

  • Community Member Profile Picture
    Community Member on at

    Okay. Thanks. Just for knowledge if I just import AXPP files then there will not be any version upgrade conflicts right?

    Regards,

    Smit

  • Martin Dráb Profile Picture
    Martin Dráb 237,965 Most Valuable Professional on at

    You should use the code upgrade service on LCS and resolve conflicts. Trying to move your without upgrading it won't work. If you open the link and scroll to "Scenario 2: Upgrade your custom code", you'll see that the code upgrade service is required in your case.

  • Community Member Profile Picture
    Community Member on at

    Hi Martin,

    I am giving description here only. It is related to this step but next error after this. See I have discarded import package of deployable package due to version mismatch. I thought it will revert to base product as it is not successful and I will build and sync again from Visual Studio.

    Now issue is due to Metadata conflicts it is giving some elements are present in other model too. Like below description.

    AX is shutting down due to an error.

    Duplicate metadata element has been detected in multiple modules. Please verify that application is deployed correctly and installed modules are compatible. Following elements are defined in more than one module:

    Element AxMap/FBContribCreditDetailMap_BR is defined in the following modules: FiscalBooks, ApplicationSuite

    So what should I do? I am not able to sync as well build.

    Should I download Operation 365 from LCS and try to deploy?

  • Martin Dráb Profile Picture
    Martin Dráb 237,965 Most Valuable Professional on at

    Can you elaborate what you mean by discarding a package? What exactly have you done?

    Are you trying to fix the target environment where you tried to import invalid code? If so, I would restore the packages from from backup and rebuild all packages. I think the package deployment makes a backup, so you should have it even if your company forgot to set up a backup strategy.

  • Community Member Profile Picture
    Community Member on at

    Hi Martin,

    Thanks for a reply.

    Discarded means I have simply closed the command prompt as I was not able to go further from step I was getting error.

    I thought if deployment is not done successful/ stopped in between then it will keep AX things in last stable state only. From where we can find that packages? If I get those packages then simply replace existing packages with back up package and then build or sync?

    Regards,

    Smit

  • Martin Dráb Profile Picture
    Martin Dráb 237,965 Most Valuable Professional on at

    As I think about what you said, I just don't understand what you did. It seems you wanted to move code, but you used a deployable package, which isn't about source code at all.

    Can you please confirm what you did and why, and whether you really have changed source code? Maybe you only screwed up the compiled application and not source code, so you can build the correct application from code.

  • Community Member Profile Picture
    Community Member on at

    Hi Martin,

    Thanks for your reply. See I have done deployable package movement for moving my customizations but there were same version.

    I tried to do same with different versions but it failed in between. So I thought I will get compiled base product if I am going to cancel installing deployable package in new version.

    Now when I am trying to do anything I am getting same error as in screenshot above. How can I get rid of that error? By restoring or deleting elements which it is suggesting in error? I don't know process.

    I need my application back in base form 1611 without any errors. I don't have any other instance. I have not changed anything in machine. I wanted to move my tables, forms and other customizations so I used deployable package thinking it will add customization in 1611 as well.

    Regards,

    Smit Patel

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…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans