During a synchronization between Microsoft Dynamics Ax 40 and another system it can happen that the import should be handled in a specific sequence.
So for example, before the addresses can be imported, the customers should be available.
In previous versions we used the RunBuff() method to run configured scripts. This is not allowed when you run in CIL.
There is a simple work around as there is new class: XppCompiler
http://msdn.microsoft.com/en-us/library/xppcompiler.executeex.aspx
A small sample is shown below:
The execute permission should of course been added as well.
The Business Integration Solution from To-Increase can be used to manage your data migration projects in Microsoft Dynamics Ax 2012:
In this blog I will highlight how to setup dependencies and still perform.
Product and item management is heavily changed in Ax 2012. The functionality is extended like:
The technical design of Ax 2012 is also changed. These changes have a lot of impact on the entire design. It’s using table inheritance, record id relations and so on. In this blog I will highlight how to import items using the Data Migration Studio. All the items are validated using the business rules to avoid inconsistency.
Read below how we get an impressive result.
Think about data sharing, cloud and application integrations. There are unlimited possibilities to receive a better value using your data.
Our Business Integration Solution on Microsoft Dynamics Ax 2012 is designed to fit that gap. We have a strong focus on:
As data migration to Microsoft Dynamics Ax 2012 is a challenge and you and others are struggling with this, I will start with an introduction to this part.
Data migration is an important part of an implementation project as most of the implementations are a replacement of the current ERP-system. One of the reasones can be for large international companies who want to use one ERP-system for all their legal enties. One application can make financial reporting and intercompany transactions easier.
As you may know, Microsoft Dynamics Ax 2012 is designed for global industries as it serves 36 countries with specific country support. It supports topics like:
An ERP implementation project requires a lot of knowledge about processes and how to map that to the application. That will raise the question: What will data migration add to the implementation project?
In Microsoft Dynamics ax 2009 and older we had a dimension field available for the dimensions for customers or items, Microsoft has chosen to introduce a new data model to support more flexibility with endless possibilities.
There are multiple ways to create the dimensions. In this blog I just want to highlight how this can be done via X++. There are posts available to the AIF services but it’s not required to use them.
In the post below I show how the dimensions can be used in combination with the ledger accounts.
The dimensions for customers can be managed in a similar way.
A really nice catch from Joris. He made a nice index to the different topics like how to import vendors, customers, open balances and more.
http://daxmusings.blogspot.com/2012/01/importing-data-to-ax-2012-using-excel.html
During a data migration project the the following two topics should be imported:
The data model in Microsoft Dynamics Ax 2012 has been changed. Also the daily journal is changed.
http://dc196.4shared.com/doc/2VrFxKd5/preview.html
In this blog I will try to explain how to use the ledger accounts and dimensions
In manufacturing companies you can have a lot of Bill Of Materials (BOM). When the Bill Of Materials are created for an integration to PLM or CAD systems or during data migration, the total of lines can be more than a million.
When you import the data into Microsoft Dynamics Ax, it can happen that the import will be slower and slower and slower.