Invalid char in UTF-8 string on Report Table took with version 2022.3

[MsBindy]

Yesterday I upgraded to 2022.3 and I'm starting to get an Invalid char in UTF-8 in my table tool.....and the output acts oddly with another tool too.

But if I run the same workflow in 2022.1  it's totally fine.  

Has anyone else encountered this?

[FinnCharlton · Accepted solution]

Hi @MsBindy,

Firstly I would check if you are using the AMP Engine, for some reason it can cause this error.

You could also try getting rid of those invalid characters before the table tool using the formula: DecomposeUnicodeforMatch([String]).

[MsBindy]

oh wow!    turning off the AMP engine totally worked.  Thank you.   I spent hours yesterday trying to find the invalid character.

[MavStar]

Hi there - revisiting this issue as I have exactly the same problem and when turning off AMP engine there's no issue.

However, when using certain Connectors and pushing the flow into online Gallery, AMP engine is considered mandatory.

Any ideas how to resolve the UTF error without turning off AMP engine?