Skip to main content
Solved

IFS transformers issue

  • September 21, 2023
  • 3 replies
  • 325 views

Forum|alt.badge.img+3

We need to import XML file but we struggle with problems with every IFS prepared transformer.

  1. IFS_XML_TO_JSON

Here is the example input XML file (focus on the marked):

 

Transformer does not work for collections.
First line of collection works properly, but next lines have type changed to Integer.
As per IFS docs. we expect that all output datatypes for transformer should be text.

Here is the JSON output:

 

Does anyone resolved/worked-around this problem ?

 

  1. IFS_XML_TO_JSON_GENERIC

Here is the example input XML file:

 

This transformer also does not work for collections. First line of collection works properly, but next lines are wrongly parsed and type changed to Integer.

Here is the JSON output:

 

  1. We also tried transformer “MODEL_BASED_XML_TO_JSON” but it does not use subcollections at all (we tested on SalesMessageService.ReceiveCustomerOrder with subcollection “ExtCustOrdLines”)

 

Any hints are appreciated.

Best answer by Krzysztof Ryszkowski

Issue solved with RU23R2

View original
Did this topic help you find an answer to your question?

3 replies

Forum|alt.badge.img+3

We managed to use our own xsl transformer together with MODEL_BASED_XML_TO_JSON transformer for action SalesMessageService.ReceiveCustomerOrder.

Input schema for MODEL_BASED_XML_TO_JSON in attached.

Issue with IFS_XML_TO_JSON GENERIC and IFS_XML_TO_JSON makes this two unusable for ReceiveCustomerOrder action.  


Forum|alt.badge.img+3

Issue solved with RU23R2


AveTonitM
Sidekick (Partner)
Forum|alt.badge.img+9
  • Sidekick (Partner)
  • 141 replies
  • June 5, 2024
Krzysztof Ryszkowski wrote:

We need to import XML file but we struggle with problems with every IFS prepared transformer.

  1. IFS_XML_TO_JSON

Here is the example input XML file (focus on the marked):

 

Transformer does not work for collections.
First line of collection works properly, but next lines have type changed to Integer.
As per IFS docs. we expect that all output datatypes for transformer should be text.

Here is the JSON output:

 

Does anyone resolved/worked-around this problem ?

 

  1. IFS_XML_TO_JSON_GENERIC

Here is the example input XML file:

 

This transformer also does not work for collections. First line of collection works properly, but next lines are wrongly parsed and type changed to Integer.

Here is the JSON output:

 

  1. We also tried transformer “MODEL_BASED_XML_TO_JSON” but it does not use subcollections at all (we tested on SalesMessageService.ReceiveCustomerOrder with subcollection “ExtCustOrdLines”)

 

Any hints are appreciated.

 @Krzysztof Ryszkowski I’m struggling also with the IFS prepared XML-JSON transformers. How is it possible to validate or see the output JSON body when all routing rules and application messages are stopped in errors?


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings