Power Platform Community Forum Thread Details

I was adjusting a previously tested power automate cloud flow. At a certain point I concatenate multiple strings.

I added some steps AFTER the concatenation.

The result concatenated string somehow changed to URI encoded, after the flow edit. I checked the concat function,

here is the entire concat function : concat(outputs('Get_item')?['body/RecID'],'_',outputs('Get_item')?['body/TitleOrigin'])

I checked the inputs, recreated the concatenation with a new variable - the result string for a new variable was NOT URI encoded, which is correct.

To my disbelief, it seems that power automate somehow added the URI encoding on his own and didnt show in the expression window, it showed with Peek code:

so my question pretty much is - "what the frick???" is there any way power automate could have added this encoding on his own, in regard to an operation added AFTER the concatenation itself???

I did ad an encode and decode URI component expression further in some flow steps, but certainly not this one...

Thank you kindly for any explanation.

Categories:

Building Power Apps

@PeterKo ,

might just be a shot into the sky....
Technically each and every connector action respectively trigger is based on certain HTTP actions.
We just get a look on a nicely wrapped present.

Personally, even though I`d somehow expect a concatenate to cast the input as data type string, your example originates from a HTTP get post against SharePoint.
It might slip through any interpreter that you do not intend to pass it along further on other potential HTTP methods (or it has been just a bump on the road of some Intellisense within the browser...have not tried to reproduce this).
How about putting the value into a compose action first? Worst thing that presumably could happen is getting an array in return under specific conditions.