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

Purchase requisition – Price

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line.   NOTE: ...

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.

Dynamics 365 Invoice Capture Feature

Microsoft recently released the new Invoice Capture for Dynamics 365 Finance. I ran through installing and configuring it.  From that experience, below is my brain dump and hopefully it can help with things that are not so obvious. Three type of invoice captures There are three invoice type paths that can be captured. These drive the screen layout and what kind of information is mandatory. PO invoice Header-only Cost invoice When an invoice comes in, you can select one of the three invoice types. Below are the three screen layouts and differences. PO invoice – Invoices of this type are associated with purchase orders. The purchase order details must be determined on each invoice line. Both the header and the lines must be reviewed in Invoice capture. This will create a pending vendor invoice. Header-only – Invoices of this type are associated with purchase orders. The purchase order field on the invoice header is a mandatory field. If the Automatically create invoice lines featur...