Forum Discussion
Josh_147
5 years agoContributor
Hi AlexKaras
This is the update regarding this issue.
I had asked the Support, after they pasting the non-printable character into a text field in their sample table app reproduces the issue.
They had reported it to the developers and it will be fixed in one of the future releases based on the general backlog order.
AlexKaras
5 years agoCommunity Hero
Hi,
Thank you for the update!
> it will be fixed
Didn't they mention what the fix will be? Are they going to store all data, including non-printable characters, and compare considering these characters, or just skip non-printable characters, or something else?
- Josh_1475 years agoContributor
Hi,
Yes, they didn't mentioned the method to fix it. Sorry about that.