Tables Limits & Importing CSVs đź“ť

Announcements
6

Possible Bug – CSV Import Doesn’t Respect Quoted Fields Containing Commas

Description:

When importing a CSV file into an ActivePieces Table, fields that contain commas are being incorrectly split across multiple columns, even when those fields are properly enclosed in double quotation marks, as per standard CSV formatting. (And, if you manually add quotes, they double up on import, as I assume AP already adds these by default?)

Steps to reproduce:

  1. Create a CSV file with values such as:
    URLs,Titles,Descriptions,Name
https://example.com,Test Page,"This is a test, with commas",Test
  2. Import it into a Table via the CSV Import feature.
  3. Map the columns accordingly.
  4. Observe that the “Descriptions” field is split at the comma, and the portion following the comma is incorrectly placed into the next column — despite being within quotation marks.

Expected behaviour:
The CSV parser should treat any field enclosed in double quotation marks (") as a single value, even if it contains commas — which is the expected behaviour based on CSV standards.

Actual behaviour:
The parser appears to split fields on every comma, including those within quoted fields, resulting in broken imports and misaligned data.

Suggested resolution:
Please update the CSV parser used for Tables to correctly support quoted field logic (in line with RFC 4180). Specifically:

  • Fields enclosed in double quotes should be treated as one unit.
  • Escaped quotes ("") within fields should be parsed correctly.

Impact:
This makes it very difficult to import any descriptive text such as descriptions, product details, or content that naturally contains commas. It’s currently a major limitation when working with real-world CSV data.

Kind regards,

3 Likes