160
Hello,
Is there a "magic" way to move elements from a specific model to another?
(As in AX2012 the option move to model)
For exemple:
All my new specific EDT/Table from MyModel to the ApplicationSuite model?
*This post is locked for comments
When you move something from one package to another, you have to first compile the original package to get the code "out". Then compile the new package to get your code in that binary. If you setup the tools to synchronize when you compile this could result in data loss on your box. If you don't have that setup and do a sync after both packages are compiled - then there will be no data loss.
Also when deploying to an existing environment this won't result in data loss if both removal from one package and addition to another are deployed together (since sync is done at the end of deploying all packages in the deployable package). And of course, it assumes the fields/tables have the same name still...
I'd say there generally shouldn't be data loss as long as table and fields keep the same names as before.
I've moved fields from customised tables to their respective extensions and entire tables between models without data loss.
I think the only crucial step apart from not changing names is to synchronise the db at the very end, not while you're still making changes.
I actually wouldn't expect data loss, although I'm not sure. Note that the file don't contain any ID at all; IDs for names are assigned on synchronization. And since the name doesn't change, AX can keep the ID the same.
Simply test it to know for sure which theory is correct.
I think you are right. Probably the data will be deleted. I don´t know if we can modify those Id like we used to do it older "AX" versions in the Data Dictionary tables. Specially in migration scenarios, sometimes we had to "play" with those Ids for table and fields.
I think Data would be lost for that column, because field name would be same but field ID (fieldnum) would be different.
Hi Joris,
One more question regarding this. I know is an old topic. If there's an over-layering modification, that adds a new field in a standard table. (This is in Production environment). Now we are working in a extensible solution in Development environment. Let's say we deleted the field from the overlayering model, and created a new one in a new model (because as you say we can't move the customization in that scenario). What will happen when we deploy the solution package into Sandbox? will the data be deleted from the field / even though the field still exists in the table but now in a different model?
Here's a Powershell snip you can modify that I used to move in VSTS to retain history.
$tf = "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\tf.exe" $source = "$/MyProject/Trunk/Main/Metadata/Directory/Directory.MySolution/AxTable/*" $target = "$/MyProject/Trunk/Main/Metadata/MySolution/MySolution/AxTable/" . $tf rename $source $target
I'll just chip in with my notes on moving label files:
Hi, Foxsor.
If your question has been answered please mark the helpful answers as verified and mark this thread resolved. Thanks.
@Róbert, I would think you need to move in VSTS otherwise when you get latest, it will just put the files back, which could duplicate them in both models?
#1
André Arnaud de Cal...
293,245
Super User 2025 Season 1
#2
Martin Dráb
231,923
Most Valuable Professional
#3
nmaenpaa
101,156
Moderator
Share
Report
All responses (
Answers (
