How to convert a custom xml file for import into D365?

(0) Share

Report

Posted on by Shooowtek

843

Hi,

I am creating a PO using an import xml file. Everything is OK in the standard, but I have a problem with the custom file. How can I customize the xml file I get from an external company to match the import into D365 for (sales orders composite V3) "SalesOrderV3Entity data entity?

I have been trying to create an xslt file so that I can convert the file I receive to one that will fit into d365.

Could someone please give me some suggestions on what steps I should take?

Thanks in advance.

I have the same question (0)

All responses (9)

Answers (1)

Suggested answer

Martin Dráb 237,795 Most Valuable Professional on at

Like (0)

Report

Add an entity and close the dialog. The double-click View map field, which opens Map source to staging form. Switch to Tranformations tab - that's where you can add transformations.

Another option is transforming the file even before using it in F&O.

Was this reply helpful? Yes No
Shooowtek 843 on at

Like (0)

Report

Hi Martin,

Thank you for your answer.

OK, but is this dialog the "raw" xml file from the customer should be uploaded?

When I do that, I getting this result, with no available mapping and no place to load the XSLT file..

btw, is it a good practice for the end-user to import PO into D365 in this way?

There is no way for an end-user to receive a differently structured XML file from their customer.

Was this reply helpful? Yes No
Martin Dráb 237,795 Most Valuable Professional on at

Like (0)

Report

There is a place to upload the XSLT. You missed the step of double-click the View map field (the red cross), which will open the form where transformations can be set up.

I think it'll be easier if your upload an already transformed file. If you tested your transformation, you should already have such a file available.

Was this reply helpful? Yes No
Shooowtek 843 on at

Like (0)

Report

It is not clear to me how this mechanism works.
Should I load an XSLT file as the first file, which itself is a "recipe" is to translate the XML file from the client to an XML file that is accepted in the D365 import?

In my opinion, the first dialog should load the "raw" file from the client and then in the form with transformations, select the XSLT file and apply it?

Could you give me an existing example where I could follow this process step by step?

I tried to load the XSLT file..

Was this reply helpful? Yes No
Verified answer

Martin Dráb 237,795 Most Valuable Professional on at

Like (0)

Report

The transformation (XSLT) should be added at the Transformation tab (your last screenshot).

You can find examples on internet, e.g. XSLT transformation in Dynamics 365 for operation.

Was this reply helpful? Yes No
Shooowtek 843 on at

Like (0)

Report

OK, thanks. I've already analyzed this example.

So the first file I load into the system is the "raw" XML from the external customer?

Do I need to transform it somehow before uploading it to the system (first screenshot in my previous post)?

As I mentioned, I'm getting an XML file that completely does not match the PO import into D365.

Steps I understand:
1. System administration ->Data management -> Import
2. Add file
3. Source data format -> XML-Element
4. Entity name -> Sales orders composite V3
5. Upload data file -> I choose the "raw" XML file from the customer
6. View map -> view map
7. Transformations -> New -> Upload file
8. Apply transforms

Was this reply helpful? Yes No
Martin Dráb 237,795 Most Valuable Professional on at

Like (0)

Report

No, use the transformed file. Use your XSLT to transform it. As I said, if you tested your XSLT, you should already have a tranformed file available.

Was this reply helpful? Yes No
Shooowtek 843 on at

Like (0)

Report

OK, I get it.

I can do that because I have access to Visual Studio.

But in general, this task will fall to the end user at the client, who will not have the knowledge or access to Visual Studio etc.

Is there any way to transform the XML file just using D365?

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 237,795 Most Valuable Professional on at

Like (0)

Report

Users can easily get a file in the right format by exporting some data through the entity.

Regarding your other question, yes, you can use other programming language to write transformation logic, such as X++ or C#. But than it's completely out og hands of end users. If you want something that (power) users can do by themselves, consider Power Automate.

By the way, Visual Studio is just one of many tools that can be used to develop and test XSLT.

Was this reply helpful? Yes No