Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012CRM Connector in Microsoft Dynamics AX 2012Financials Management in Microsoft Dynamics AX 2012Upgrading to Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
Inventory Costing in Microsoft Dynamics AX 2009
SSRS and SSAS Integration
I am trying to make a build, based on code from ax 2012. Does anyone have any idea how to make an axmodel from the physical xpo files? In a demo video in januari, David Froslie showed they had tried that, but i haven't found information on how.
you have to use AxUtil create
open AOT -> Tools -> Model management - > create model
create a new model
select the new create model and import the code.
you do the same thing using for the creation build using AxUtil
@Bjorn: Your question is actually pretty good.
Definitely you can use a similar approach as in AX2009, i.e. to extract .xpo files from the repository, merge them and import them to AX. Then you could export the model from your build environment.
It would be nice to create a model directly from .xpo files - unfortunately I don't know how. I'll try to explore it later, it could be useful for us as well.
[ Goshoom.NET Dev Blog ]
If the xpo are already imported to the default model like VAR or CUS then you can move the elements form model to another using AXutil move
Add the time of creation of model , you can check it to TFS
Huzaifa, please, Bjorn would like to build a model by Team Foundation Build.
Well, as Martin said...this is a realy great question.
I am also trying to solve this.
As far as i know there is no tool available which creates a model from a set xpo files.
So you have to use some kind of workarround.
Theoreticaly it should work when you have something like a build system connected to tfs.
1. You have to sync the Build system with tfs (get the current sources).
2. Compile and synchronise the application.
3. Do a best practice check and/or run the unit tests (this step is optional)
4. Use AxUtil to export the model.
But in the standard there is no support to trigger Ax to synch the sources lets say form a build template or build task. So this is a point were you have to write a customisation for.
For the other steps it should be possible to use i.e. a Command Task inside the Build-Workflow.
Please, when you get this running.....share this with us.. :-)
The model store stores both the X++ compiled and the IL compiled code, along with the source. So, you cannot directly convert an XPO to a model, since it needs to be compiled as well. The AXUtil utility works directly on the model SQL database, it does not use the AOS. So AxUtil as such cannot do anything with XPOs, unfortunately (the AOS contains the kernel with the compiler).
Think about builds in previous versions of AX. The only binary output you could get for AX was a layer file, today it's models. But to create a binary build of something, you need to convert source code into compiled code. That's the AOS. So the process is not too different between AX 2009 and AX 2012, just the output. Process is still, combine the XPOs, import into one or more models, compile, and export the output, which is now a model instead of a layer file.
I have resource on my blog, including a TFS 2010 XAML file, and build scripts on CodePlex for AX 2009. These cannot be directly taken to use for 2012 (I'm working on getting those out and available), but with some adaptation it can be done, since the process is not too much different.
Check daxmusings.blogspot.com/.../alm-from-source-control-to-deployment.html where I've listed some links to blog posts, and other resources available online. Again, these are all 2009, but it illustrates the flow quite well.
Dynamics AX MVP | My Blog | Sikich | Twitter @JorisdG
FYI, the demo from Dave Froslie from January used the same principals (combine XPOs, import them, compile the whole thing), although he didn't show it in the demo directly. Dave has actually told me this morning they are working to get more guidelines out for AX 2012, and he was gathering some common issues and questions as they've come up from people I've worked with. No timeframe on that, since he and his team are doing this voluntarily for the community.
Well, wenn combile xpo is used to create a "layer xpo" there is still on problem.
When combine xpo is used, only the x++ parts of the current soure code can be imported into the build system. This will not handle the reports, .net assemblies and so on.
So my thinking is, that some kind of trigger function is needed, to invoke the synchronisation process of AX to get all sources incl. the reports, visual studio project and so on.
@Joris: I have seen the project on codeplex you created for the AX build process. Would be nice when we can talk a little bit more in detail about the AX-TFS-Build......
@Joris: Correct me if I'm wrong, but I think although the model store contains compiled code and it's so also for .axmodelsore exports, it's not true for .axmodel exports.
This is also visible in the import workflow, when installation of .axmodel requires compilation (and IL generation) while .axmodelstore doesn't.
@Axel: And is the synchronization a big issue? SysVersionControlSynchronization (-> SysVersionControlSystemFileBased.commandSynchronize()) supports synchronization to a label and to call it is all what's needed, isn't it?
BTW what I've explored to far, the export to .axmodel seems to not do much more than just serializing model store database objects, but still that's nothing what I would like to replicate. When an object is saved in AX, XU_Insert or XU_Update storage procedure is called, but the data are already preprocessed by AX or some component between. It looks like it way would go too deep into AX bowels than it's reasonable.
The Modelstore includes everything for sure (I actually confirmed that this week with Microsoft - I will blog on this soon), agreed I'm a little unsure about the .axmodel file.
However, the axmodel does contain the p-code for X++ at least. It's easy to try this out... because of the "installation specific IDs", the p-code inside an .AxModel contains the compiled code for fields and classes, so they get the IDs compiled into them. I have run into issues already, that if you don't compile after installing a model, the code potentially references the wrong fields because it has the wrong IDs in it (this to me is proof that there is in fact compiled code in the AxModel).
@akuehn: everything is in the XPOs, including visual studio projects and reports, I'm not sure what you are saying there? Granted, reports are not DEPLOYED, but they are definitely in the XPOs. As far as assemblies go, the import of an XPO project imports the code, and a compile inside AX actually runs the build to compile the assemblies. So I'm curious what you think is not there?
Also, if you can use the "contact me" on my blog we can chat about TFS. I'd rather not publish my email address out in the open like that :-)
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13