6� bug

Mike,

I have run into this with various "special" (very common) characters entered on Apple devices, though I don't recall exactly what characters were affected in addition to quotes. I believe it has to do with how Apple encodes some characters. Interestingly, the conversion of quotes and apostrophes I've seen gives a different text string than yours (see below). Our users are using iPads to collect the data, perhaps different devices encode the characters differently. Just something to keep an eye on in case you see multiple conversion strings for the same characters within your applications.

I have a solution that, while not fixing the source of the issue, works for our purposes. If you are importing the data, do not display the imported field containing the converted characters. Create a second field that has a formula to SearchAndReplace() the converted text back into the intended characters. If you have multiple characters you need to replace, you can nest multiple instances of this formula inside itself. Of course, if you have multiple fields that include these special characters, you will need the same number of "correction" fields.

I've included an example of one of my formulas below. If any of your conversion strings also contain special characters like mine did, I suggest copying and pasting the string directly from your field instead of trying to insert the characters manually, as for some reason it doesn't always recognize the match otherwise.

var text corrected =
SearchAndReplace(
     SearchAndReplace(
          SearchAndReplace([Imported Text Field],"’","'"),
     "”","\""),
" ,","");

------------------------------
Oana Toma
------------------------------