I have seen this posted elsewhere but there wasn't any response, so I thought I'd post again with some additional examples.
I'm experiencing problems with the REST step in Flow Design Actions in that it is corrupting the parameters making the URL potentially unreadable by the end point provider. Initially I though it was due to the use of data pills, but I've ruled this out.
Here's an example, the REST query parameters are defined using Data Pills, aside from one which is typed in by hand;
When the action is tested, the query parameters look like this;
Notice the red dots in the coordinates value, and the language.
When placed in a hex editor, the dot reveals itself as #EF #BB #BF
So, why is this being added. As it's part of the REST step you don't get a chance to parse it, but why should you need to especially if the parameter isn't even coming from a data pill.
I'm running the latest available version of San Diego in my PDI.
Updated
I ran a further test to build the query parameter using an inline script
var coordinates = [fd_data.action_inputs.longitude, fd_data.action_inputs.latitude].join(',');
return coordinates;This fixes the issue, so if you look at the JSON below you'll see 'coordinates' is correct as that has been generated by script, but 'coord2' is incorrect as that comes from the data pill.
Another Update....
It also seems like the rogue characters can be added to the query parameter name as well 😞
But, the fix for the values is to use the inline script and perform some kind of string manipulation.
