Parsing json array in liquid template

siva pokuri 21

I have been facing issues with the looping to iterate through the JSON array and create XMLHere is my sample -

{ "userPriority": "Medium", "fileAttachment": [{ "fileExt": "", "fileName": "", "fileBase64": "" }] }, "sharedList": { "contact": [ { "userId": "pokuri" }, { "userId": "sam," } ] } } Here is the policy -

<SharedList>
{% for contact in body.Document.SharedList.Contact %} <Contact>{% if contact.userId %} <UserId>{{ contact.UserId }}</UserId> {% else %} <UserId>Empty</UserId> {% endif %} </Contact> {% endfor %} </SharedList>

Here is my liquid template transformation for Azure APIM policy. However, in the trace, I see that the policy below does not read array attributes.

Please let me know if I have to correct anything in the policy.

Thanks

Siva Pokuri.

Khadeer Ali 485 Reputation points Microsoft Vendor

2024-10-07T05:04:01.3566667+00:00

Hi @siva pokuri

Thanks for reaching out to Microsoft Q&A.

It looks like Case Sensitivity issue. In Liquid, the property names are case-sensitive, so ensure you use sharedList and contact as per your JSON structure (lowercase).

If the answer is helpful, please click "Comment" and kindly upvote it.
Khadeer Ali 485 Reputation points Microsoft Vendor

2024-10-08T01:07:15.1133333+00:00

hi @siva pokuri ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
siva pokuri 21 Reputation points

2024-10-08T01:27:20.6566667+00:00

Hi Khadeer,

Issue is sorted. I had to changed the way reading the array. Solution is that instead of looping through the contact I had to loop through the Sharedlist and then read the contacts.

Thanks

Siva Pokuri

Share via

Parsing json array in liquid template

Your answer