[422] Invalid Parameter despite filtering out bad character
I have a scenario that ends in a custom API to do a POST call.
It's throwing an occasional "[422] Invalid Parameter" error. Apparently, some users are pasting control characters (namely TAB) into task names and when fusion throws them into the JSON response it's failing.
I've tried using the ascii() function, which seems to strip the character out, but the error is still being thrown, which I don't understand at all.
Thoughts?
