Skip to main content
Question

Pipelines not running due to Mixed Encoding issues

  • September 21, 2023
  • 0 replies
  • 164 views
MattMakris
Forum|alt.badge.img+7

Some pipelines all of the sudden stopped working for certain tables last month. Support said it's due to a mixed encoding issue and that I'd have to run the Mixed Encoding Scanner. It uncovered over 5,700 rows with issues across dozens of fields - trademark symbols, curly single quote characters, and other basic characters tripping the errors. I don't have the ability to manually fix these or even do find/replace on each table/field. Is there any way around this? This seems crazy that the platform cannot support a trademark symbol.



------------------------------
Matt Makris
------------------------------
    This topic has been closed for replies.

    Forum|alt.badge.img+11

    or Indian currency symbol 



    ------------------------------
    Prashant MaheshwariPrashant Maheshwari
    ------------------------------
    Forum|alt.badge.img+7
    • KimG
    • Registered
    • September 27, 2023

    I don't really have any good answers for you, but feel your pain. We also have run into this issue with pipelines. 

    Also we have old notes that are now filled with diamond question marks where a curvy apostrophe or quote, or a micron symbol once was. Sometimes I'm not quite sure what the character originally was.  We also have thousands of these so it's not possible to fix them all. I was able to fix issues in a couple of tables that only had a few instances, but not in all the tables. 

    One thing I would check is to see if you have any of these characters in the field names of the tables, because I think removing them from field names can make a difference even if the data itself holds these "special" characters.  



    ------------------------------
    Kim G
    ------------------------------
    Terms & ConditionsAccessibility statement