AnsweredAssumed Answered

Weird Encoding issue with building a string value

Question asked by janp on Oct 22, 2015
Latest reply on Oct 26, 2015 by janp

I'm not sure if I should post this as a bug or not. I hesitate to but I found it a pain in the ... so I thought I'd share and possibly learn more about the process.

 

In a workflow I built, I needed to combine a couple of strings together and then add them to a general body of text that would then be exported to a CSV file via the Web Request action. All worked well except that some of the strings had an  in them.

 

example: max. size of 200Â mm

 

These particular strings were created by combining strings using the Set Variable Action = max. size of {workflow variable:max size} mm

It seems that while using that control (set variable) for strings, it does not use utf-8 charset. (I guess that's because it's not just for strings)

 

Using the Build String Action resolved the issue which leads me to believe that's the proper/intentional way to set any string variable (especially when combining strings).

 

Is this intentional?

Outcomes