how to escape special characters in POST json body defined via custom connectors?

(0) Share

Report

Posted on by SunnyTokyo

Hope we get some clue on the problem below.. We have succeeded,

1. creating a custom connector to POST to solr database outside azure.

2. and tested the API on the custom connector through 200 success with correct a response. The successful json request body looks like this on custom connector's "test" tab;

when "raw body toggle button" is on => "{ \"solr_query\": \"text_headline: today is a sunny day\" }"

when "raw body toggle button" is off => { "solr_query": "text_headline: today is a sunny day" }

But, when we go back to canvas app and put a button with the below function. It fails with limited error message.

Set(var_parts_solr_records,solrCallFunctionApi("text_headline: today is a sunny day"))

I'm assuming there should be some automated interpretation of ":" even in "string" area. Some workaround of escaping the character would be very appreciated!

Categories:

Building Power Apps

All responses (4)

Answers (2)

Sort by

Verified answer

RandyHayes 76,299 Super User 2024 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

@SunnyTokyo

You might want to consider using the EncodeUrl function on your text to help in your scenario.

Beyond that, you would need to utilize the substitute function to make specific changes in the text.

I hope this is helpful for you.
Verified answer

Prakash4691 1,332 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @SunnyTokyo ,

Try, Text("text_headline: today is a sunny day")

Regards,
Prakash
SunnyTokyo 29 on at

Like
a
(0)

Report
Copy link

Link copied!

@Rani @Prakash4691 thank you for the reply. We tried the both and were helpful on the topic. One thing I noticed was when we post double quate("") or backslash(\) from powerapps to flow or to logic apps even in the json body text area, it causes automatic adding of some escaping strings. So we switched the whole idea into substituting all the "\" into "/" until we finally need to utilize the original string. Looks like it's JSON side restriction.
gy2023 2 on at

Like
a
(0)

Report
Copy link

Link copied!

maybe this tools will be helpful as well URL ENCODE ONLINE