Bug/Feature: Improve Handling of CSV Files with Different Delimiters

[isaquepim]

Currently, the application only supports CSV files that are comma-separated (,).

However, many CSV files — especially those generated in certain locales (e.g., Excel in some regions) — use semicolons (;) as delimiters.

Problem

When a user uploads a CSV file separated by ;:

• The upload may succeed without errors
• The file is parsed incorrectly
• The user receives no clear feedback about what went wrong

From the user’s perspective, it is unclear why the data is malformed or broken.

(ou como aconteceu aqui na SES, o usuário achou que era caracter estranho quebrando o OLIM. Corrigiu isso, mas voltou a ter erros e começou a achar que os dados estavam muito grandes. No fim o arquivo era separado por ;).

Expected Behavior

If the system only supports comma-separated CSV files, it should:

• Detect incorrect delimiters
• Show a clear and actionable error message

Example:

Invalid CSV format. Only comma-separated (,) files are currently supported.

Proposed Improvements

Option 1 — Validation Only

• Detect delimiter before parsing
• Reject unsupported formats with a clear error message

Option 2 — Automatic Delimiter Detection (Preferred)

• Automatically detect delimiter (, vs ;)
• Parse accordingly

Option 3 — User-Selectable Delimiter

• Add a delimiter selection field during upload
• Default to auto-detection

Benefits

• Improves user experience
• Reduces confusion during upload
• Prevents silent parsing errors
• Makes the application more robust across regions