set-body policy gives error when saving when body has { } , but still works

Question

<policies>
    <!-- Throttle, authorize, validate, cache, or transform the requests -->
    <inbound>
        <base />
        <choose>
            <when condition="@(1==1)">
                <set-variable name="newaccesstoken" value="TOKENNOTFOUND" />
                <return-response>
                    <set-status code="401" reason="Unauthorized" />
                    <set-body>{"QueryString": "123", "param1": "4567"}</set-body>
                </return-response>
            </when>
            <otherwise>
                <set-variable name="newaccesstoken" value="SOMEOTHERREASON" />
            </otherwise>
        </choose>
    </inbound>
    <!-- Control if and how the requests are forwarded to services  -->
    <backend>
        <base />
    </backend>
    <!-- Customize the responses -->
    <outbound>
        <base />
    </outbound>
    <!-- Handle exceptions and customize error responses  -->
    <on-error>
        <base />
    </on-error>
</policies>

My policy looks like this (never mind the logic of this policy. I wanted to simplify the error I am seeing). In the set-body I am doing a json . While saving the policy it gives me an error that there is a formatting error. see attachment. However I go ahead and click ok to save it. The policy works as expected and I get the json response. What can I do to avoid this error message when saving the policy ?

Answer 1

@Martin Kallukalam Thanks for reaching out. While the policy saves successfully, the warning indicates that the syntax is not fully compliant with the expected format for dynamic expressions.

To avoid the warning, you should use the correct syntax with the expression enclosed in parentheses, as shown in the corrected policy:

<set-body>@(new JObject(new JProperty("QueryString", "123"), new JProperty("param1", "4567")).ToString())</set-body>

This ensures that the expression is properly evaluated and avoids any potential issues during runtime.

do try and let me know incase of further queries, I would be happy to assist you.

Answer 2

@JananiRamesh-MSFT It sitll gives me error (different error). I copy pasted exactly as you suggested

Answer 3