You’re offline. This is a read only version of the page.
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.
Can anyone help how to resolve below error? Or from where to see metadata events?
*This post is locked for comments
Hi Tejas,
Please post answer if you find any solution.
Regards,
Smit
Thanks Sumit.
Yeah I am facing same issue.
Regards,
Tejas.
Hi Tejas,
We discarded VM. It was critical for us but I did not have any options. Are you facing same issue?
Regards,
Smit
Hi Suit,
so what did you finally do to resolve this?
Regards,
Tejas.
Smit, I moved your question from the other thread, because it's clearly a continuation of this discussion.
First of all, please tell us what you didn't simply deploy a new box, after two of us told you it's likely the easiest solution. Why are you complicate your life, especially when see how you're struggling with it?
Then, if you have to follow the more complicate path anyway, you'll have to tell us which errors you got and what "package MS given: you're talking about. I thought you were talking about your customizations, not a package from Microsoft.
Hi Martin,
Sorry for asking same again.
I am getting errors while recompiling itself. When I try to rebuild project creating elements which have errors. It takes lot of time or I can say it is not getting completed. I have to stop them manually after 2 hours. Please suggest me alternative.
I thought to deploy package MS given for update 2 to update 3. But still it is finding those elements on AOS update step as well as sync step. I am totally clueless how to move further.
Can we do recompile by command window?
Regards,
Smit Patel
Hi Smit,
Like Martin already mentioned, the most easy way to get a really clean environment is deploying a new fresh environment.
You said you wanted to migrate your customization to a new version, which can't be done deployable packages. These are used for code deployment, so you did a wrong thing from the very beginning. Forget about changing XML files; they're not included in deployable packages so installing a deployable package doesn't change them.
I don't know what you mean by "to do anything", but the error in the screenshot was thrown when applying the package, which you shouldn't be anymore. Didn't you mean a different error?
If you need a clean 1611 application, the easiest way likely is a deploying a new box. If you don't want to do it for some reason, I suggest you try to recompile the whole application (if the environment contains source code.
Is there any way if I delete some folder or some XMLs from Packages folder then I will come to base product?
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
#1
Mohamed Amine Mahmoudi
100
Super User 2025 Season 1
#2
Community Member
48
#3
Zain Mehmood
6
Moderator
Share
Report
All responses (
Answers (
