Parsing XML on Errors

Integrator.io
, ,
1

So, I'm sending an API call to Excalibur WMS, and on error, it returns the following XML:

The image shows an HTTP response indicating a transaction failure due to a data issue, specifically a duplicate tag error in Microsoft Dynamics. (Captioned by AI)
The image shows an HTTP response indicating a transaction failure due to a data issue, specifically a duplicate tag error in Microsoft Dynamics. (Captioned by AI)860×243 42.6 KB

Since it doesn't return JSON, I can't put it into the mock output, nor does it get passed to later steps in the process, even when error handling is set to Proceed to the next application regardless, and the Override media type for error responses = JSON or Plain Text.

My goal is to extract this section of the response and put it into an email to the CSR.

The image shows an error message from Microsoft Dynamics, indicating a transaction failure due to a data issue with a duplicate tag ID. (Captioned by AI)
The image shows an error message from Microsoft Dynamics, indicating a transaction failure due to a data issue with a duplicate tag ID. (Captioned by AI)901×179 34.2 KB

Unfortunately, since the XML isn't parsing, I don't get any data back to be put into the response mapping.

I worked with @christran, and he told me to ask the community as well, so what do y'all think?

2

You have the "Override media type for error responses" set to XML? Plain text is always a backup as well. Can you share your setup?

The image shows a settings interface for configuring non-standard API response patterns, with "XML" selected for overriding the media type for error responses. (Captioned by AI)
The image shows a settings interface for configuring non-standard API response patterns, with "XML" selected for overriding the media type for error responses. (Captioned by AI)577×312 15.1 KB

3

Hello Tyler,

These are the options I have:

The image shows a user interface for configuring non-standard API response patterns with fields for HTTP response body paths, error and success values, and media type overrides. (Captioned by AI)
The image shows a user interface for configuring non-standard API response patterns with fields for HTTP response body paths, error and success values, and media type overrides. (Captioned by AI)894×661 31.7 KB

Setup:

The image shows a software interface for editing an HTTP import process with an error message related to a SOAP request indicating a duplicate tag issue. (Captioned by AI)
The image shows a software interface for editing an HTTP import process with an error message related to a SOAP request indicating a duplicate tag issue. (Captioned by AI)1828×758 112 KB

4

That must be because you already have media type as XML on your connection. If you click populate with live data, what happens? It should be parsing it into json and putting it into the _json field.

5

I get this

image
image568×106 9.38 KB

6

Also tried post response mapping to _json.message with Chris and that didn't give me anything either.

7

And when I put the parsed output into the mock output, then I get this set of errors

The image shows a JSON error response with a code 500, indicating a transaction failure due to a duplicate tag ID, displayed in two panels for mock and preview data. (Captioned by AI)
The image shows a JSON error response with a code 500, indicating a transaction failure due to a duplicate tag ID, displayed in two panels for mock and preview data. (Captioned by AI)1786×717 110 KB

image

8

Can you map to just _json in response mapping and see what you get during run?

9

Tried that

A message from Jack Harris discussing a failed attempt at response mapping with JSON. (Captioned by AI)
A message from Jack Harris discussing a failed attempt at response mapping with JSON. (Captioned by AI)783×182 16 KB

10

No, not to _json.message, just to _json.

11

Comes out as blank. I also tried clearing the the Mock Data and running in test and it just reverts to the "replace me" text in the response mapper.

The image shows a JSON structure with various attributes including "id," "mockResponse," "headers," "statusCode," "_json," and "traceKey." (Captioned by AI)
The image shows a JSON structure with various attributes including "id," "mockResponse," "headers," "statusCode," "_json," and "traceKey." (Captioned by AI)458×327 19.2 KB

12

Yeah, can you map it and force a failure in flow to see what you get?

13

I did, I don't get anything.

14

Can you invite me to the account? It's there in my testing.

15

Invite Sent

16

I looked into it and see what's going on. We have a backlog item to populate _json with the response body even when there's an error. Right now, the XML response is getting placed into errors.0.message as raw XML.

To work around this, I mapped errors.0.message back into your data, then used Celigo’s internal API to convert the XML to JSON. This is an undocumented endpoint (which we might want to officially document now) that accepts XML and returns JSON.

The image shows an interface for editing response mapping with fields for importing a response and source record fields. (Captioned by AI)
The image shows an interface for editing response mapping with fields for importing a response and source record fields. (Captioned by AI)2218×812 30.9 KB

The image shows a configuration interface for editing an HTTP lookup, using POST method and JSON request body with a resource path. (Captioned by AI)
The image shows a configuration interface for editing an HTTP lookup, using POST method and JSON request body with a resource path. (Captioned by AI)1572×1338 155 KB

The image shows a settings interface for configuring non-standard API response patterns with fields for defining the path to records and error fields in the HTTP response body. (Captioned by AI)
The image shows a settings interface for configuring non-standard API response patterns with fields for defining the path to records and error fields in the HTTP response body. (Captioned by AI)1506×614 36.5 KB

The image shows a data transformation interface with fields and JSON-like input and output sections, focusing on fault codes and messages. (Captioned by AI)
The image shows a data transformation interface with fields and JSON-like input and output sections, focusing on fault codes and messages. (Captioned by AI)3038×1476 323 KB

The image shows a software interface for editing results mapping, displaying rules alongside JSON input and output sections. (Captioned by AI)
The image shows a software interface for editing results mapping, displaying rules alongside JSON input and output sections. (Captioned by AI)3040×1588 378 KB

2 Likes
17

That's working! Thank you for all of your help!