A lengthy session of root-cause analysis found that scraped data was including a non-visible, non-identifiable "space-like" character, at the beginning of text strings. This deceptive character is immune to the TRIM function, as it is not considered a space. (I wasn't able to copy it, and search/replace as it didn't interpret the character accurately on copy.) The impact was quite frustrating because:
- the invisible nature of the character (the fact that it couldn't be "seen" by human-eyes) &
- that the character could be seen and interpreted programmatically, led to
- an unclear failure when performing an Index-Match-Lookup to match columns across multiple data scrapes.
Love the extension, other than in times of frustration :) Thank you for your clearly arduous, time intensive & highly appreciated efforts! Hope you can find a little time to clear this for others.
A lengthy session of root-cause analysis found that scraped data was including a non-visible, non-identifiable "space-like" character, at the beginning of text strings. This deceptive character is immune to the TRIM function, as it is not considered a space. (I wasn't able to copy it, and search/replace as it didn't interpret the character accurately on copy.) The impact was quite frustrating because:
Love the extension, other than in times of frustration :) Thank you for your clearly arduous, time intensive & highly appreciated efforts! Hope you can find a little time to clear this for others.