Has anyone else found that the SEARCH and FIND formulas count unicode characters (like emojis) as two positions within a string, as opposed to one position. This means that both functions seem to return the incorrect index if the matching string starts after any unicode chars in the text to search.
Short of stripping out any unicode characters, does anyone have ideas for other workarounds?
I ran into this problem the other night and was tearing my hair out! I did find that the LEN() formula saw the emoji as one character and gave me the expected result for the length of the string as a whole… you might be able to use that to somehow adjust your calculations depending on what you need the end result to be.
That being said, I’m not sure how consistent this is across formulas/emojis/characters/maybe even browsers :frowning: