CSV Decimal Commas: Preserve Field Boundaries Before Converting Numbers
A decimal comma can be valid numeric notation and still break a comma-delimited handover. Parse the file’s structure first, then apply the agreed numeric convention to the intended measurement columns.

Original conceptual illustration; not a live software screen, specific product or customer installation.
Key takeaways
Keep the original export unchanged.
Parse quotation and delimiters before numbers.
Reconcile typed values with the source.
1. Separate the delimiter from the number
The common CSV format described by RFC 4180 uses commas between fields and double quotes around fields containing commas. It is an informational description, not a guarantee that every exported file follows the same dialect.
A ProSight Software platform overview enquiry should include a representative source file and its declared format. Confirm the supported handover route before assuming a monitoring deployment accepts an arbitrary CSV export or regional number convention.
2. Preserve a source copy
Keep the original export unchanged and document its encoding, delimiter, quotation rules and decimal convention. Work on a controlled copy with a parser that supports the agreed dialect. Opening and saving a file through a spreadsheet may change types or delimiters before the problem has been diagnosed.
Write down the intended column names, measurement units and treatment of missing values. Separately identify text columns such as asset descriptions. A comma in an equipment location is not a decimal separator and should not be globally replaced.
3. Compare two hypothetical rows
Consider a two-column export with headers asset and temperature. The row A1,"12,5" has two fields when quotation is recognised; the second field can then be interpreted as 12.5 under an explicitly agreed decimal-comma rule.
The unquoted row A1,12,5 has three fields under a comma delimiter. Guessing that the last two fields should be joined is unsafe: a different source might genuinely contain three columns. Reject or quarantine the structural mismatch and obtain the correct export contract.

Original explanatory infographic. Values and test cases are hypothetical; equipment selection and implementation require project-specific verification.
Diagnostic comparison
Observation | Check next |
A1,"12,5" | Two parsed fields; numeric conversion needs declared locale. |
A1,12,5 | Three fields under comma delimiter; check export contract. |
1,234 in a measurement field | Resolve decimal versus grouping convention. |
4. Convert only the intended values
After parsing, validate measurement columns with the agreed numeric syntax and units. Keep identifiers as text. A source value such as 1,234 is ambiguous without its regional convention: it may be a decimal value or a thousands-formatted integer.
Create a small acceptance file with a decimal value, negative value, zero, missing measurement and a text field containing a comma. Compare the parsed field count and resulting typed values. A successful file open is not sufficient evidence that numeric magnitudes survived.
Keep the original export unchanged.
Parse quotation and delimiters before numbers.
Apply numeric rules to named measurement columns.
Quarantine field-count or format mismatches.
Reconcile typed values with the source.
5. Retain traceable exceptions
Return a rejected row number and a useful reason without silently changing the original. Reconcile source rows against accepted and rejected rows. If a supplier changes the export dialect, treat that as an interface change and repeat the boundary tests.
For ProSight Custom discussions, provide the file contract and required validation behaviour. The implementation may require an engineered preparation step; do not assume a documented standard or a conceptual diagram is an available product feature. Confirm the exact scope, ownership and acceptance evidence.
Recommended equipment / related solutions
Start with the ProSight Software platform overview to discuss the supported software scope and the reporting evidence your team needs.
Where the requirement needs engineered integration or a tailored reporting workflow, review ProSight Custom project scope. Confirm deliverables and the exact supported deployment before selecting an implementation.
Related practical guide: Industrial CSV Exports: Keep Text Fields from Becoming Spreadsheet Formulas
Frequently asked question
Can I replace every comma with a decimal point?
No. That can destroy column boundaries and alter text. Parse the agreed file structure first and convert only validated measurement fields under the declared numeric convention.
Technical references
Need help with your application?
Send the equipment models, current documentation and a sanitised test example. Discuss this integration and equipment requirement with ProSense; confirm the actual functions, interfaces and acceptance scope before purchase or deployment.

.png)
Comments