Issue with French characters when previewing from FTP Source Tile

Integrator.io
, ,
1

Current process is we have an FTP folder where our dealers will drop their orders in json file format. Here is a sample data with French characters

[
    {
        "Customer Code": "2633",
        "PO": "M1C0000887",
        "Date": "2023/12/27",
        "Location": "1",
        "Ship To Addressee": "Test Dealer",
        "Ship To Attention": "",
        "Ship To Telephone Number": "999-999-9999",
        "Ship To Address 1": "à, è, ù",
        "Ship To Address 2": "â, ê, î, ô, û",
        "Ship To Address 3": "ë, ï, ü",
        "Ship To City": "Sainte-Adèle",
        "Ship To State": "QC",
        "Ship To ZIP": "J8B 0K1",
        "Ship To Country Code": "CA",
        "Notes": "This is a test dropship order, do not proceed",
        "Items": [
            {
                "Part Number": "999999-9999-99",
                "Qty": "1"
            }
        ]
    }
]

This is how it looks like when we preview the data in our FTP Source tile.

{
  "page_of_records": [
    {
      "record": {
        "Customer Code": "2633",
        "PO": "M1C0000887",
        "Date": "2023/12/27",
        "Location": "1",
        "Ship To Addressee": "Test Dealer",
        "Ship To Attention": "",
        "Ship To Telephone Number": "999-999-9999",
        "Ship To Address 1": "�, �, �",
        "Ship To Address 2": "�, �, �, �, �",
        "Ship To Address 3": "�, �, �",
        "Ship To City": "Sainte-Ad�le",
        "Ship To State": "QC",
        "Ship To ZIP": "J8B 0K1",
        "Ship To Country Code": "CA",
        "Notes": "This is a test dropship order, do not proceed",
        "Items": [
          {
            "Part Number": "999999-9999-99",
            "Qty": "1"
          }
        ]
      }
    }
  ]
}

I tried playing around with the file encoding options: UTF-8, UTF-16LE, and Windows-1252 to no avail.

Is there a fix for this issue that we are experiencing? Any advice is welcome and thanks!

2

Hi, Raul. I ran your question past a solutions consultant based in France, and he was unable to reproduce the issue with the JSON you provided above.

He did suggest re-uploading the sample file – and not placing the file on FTP – for your testing.
The 'preview' takes the sample file uploaded below:

5301043caa20740200000001-ae182015b1294015bb2217a0664bd8ff.png
5301043caa20740200000001-ae182015b1294015bb2217a0664bd8ff.png1502×618 27.8 KB

3

Hi Stephen,

I've tried one to no avail. I'm still getting those characters. Let me know if I'm missing a step. Thanks!

5301043caa20740200000001-55f51ff3def64d2693f6dd501c750d5d.png
5301043caa20740200000001-55f51ff3def64d2693f6dd501c750d5d.png874×442 147 KB

4

Hi @raulbernales,

Thank you for reaching out.

I tried creating a new export and uploaded a sample file that had French characters and I was successfully able to parse.

I suggest creating a new export trying to choose the file and doing a preview.

5301043caa20740200000001-586556616496472fb89a490f4bf303f3.jpg
5301043caa20740200000001-586556616496472fb89a490f4bf303f3.jpg2560×815 190 KB

UPDATED: It's a known limitation that the platform preview always uses UTF-8 encoding, and it's not possible to change the encoding in the interface itself. (Presumably, we were unable to reproduce the issue because we copied the text below from the Help Center Community, which also displays the UTF-8 character set.) We recommend proceeding with the assumption that the encoding that you selected in the export/import step is correct and then validating the end result in the app where the text values are imported.

5

Team: Just want to thank everyone for their help. You are all correct that there is nothing wrong on Celigo's end. The root cause of the problem was our dealer when switching their computer language from "Canada, French" to "USA English". Many thanks again for all your help and have a great day.

6

Thanks for the update, Raul. Glad to hear it.

For any other readers, too, I would like to point your attention to a similar report from a customer that was fixed in the January 17, 2024 (EU) release:

  • Export previews failed to properly display extended characters, resulting in missing data