> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/tutorials/components/csv-parser/fix-encoding-and-delimiter-issues.md).

# Fix encoding and delimiter issues

Diagnose a CSV file that imports wrong (garbled accents, one giant column, a title row) and fix it with the CSV Parser's Parser settings.

Your events team comes back from a trade show in Lyon with the badge-scanner export. The file opens fine in Excel, but in the flow the names read `Zo� Lef�vre` and every column is squeezed into one. Nothing is wrong with the leads: the file was saved by Excel on a European laptop, with semicolons and without UTF-8.

This page shows how to find out what is wrong with a file and which setting of the [CSV Parser](https://docs.avonnicomponents.com/flow/flow-components/csv-parser.md) fixes it, before anyone imports a single lead.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FrO5Sqd8pqGXnuXsmx6XP%2Fcsv-fix-encoding-and-delimiter-issues-result.png?alt=media" alt="The CSV Parser after uploading a semicolon file saved in ISO-8859-1, with Encoding set to ISO-8859-1: Found 5 rows, five columns mapped to First Name, Last Name, Company, Email and Country, and accented names such as Zoé Lefèvre and Kühlkette Süd GmbH reading correctly."><figcaption><p>With Encoding set to ISO-8859-1 and Delimiter set to ;, the European export reads correctly.</p></figcaption></figure>

## Before you start

* A screen flow with a CSV Parser on a screen. If you have not built one yet, start with [Import a CSV file in a screen flow](https://docs.avonnicomponents.com/flow/tutorials/components/csv-parser/101-tutorial.md).
* The file that causes the problem, saved on your computer. Diagnose with the real file, not a clean sample.
* The file must have the `.csv` extension. The upload button only accepts `.csv` files, so an `.xlsx` workbook cannot be picked: save it as CSV from Excel first.

Here is the file used on this page. In the original it is semicolon-separated and saved in Western European encoding (ISO-8859-1), which is what Excel's plain "CSV" format often produces on a French, German or Spanish computer:

```csv
FirstName;LastName;Company;Email;Country
Zoé;Lefèvre;Atelier Rhône Logistique;zoe.lefevre@rhone-logistique.example;France
Jürgen;Häusler;Kühlkette Süd GmbH;j.haeusler@kuehlkette-sued.example;Germany
Inés;Álvarez;Tránsitos Ibéricos;ines.alvarez@transitos-ibericos.example;Spain
Søren;Brønd;Nordhavn Fragt;soren.brond@nordhavn-fragt.example;Denmark
Chloé;Müller;Genève Cargo Services;chloe.muller@geneve-cargo.example;Switzerland
```

## Steps

{% stepper %}
{% step %}

### Open the Component Builder and turn on the two checks

1. In Flow Builder, open the screen and select the CSV Parser on it.
2. In the panel on the right, click **Open Component Builder**. The **Edit CSV Parser Component** window opens with a live preview on the left and the settings on the right.
3. In the **Properties** tab, turn on **Show Row Count** and **Show Preview**.

**Show Row Count** prints the number of data rows the component read, for example `Found 5 rows.` **Show Preview** adds a **Preview** section (collapsed at first: click it to open) with the first three rows, already converted to the Salesforce fields they are mapped to. Together they tell you whether the file was read correctly.

{% hint style="info" %}
The Parser settings live in the Component Builder only. The panel on the right of the screen editor shows the main settings (Label to Show Row Count), not the **Parser** or **Save As Content Document** groups.
{% endhint %}
{% endstep %}

{% step %}

### Upload the problem file in the preview

In the preview, click **Upload Files** and pick the file. The preview behaves like the real component: you see the **Mapping** section with each column header, the first values of that column under it, and the row count.

Compare what you see with the file:

* The row count matches the number of data rows (the header row is not counted, empty lines are skipped).
* Each column of the file appears as its own header in **Mapping**.
* The sample values under each header read correctly, accents included.

If one of these is off, find the symptom in [What you see and what fixes it](#what-you-see-and-what-fixes-it) below.
{% endstep %}

{% step %}

### Change one Parser setting

Scroll to the **Parser** group in the **Properties** tab. Click it to expand it if it is collapsed: a group that already holds values opens by itself. Change only the setting that matches your symptom, for example **Encoding** or **Delimiter**. To force a separator, type it in **Delimiter**; use **Delimiters To Guess** to narrow the candidates the parser tries when **Delimiter** is blank.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2F9LKvL7FLb66aJETmdoXW%2Fcsv-fix-encoding-and-delimiter-issues-parser-group.png?alt=media" alt="The Parser group of the Edit CSV Parser Component window, expanded: Comments, Delimiter set to a semicolon, Delimiters To Guess, Encoding set to ISO-8859-1, Escape Character, Fast Mode off, New Line and Quote Character." width="320"><figcaption><p>The Parser group, with Delimiter and Encoding set for a European Excel export.</p></figcaption></figure>
{% endstep %}

{% step %}

### Upload the file again

The component reads the file at the moment it is uploaded, so a new setting has no effect on a file already in the preview. Upload the same file again and check the three points of step 2 one more time.

If it is still wrong, undo that change before you try the next one. Two settings changed at once make it hard to tell which one fixed the file.
{% endstep %}

{% step %}

### Save and test

1. Decide whether your users should keep seeing the row count and the preview. Both are useful on a real import screen; turn them off if you prefer a shorter screen.
2. Click **Done**, save the flow and run it with the real file.

The screen shows the same result as the preview: accents readable, one header per column, and the row count matching the file.
{% endstep %}
{% endstepper %}

## What you see and what fixes it

<details>

<summary>Accents come out as <code>�</code> (Zo� Lef�vre)</summary>

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FmdJMMJ26puHplsmzR6qg%2Fcsv-fix-encoding-and-delimiter-issues-garbled.png?alt=media" alt="The same file uploaded with the default encoding: Found 5 rows and five mapped columns, but every accented letter shows as a replacement character, for example Zo� and Lef�vre."><figcaption><p>Read as UTF-8, every accented letter of an ISO-8859-1 file turns into a replacement character.</p></figcaption></figure>

**Cause:** the file is not saved as UTF-8. The component reads uploaded files as UTF-8 by default, and characters such as é, á or ü stored in another encoding cannot be read that way.

**Fix:** in the **Parser** group, set **Encoding** to **ISO-8859-1 (General US & Western Europe, ISO-LATIN-1)**. This is the right choice for most files saved by Excel's plain "CSV" format on a Western European computer. For files from Japan, China or Korea, pick the matching option in the same list, for example **Japanese (Shift-JIS)** or **Korean (EUC-KR)**.

**Better long term:** ask whoever produces the file to save it with Excel's "CSV UTF-8" format. A UTF-8 file works with the default setting, **Unicode (UTF-8)**, and you can leave **Encoding** alone.

</details>

<details>

<summary>Accents come out as two characters (ZoÃ© LefÃ¨vre)</summary>

**Cause:** the opposite case. The file is UTF-8, but **Encoding** is set to another value, often **ISO-8859-1**, left over from an older file.

**Fix:** set **Encoding** back to **Unicode (UTF-8)**.

</details>

<details>

<summary>Mapping shows a single header with the whole first line in it</summary>

**Cause:** the component did not split the columns on the right character. When **Delimiter** is blank, the component guesses it from comma, tab, pipe and semicolon, and the guess can be wrong, for example on a semicolon file whose values also contain commas (decimal amounts such as `12,50`). A **Delimiter** set to `,` on a semicolon file gives the same result.

**Fix:** set **Delimiter** to the character the file actually uses, for example `;`. A European Excel export is almost always `;`.

</details>

<details>

<summary>The first header is a title such as "Booth leads, Lyon 2026"</summary>

**Cause:** the component always takes the first line of the file as the header row. A title or a note above the real headers becomes the header, and the real column names turn into a data row.

**Fix:** delete the title rows in the spreadsheet and save again. If the export tool writes notes on lines that all start with the same marker, for example `#`, set **Comments** to that marker instead: every line starting with it is skipped.

</details>

<details>

<summary>A company name with a comma is split across two columns</summary>

**Cause:** a value that contains the delimiter must be wrapped in quotes, like `"Becker, Sons & Co"`. The component reads quoted values correctly by default. It goes wrong in two cases:

* the file uses another quote character, for example single quotes;
* **Fast Mode** is on. Fast Mode only works on files with no quoted values at all.

**Fix:** turn **Fast Mode** off. If the file wraps values in another character, set **Quote Character** to it, for example `'`. If quotes inside a value are written `\"` instead of `""`, set **Escape Character** to `\`.

If the value is not quoted at all in the file, no setting can tell the comma from a delimiter: fix the export.

</details>

<details>

<summary>The file comes from Windows (or an old Mac) and the last column looks odd</summary>

Nothing to change. The component detects Windows (`\r\n`), Unix (`\n`) and old Mac (`\r`) line endings on its own, and removes stray line breaks from values. Leave **New Line** blank unless a file needs one sequence forced, in which case type `\r`, `\n` or `\r\n` there; any other value is ignored.

</details>

<details>

<summary>Amounts with a thousands separator are not read as numbers</summary>

**Cause:** when a column is mapped to a number, currency or percent field, the component accepts a decimal comma (`12,50` becomes `12.5`) and ignores spaces, `$` and `%`. A thousands separator is not understood: `1,250.00` or `1.250,00` is not converted to a number.

**Fix:** format the column without thousands separators before saving the CSV, for example `1250.00` or `1250,00`.

</details>

<details>

<summary>The row count stops at 10000 and a red message appears</summary>

**Cause:** the component processes at most 10,000 rows per file. Beyond that it keeps the first 10,000 and shows: `The uploaded CSV file exceeded the rows limit. Only the first 10000 rows were processed.`

**Fix:** split the file into several files of 10,000 rows or fewer. For a one-off bulk load or a data migration, use Data Loader.

</details>

<details>

<summary>The file comes from Salesforce Files, not from an upload</summary>

When the CSV Parser reads a stored file through **File Value**, it always reads it as UTF-8: **Encoding** only applies to files the user uploads. Convert a stored file to UTF-8 before saving it in Salesforce.

A stored semicolon file with no comma in any value is refused with `Could not parse the file value provided.` [Import a file stored in Salesforce](https://docs.avonnicomponents.com/flow/tutorials/components/csv-parser/import-a-file-stored-in-salesforce.md) lists the causes of that message.

</details>

## Related tutorials

* [Import a CSV file in a screen flow](https://docs.avonnicomponents.com/flow/tutorials/components/csv-parser/101-tutorial.md): build the import screen this page troubleshoots.
* [Pre-map CSV columns for a recurring import](https://docs.avonnicomponents.com/flow/tutorials/components/csv-parser/pre-map-csv-columns.md): once the file reads correctly, map headers such as "First Name" that do not match a field on their own.
* [Import a file stored in Salesforce](https://docs.avonnicomponents.com/flow/tutorials/components/csv-parser/import-a-file-stored-in-salesforce.md): read a CSV already in Salesforce Files with **File Value**.
* [CSV Parser](https://docs.avonnicomponents.com/flow/flow-components/csv-parser.md): every setting of the component.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avonnicomponents.com/flow/tutorials/components/csv-parser/fix-encoding-and-delimiter-issues.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
