Tablora

Tablora · Library

Stop when a quoted field never closes

A quote that opens a CSV field but never closes makes the rest of the text ambiguous. The inspector rejects it so you fix the source first.

Why one missing quote breaks everything after it

In CSV, an opening quote tells the reader that everything up to the matching closing quote belongs to one cell, including commas and line breaks. If the closing quote never arrives, the reader cannot know where the cell was meant to end. Every following delimiter and line break could be part of that one value, or none of them could.

Some tools guess and swallow the rest of the file into one cell. The inspector does not. It rejects the text with Check the entered values and try again, so you see the problem before any rows are built from a guess.

The unfinished note example

The page example has a header id,note and a record 1,"unfinished with an opening quote and no closing one. With comma as the Delimiter, the expected outcome is that the unfinished quoted field is rejected: no preview, no row count and no download. With Detect delimiter selected the result is the same, because none of the supported delimiters can parse the text.

Typical causes

Fixing the source copy

Do not close it at the end

Adding a closing quote at the very end of the text makes the error disappear, but turns everything after the opening quote into one cell. The inspector would then report fewer rows and a single oversized note. Put the quote where the field really ends.

Original synthetic example

Input
id,note 1,"unfinished
Delimiter
,
Expected outcome
The unfinished quoted field is rejected.

Tools

Sources