Audit a Semicolon-Delimited Export Before Import

Switch delimiter settings, inspect a synthetic product table, and confirm the parsed columns before reusing a regional export.

By DevSphere Editorial · · 5 min read

Open CSV Tools

Recognize the delimiter mismatch

A comma-based CSV viewer can make a semicolon-delimited file appear to have one oversized column. CSV Tools exposes a Delimiter selector with comma, tab, semicolon, and pipe choices, plus a quote character selector and a First row is header checkbox. This is a practical way to inspect small text exports before importing them, but it does not infer a locale or guarantee strict CSV conformance. Use fictional product data and check the file's documented export settings. Here a demo supplier uses semicolons and double quotes. The workflow is to choose the delimiter, verify header interpretation, inspect a quoted field, and compare the resulting row and column counts with expectations. Do not copy real supplier pricing or internal item codes into an unapproved environment.

code;item;price;note
P-01;Demo Mug;6.50;sample stock
P-02;Desk Tray;12.00;"seasonal; display"

Set parsing options first

Open CSV Tools and replace the example text in CSV Input with the sample. Set Delimiter to Semicolon and leave Quote as Double quote. Keep First row is header checked. The table should show four columns named code, item, price, and note, plus two data rows. The statistics above the editor report rows, columns, and cells; check them against the expected two records and four fields, which make eight data cells. If the count is off, confirm the delimiter and quote character before changing the source. The parser recognizes doubled quote escapes and keeps a delimited segment together while inside quotes, but it trims the resulting field text. Empty lines are skipped when they contain no nonempty fields. These choices may not match every CSV dialect, so document the originating convention.

Inspect quoted values in Table View

Leave Table View active to inspect rows in a grid. The semicolon inside seasonal; display should remain part of a single note cell because the field is quoted. Click a column header to sort by that column; clicking the same header again reverses the sort direction. Sorting tries numeric ordering when both values parse as numbers and otherwise uses locale string comparison. For a table with prices, this can help find high or low values, but imported values are initially strings and mixed formatting may not sort as expected. Enter a distinctive term in Filter rows to show rows containing it anywhere in the row, then check Showing n of m rows. Filtering does not alter the underlying CSV input or the JSON and SQL conversions. Clear the filter before judging total data.

| code | item      | price | note              |
| P-01 | Demo Mug  | 6.50  | sample stock      |
| P-02 | Desk Tray | 12.00 | seasonal; display |

Understand conversion behavior

The JSON tab converts each row into an object using the chosen headers. It attempts to convert exact true and false strings to booleans and numeric-looking cells to numbers. This inference is convenient for samples but can damage identifiers such as 001 or account-like codes with leading zeros; inspect them before using JSON output. SQL creates INSERT statements, with a Table Name field initialized to data. Its value escaping handles single quotes in values and emits simple numbers and booleans without quotes, but table and column identifiers are inserted directly and should never come from untrusted input. Generated SQL is a draft, not an execution plan. The tool has no database connection and does not check the destination schema, SQL dialect, constraints, or permissions.

Verify, export, and troubleshoot

Confirm the two product codes, prices, and note strings against the original before copying or downloading a result. The JSON tab includes Copy and Download; SQL has its own controls, and Table View can be used to spot an anomalous value. If all data appears in one column, reselect Semicolon. If quoted content splits unexpectedly, confirm the double-quote setting and inspect balanced quotes. The parser is a lightweight character-by-character implementation, not a complete CSV standards validator; it does not report robust row-level diagnostics for malformed quotes and trims whitespace around fields. For strict ingestion, validate with the same library used by the target system. Use Clear in the input section between files, and keep the original export so any formatting or type inference can be reviewed.

Before handing the table to another team, document the delimiter and quote character. A recipient may default to comma even if the file is semicolon-separated, creating a misleading single-column preview without changing the source text. The row and column counts are a quick checksum for this sample, but a larger delivery should also be checked for rows with missing or extra fields. This interface trims fields and skips wholly empty lines, so it cannot preserve every whitespace convention. If trailing spaces are significant or blank lines represent records, choose another parser with an explicit dialect policy. Keep a raw backup and compare a representative row after importing it into the destination.

The semicolon inside the quoted note is a useful diagnostic because it should not create a fifth column. If it does, inspect the quote setting and confirm the opening and closing double quotes survived copying. Also check a row with an empty final field if your supplier export may include one; CSV parsers often differ in how they present that trailing blank. The table preview is convenient for finding obvious shifts, but it does not highlight row-width inconsistencies with a detailed error report. For important imports, compare the number of fields in every source record with the header width and use the exact parser that the destination will run. This prevents a plausible-looking first row from masking a bad record later in the file.

Browse all tutorials