Showing results for 
Search instead for 
Did you mean: 
Resolver III
Resolver III

Custom connector - query parameters are HTML-encoded, resulting in errors

I have a custom connector that I built that was returning errors when I tried to use a sort token (provided by the API) to paginate through the results.


A few tests revealed that the problem was that the sort token sometimes included a percent sign (%), and Flow was encoding the query parameter for HTML, changing it from '%' to '%25'. 


Here is a screenshot of a test - as you can see, the sort token includes a couple of percent signs, all of which are changed by Flow to %25, and as a result the test fails.




Helpful resources

Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

Top Solution Authors
Users online (9,846)