Skip to main content

Duplicate a company in AX 2012

I have heard from a few people struggling to duplicate a company in AX 2012. So, I decided to try it out my self.

The recommended approach is to use dat/def export and import. There is a good article on technet.

Import duplicate company data to use for testing [AX 2012]

I  have had 1 failed and 1 successful duplicate attempt. I will explain the steps that worked for me.

1. Create your new Legal entity

2013-07-29_2028

2. Set up the Ledger form which is a shared table. I selected the same account structures as the company I was copying from.

2013-07-29_2030

3. Create a definition group to export the data from main source company. If I didnt want master data such as customers, vendors etc. I would untick Main group.

2013-07-29_2032

Included shared tables in my export.

2013-07-29_2036

Now export your dat/def.

4. Now I imported without shared tables.

2013-07-29_2035

5. The result is good. Chart of accounts and posting profiles all work fine. Vendors, customers imported fine (note: the vendor uses the same partyId as the source company).

 

Summary

This shows steps that worked for me. My first attempt I set the Ledger form after the import. This failed to resolve any references to dimensions, main accounts etc. So don’t forget to set it up first. This may or may not have been the issue for me. I wasn’t paying close attention.

If you are moving data be very conscious of your account structures, financial dimension etc. They are the biggest headache to resolve and fix up.

If you are importing master data such as vendors, customers and products. Then dont import the Main table type. Then use Data Import Export framework to pull those through.

Reference:

Import duplicate company data to use for testing [AX 2012]

Import data from another instance of Microsoft Dynamics AX [AX 2012]

Popular posts from this blog

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !set.in(custTable))         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi