In this post I will cover import-export data using the composite entities in new Microsoft Dynamics AX RTW. There are 12 composite entities available out of box.
I will take example of Customer Payment Journal entity. It has 2 following entities as a part of it.
Export the Payment journal:
Navigate to Data management.
Click on Export.
Fill in the details as follows:
Name of the data package.
Target Data format: For composite entity only allowed data formats are XML-Element and XML-Attribute.
Entity Name: Customer invoice journal
Click on the Add entity.
Customer payment journal entity will be added as shown below.
Click on the export.
As you see in the above screenshot, total 38 records were exported. 8 out of Header entity and 30 out of line. Click on the Download button. The XML file will be downloaded. It looks like below:
Import the Payment journal:
Similar to export create an import data package with same entity.
Upload the XML file with the new payment journal. I created a file with 1 header and 1 line and then click on import.
Directly from Staging data you can go to created payment journal.
Journal looks like below:
You can now validate and post the journal.
I will take example of Customer Payment Journal entity. It has 2 following entities as a part of it.
- CustomerInvoiceJournalHeader
- CustomerInvoiceJournalLine
Export the Payment journal:
Navigate to Data management.
Click on Export.
Fill in the details as follows:
Name of the data package.
Target Data format: For composite entity only allowed data formats are XML-Element and XML-Attribute.
Entity Name: Customer invoice journal
Click on the Add entity.
Customer payment journal entity will be added as shown below.
Click on the export.
As you see in the above screenshot, total 38 records were exported. 8 out of Header entity and 30 out of line. Click on the Download button. The XML file will be downloaded. It looks like below:
Import the Payment journal:
Similar to export create an import data package with same entity.
Upload the XML file with the new payment journal. I created a file with 1 header and 1 line and then click on import.
Directly from Staging data you can go to created payment journal.
Journal looks like below:
this does not work for importing EDI 820 Customer Payment Journals where the Journal Batch Number is generated on the Header and should copy to the lines .
ReplyDeleteThis composite Data entity is broken for this functionality.
I am at a loss as to what the Dimension sets for integration need to be set to...
Results. The number of dimension values specified in [CustAccount] is different from the number set up in the active format for data entities.
Things to try:
• Make sure the number of dimension values specified matches the active format for data entities.
• Make sure that any dimension values specified that include the chart of accounts delimiter character in the name escape the delimiter character with a backslash character '\'.
Results. Error found when validating record.
Thanks for nice information
ReplyDeleteImportexportfederation provide all export licenses at affordable cost. We provide Import Export Code (IEC) License free of cost in Pune, Mumbai, and Maharashtra, India.import export licenses seminars, international trade licenses at affordable cost,IEC License, Import License Consultants, import export license, Import Export Code License
What are you using to edit the multi level XML, excel will open and display these composite but refuses to save the data back into a XMl due to the "list in list" error (i.e. XML that have header and line)
ReplyDelete