I have an exported Model Store from AX2012 R2 CU6 that would now like to import just the Var Model into AX2012 R2 CU7. What steps do I take to do this?
You can use "Install-AXmodel" to install the exported axmodel:
Notice that the default behavior is model will be installed in the same application layer it was exported from.
Tommy Skaue | Dynamics AX Developer from Norway | http://yetanotherdynamicsaxblog.blogspot.no/ | www.axdata.no
The model store contains all elements for all layers and models with the installation specific ID's. It is not possible to import just the VAR model from this model store.
Is is possible to export the VAR model (not the complete store) and import this in a CU7 installation. If you want to keep the installation specific ID's you need to upgrade the CU6 VAR installation.
André Arnaud de Calavon | Microsoft Dynamics AX Solution architect | My blog | My company
This post is my own opinion and does not necessarily reflect the opinion or view of my company, Microsoft, both its employees, or other MVPs.
Andre's answer is correct. I misread the question. :-)
I was afraid of that. I should start by saying that this is a test upgrade. I exported the model store thinking I could restore it after creating a new database, and avoid 6 hours of compiling. I tried, but the import of the store wouldn't get past the ID conflict prompt. Then I discovered cu7! 30 minute compiles! I reinstalled all components and am to the pont of creating the var model. I also created an xpo of the var layer, so that I could fall back to the familiar, but I wanted to get familiar with using the models. can I restore a full model store to a fresh cu6 installation?
You should really read through the upgrade guide carefully, escpecially the code upgrade part, to familiarize yourself with the steps when upgrading layers by layers AND making sure your Element IDs and Element Handles remains unchanged. You do not want loss of data.
Also feel free to read my blogpost about element IDs and element Handles - hopefully it gives some additional insight.
A code upgrade done right is not something to be taken lightly. :-)
Check this out. Here you can filter models based on layers-Import/Export models without powershell/AXUtil inside AX client.:)http://www.42hertz.com/posts/42hertz-dynamics-ax-model-porter/. Thanks 42hertz INC
App URL: http://store.42hertz.com/collections/ax-modules/products/42hertz-dynamics-ax-model-porter
While exporting has a pretty low risk, importing models into a running system isn't recommended at all.
The wizard looks for OK for a developer who doesn't want to run command line tools, but the steps prior and after installing a model will still remain the same and have the same "technical" aspect.
I feel the wizard lacks that small hint of "use with care", and the gives the impression you can install models just by running a wizard, which is more often never the case. :-)
Well, this tool basically uses the same dll, which is used by powershell/AXUtil, and is anyway present on the client.
The tool just removes the step of using another utility to import/export models and allows you to do the same within the client itself.
The dll handles all the "risk factors" and besides this will relieve you of the migration tension. Test->Staging->Production..... you can keep it in every environment. It is simple and fast.
What Tommy means that even if use a wizard, you still have to do all subsequent steps such as the AOS restart, compilation and so on. You saved just a single command. It makes sense if you do everything manually, but than you're doing it wrong anyway. Command-line scripts allow you use automate all mundane steps (stopping services, installing models etc.) and you don't have to waste precious time just with clicking around.
By the way, you mentioned a production environment but installing individual models to production environments isn't recommended. You should use the model store instead, which will also help you to shorten the down time.
The risk is that you would keep it simple - but slow and wrong. Just ignoring some steps doesn't really make the problem simpler.
Martin "Goshoom" Dráb | Freelancer | Goshoom.NET Dev Blog
See you are just speaking about one side of it i.e import, which requires you to do these subsequent steps. But exporting does not require you to all these.
You being a technical guy would prefer to use Command-line scripts which is fine.
This tool is for people who are not very technically sound in this particular thing.
Providing them with a GUI would make it really easy. So there is nothing wrong or right here as it depends on the user who is using it.
I would agree with you if it was just for export and your post didn't seem to suggest that you can simply run a wizard to install a model to AX environment.
I want to be sure that users won't get wrong impression and don't forget about other crucial steps.
Well it does allow you to install also but I agree you would have to do the other steps manually. However, most users feel comfortable with GUI and that's what post is also saying.