Skip to main content

Data Import/Export Framework–Move data from AX to another AX environment

This below is a step by step to export data from an AX environment to another environment using the Data Import/Export Framework.

Export from Source AX environment

1. Open the Source data formats form.

Create a record and select AX type.

DataFormat2013-03-31_1743

2. Open the Processing group form and create a new record.

Proc2013-03-31_1837

3. Click on Entities button.

Select your entities you want to export (Example below has Customers).

Entit2013-03-31_1838

4. (Optional) You can click on the Select button to put a filter.

Q2013-03-31_1840

5. Go back the Processing group form and click the Get staging data button. This will bring up the following execution form. Click the Run. This will then pull data and place it in staging table. It will enable the buttons on the Processing group form.

Stag2013-03-31_1846

6. On the Processing group form, click the Export to AX button. This will bring up a dialog, enter the file name and type.

E2013-03-31_1851

This will generate a dat and def file.

Import into Destination AX environment (Option 1)

We will import the file using dat/def. Other options to use files.

1. Click on System administration > Common > Data export/import > import

Select your file.

I2013-03-31_1855

There is an option on the Advanced tab. Tick the Update existing record flag if you dont want to replace some important data in your Data Import/Export Framework tables.

I2013-03-31_1855_001

Click OK.

2. This will import data into the staging table and the processing group table. Ready to be executed.

3. Go the Processing group form and you should find the data already in the staging table too.

4. Click on the Copy data to target button. Follow the prompts and run it. This step will move the data from the staging table to the target destination.

Import into Destination AX environment (Option 2)

After we have our data in the staging tables. Instead of exporting to dat/def files. We will instead export to a flat file (csv).

1. In the Execution history. Click on the view staging data. This will bring up a dynamic grid showing your data.

E2013-03-31_1911

2. Click on the Export to file button. This will allow you to select a processing group (a file format setup).

Enter your file name and click OK.

s2013-03-31_1914

This has generated a file now that you can use for importing into your other environment.

Follow these step by step that I wrote last year to import using a file (csv).

http://dynamicsnavax.blogspot.com.au/2012/08/step-by-step-import-with-data-migration.html

Labels:

Popular posts from this blog

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.
Read more

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: ...
Read more

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...
Read more