Replace XSLT transformation in the current data management project for ER file import

(0) Share

Report

Posted on by VRD

Hi,

Now, as per MS docs below , XSLT script in data management is being deprecated from the platform version 10.0.30.

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/get-started/removed-deprecated-features-platform-updates#xslt-scripting-in-data-management

MS has clearly mentioned that X++ based solutions needs to be applied instead.

-------------------------------------------------------------------------------------------------

Current Scenario :- 10.0.28 platform version.

We have a Bank response file (flat file) that we get from the bank for the payment approval/rejection notification and based on this file, we mark the paymentstatus in the payment journal lines.

As per the current implementation, we have a custom entity created from LedgerJournalTrans table and used into Data Import project in the Data Management. We created the recurring integration end points where the above ER file (comes from the bank) is integrated to data management import project periodically and we have XSLT transformation applied to this data import project which then sends data to the entity and finally journal lines are getting updated.

-------------------------------------------------------------------------------------------------

My questions are

1. Can we just keep above implementation and just remove XSLT and write code of transformation in Data Entity methods itself? If yes, What should be the approach? What methods of the data entity can be used to read the flat file and transform the data before it can call to the actual data entity insert method?

2. Is it a good idea to write a custom service with all the transformation code and data insert directly to journal line table from the service itself and never use data entity? Let the exernal API calls this service endpoint to pass the flat file to it.

3. Another approach we are thinking of Electronic Reporting. We can create a ER model and format and what standard class we can use which accepts the files and pass it to this ER model and gives us the output records that later on can be inserted into the journal line table.

Experts - Please suggest what would be the best approach here?

Thanks & Regards,

Vikky

I have the same question (0)

All responses (6)

Answers (0)

Martin Dráb 238,024 Most Valuable Professional on at

Like (0)

Report

My understanding is that the ability to use XSLT transformations isn't removed. You just can't use scripting inside XSLT.

Was this reply helpful? Yes No
VRD on at

Like (0)

Report

Hi Martin,

Thanks for your response.

How do I know if my XSLT file has script?

Below is my one of the XSLT and it contains the C# script at the end in the same file. there is a function trimDateTime() which is getting used at the multiple places in the same file.

Below is the script at the end in the same XSLT file.

If this is going to be deprecated then we need a way to implement it through other means.

Regards,

Vikky

Was this reply helpful? Yes No
VRD on at

Like (0)

Report

Here I am providing more information to my original question, so that you will understand how we have set it up.

Currently we are pushing this file using Recurring integration that uses REST API as mentioned in below article. We get bank file which is integrated with Dynamics using REST API call. This kicks in DMF import project where we have a data entity set and XSLT Transformations are applied.

docs.microsoft.com/.../recurring-integrations

We are looking for the best approach going forward for this import to work fine.

Do you think the best approach would be to create custom service and publish the endpoint from where bank file can be sent? Here transformation logic needs to be written in X++ for the obvious reasons.

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

Like (0)

Report

Can't you simply put the logic to the data entity, as it's usually done?

And is it even needed at all? yyyy-MM-ddTHH:mm looks like the right format for datetime fields, and I guess that F&O will use the null date (1900-01-01) if the imported value is empty. But I may be wrong.

Was this reply helpful? Yes No
VRD on at

Like (0)

Report

Hi Martin,

This is exactly I am expecting to do if that is easier than writing whole new Custom Service.

My incoming file is unstructured file. Transformation was doing all the job of formatting and pushing to entity and doing mapping as per the fields available in the entity.

But I am not sure, which data entity method can provide me access to whole content of incoming file which I can apply my own logic of transformation and then move ahead with this transformed data to push into data entity. There are not much documentation available around this.

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

Like (0)

Report

There is no such a method. Also, why do you want to throw away the complete transformation and start again with a completely new solution if your only problem is with trimDateTime()?

You can also keep using your transformation (including the script). You won't be able to use it inside F&O, but you could use a middle-tier service (e.g. a Logic App, Azure function or a custom web service) to run XSLT and push the transformed file to F&O.

Was this reply helpful? Yes No