CSV Header Looks Correct but Will Not Map? Check the UTF-8 File Boundary
A monitoring CSV appears to contain the expected asset_id column, yet the import reports that the field is missing. Renaming the visible heading seems to fix one file but the problem returns with the next export. An invisible character introduced by decoding is one possible cause.

Original conceptual illustration; not a live software screen, specific product or customer installation.
Key takeaways
Visual header equality does not prove character equality.
Treat a permitted UTF-8 signature at the file boundary deliberately.
Preserve the original file and test encoding, parsing and mapping separately.
1. Preserve the file that failed
Keep an unchanged copy of the failed export before opening and saving it through another application. Record the exporter, receiving tool, file encoding, delimiter and import route. A spreadsheet save can change the evidence needed to explain the original failure.
Use the ProSight Software platform overview to scope the reporting and handover discussion. This guide concerns a file-interface acceptance check; it does not establish that a specific CSV importer or automatic encoding control exists in every ProSight Software deployment.
2. Inspect the beginning at the byte level
Unicode documents the UTF-8 byte-order-mark representation as EF BB BF. In UTF-8 it can act as an initial signature; it does not choose an alternative byte order. Some recipients do not expect that signature, so the receiving interface contract matters.
If a decoder passes the initial U+FEFF character through as content, the first parsed heading may include that character before asset_id. A visual display can conceal the difference. Inspect an escaped representation or code-point listing through approved tools rather than relying on how the heading looks.
Do not conclude that every missing first column is a BOM problem. Incorrect delimiters, quoting, whitespace, case rules and a genuinely different field name are separate causes. Verify the actual bytes and parsing outcome before changing a mapping.
3. Make the boundary policy explicit
Specify the permitted encoding and whether an initial signature is allowed. Configure a supported decoding path that follows that contract before the CSV parser and field mapper run. Reject unsupported encodings with a useful error rather than guessing and silently changing the record.
Do not delete the first three bytes unconditionally: a UTF-8 file without a signature begins with real content. Also avoid globally removing U+FEFF or other invisible characters throughout every field. Characters inside data need their own documented validation rules.
Encoding and CSV syntax are separate layers. Correctly decoding UTF-8 does not make a malformed quoted row valid. Likewise, successful CSV parsing does not establish that required field names or asset identifiers meet the receiving schema.

Original explanatory infographic. Values and test cases are hypothetical; equipment selection and implementation require project-specific verification.
Diagnostic comparison
Observation | Layer to inspect |
Only the first header fails | Initial bytes and decoded code points |
All columns merge into one | Delimiter and quoting configuration |
Characters become replacement symbols | Encoding mismatch or invalid byte sequence |
4. Build two faithful test files
Create a harmless synthetic CSV with the exact first header asset_id and one invented record. Make two byte-level versions: UTF-8 without a signature, and UTF-8 with the permitted initial EF BB BF signature. Keep all subsequent content identical.
Where the agreed interface accepts both forms, both imports should produce exactly the same first field name and record identity. Where only one form is accepted, the other should fail explicitly under the contract. Neither outcome should silently create a second unexpected column.
Include a non-ASCII description, an empty optional field and a quoted delimiter to check the surrounding workflow. Inspect parsed field names, row count and exact identifiers. These are synthetic acceptance cases, not evidence that an operational export has a defect.
Preserve the original bytes and record the interface contract.
Inspect any initial signature and decoded first heading.
Validate encoding before CSV syntax and field mapping.
Test permitted files with and without the signature.
5. Verify repeatable handover
Retest the original import route after correcting the supported decoder configuration. Preserve the original evidence and document any conversion applied to a working copy. Confirm that automated refreshes use the same settings as the successful manual test.
Avoid repairing each incoming file by hand without addressing the interface. Keep a small approved fixture for future exporter or import-tool changes. A useful error identifies the encoding or required-field problem without exposing sensitive file contents.
For ProSight Software assistance, provide a sanitised original file, an escaped first-header representation and the receiving application/version. Ask for a documented data-handover assessment with explicit supported formats. The practical goal is predictable field identity across the complete export, decode, parse and map path.
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
Should I strip invisible characters from every field?
No. Handle the permitted file signature at the boundary and validate data fields under their own rules. Broad character deletion can change identifiers and destroy evidence.
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