Suggestion on mapping Integration response

RE: Suggestion on mapping Integration response

Mike Schmitt — Thu, 29 May 2025 12:00:04 GMT

great, thanks for confirning - would appreciate a 'verify' if/when you get a chance, too.

RE: Suggestion on mapping Integration response

poojithak2926 — Wed, 28 May 2025 22:51:26 GMT

i tried this it did not work

RE: Suggestion on mapping Integration response

poojithak2926 — Wed, 28 May 2025 22:50:49 GMT

Wow! Thanks a lot for this explanation🙂.Considering your suggestions i have build the below code and its working in all possible conditions.

a!localVariables(
local!body: if(
a!isNotNullOrEmpty(ri!integrationResponse),
a!fromJson(
index(ri!integrationResponse, "body", null)
),
{}
),
{
if(
a!isNotNullOrEmpty(local!body),
property(local!body, "jobId", null()),
{}
)
}
)

RE: Suggestion on mapping Integration response

gayathrik6397 — Wed, 28 May 2025 14:16:41 GMT

Good explanation.

RE: Suggestion on mapping Integration response

Mike Schmitt — Wed, 28 May 2025 12:25:58 GMT

You need to step through this piece by piece to understand what's actually going on.

Firstly we can see that the "body" you're getting back is a JSON string (I can see you're already trying to treat it as JSON but just reiterating here for clarity).

So when "body" is populated, we will want to translate it back from JSON, which of course results in a dictionary:

Now of course, as with all dictionaries/CDTs/maps, if we want only the property within the dictionary, we actually have to retrieve the value of that property (Even when the entire dictionary only holds one property). For this, dot property would work, but if there's ever a chance it would be empty, it would be safer to use property(). (Note as always: property() and index() are the same function in the back-end; but my personal best practice is to use property() for properties, and index() for indices [i.e. positional within an array], for code cleanliness and readability).

Side note: if you're passing the "body" value directly into a!fromJson(), then your null-safe returned value should be something that doesn't cause a!fromJson() to crash - I've found "[]" or "{}" work well. It will error on you if you pass it null().

RE: Suggestion on mapping Integration response

David Jimenez — Wed, 28 May 2025 08:06:20 GMT

You need to add one more index if you want to recover jobId value from the response.

index(index(ri!integrationResponse, "body", null), "jobId", null)

RE: Suggestion on mapping Integration response

sarathkumar13 — Wed, 28 May 2025 06:01:07 GMT

Please try the below code

index(index(ri!integrationResponse, "body", ""), "jobId", "")

RE: Suggestion on mapping Integration response

VarunTejaGurrapu — Wed, 28 May 2025 05:57:05 GMT

Hi poojithak2926 ,

I would suggest you to create a rule and use the integration in the following way:

rule!ABC_FormatData(ri!response : ri!integrationResponse)

a!localVariables(
  local!data: split(
    index(
      ri!response,
      "body",
      {}
    ),
    ":"
  ),
  local!jobId:index(local!data, 2, {}),
  left(local!jobId,count(char(code(local!jobId)))-1)
)

RE: Suggestion on mapping Integration response

Harsha Sharma — Wed, 28 May 2025 05:47:52 GMT

Did you try this?

if(
a!isNotNullOrEmpty(ri!integrationResponse),
a!fromJson(
index(ri!integrationResponse, "body","jobId" null),
),
{}
)