Asset ID 00123 Became 123? Preserve Identifier Types in CSV Handover
A maintenance team exports asset records, opens the file in a spreadsheet and later finds that asset 00123 no longer matches the monitoring record. The characters were treated as a number instead of an identifier. Define text fields before import and verify exact identity through the complete handover workflow.

Original conceptual illustration; not a specific product, live software screen or customer installation.
Keep identifier-preservation requirements in the data handover specification. Start with the ProSight Software platform overview. Confirm the exact equipment, interface and project scope before selection.
Key takeaways
Identifiers are labels even when every character is a digit.
Formatting a changed value cannot recover lost source characters.
Test imports, joins, saves and reopened files against the original dataset.
1. Decide what each column means
Separate identifiers from quantities in the data dictionary. An asset code, serial number or location key may look numeric but generally identifies one record. A flow quantity or temperature reading has different arithmetic and validation requirements.
Specify the exact identifier representation: allowed characters, case treatment, expected length and whether leading zeros are significant. Do not choose a fixed width simply because the first few examples happen to match. Variable-length codes can make automatic padding ambiguous.
This article concerns an integration handover process. It does not establish that any particular CSV export, spreadsheet connection or type-control feature is included in ProSight Software. Confirm the supported output and consuming applications for the actual deployment.
2. Control interpretation before conversion
Microsoft documents that Excel can remove leading zeros and convert long digit strings during automatic numeric interpretation. Its supported import methods allow a column to be assigned a text type. Availability of automatic-conversion controls depends on the Excel version.
Use the approved text-import workflow and explicitly set identifier columns to text before accepting the loaded data. Inspect automatically inserted type-conversion steps as well as the final visible cells. A conversion that already removed information cannot be repaired by changing only the display format.
CSV quotes delimit fields; do not rely on them alone as a declaration of column type. Keep the original exported file unchanged and test the actual receiving application. Other spreadsheet engines and import tools can have different inference rules.
3. A hypothetical join that changes the result
Create a synthetic reference dataset containing identifiers 00123 and 123 as two distinct assets. Give them different harmless descriptions. The expected handover preserves two distinct keys and matches each record to its own description.
If both values become numeric 123, a later join can merge, duplicate or misassign records depending on the receiving tool. That is a data-identity problem even if the displayed measurement values remain reasonable. Check exact key equality and match counts, not just whether the file opens.
Include a long synthetic digit-only identifier and a code containing the letter E. Test their exact characters after import, save and reopen. Do not use genuine customer identifiers for a commissioning fixture. This example is an invented test case, not a reported incident.

Original explanatory diagram. Examples are hypothetical; verify the actual equipment, interface contract and project requirements.
4. Repair from the source, not from appearance
If a working copy has lost zeros or precision, return to the unchanged original or another authoritative record. Do not reconstruct identifiers by adding a guessed number of zeros or copying a rounded display. Several original keys may map to the same converted number.
Keep numeric measurements numeric where the receiving contract requires arithmetic. Converting an entire dataset to text as a shortcut can break totals, sorting and validation. Apply types by column and verify the intended calculations separately.
Avoid formula-based tricks that change the identifier’s actual contents merely to influence a spreadsheet. If a presentation transformation is required, document it and preserve a faithful machine-readable source. Keep spreadsheet formula-safety review as a separate acceptance question.
Define identifier columns and their exact character rules.
Import those columns as text before automatic conversion.
Compare distinct keys, exact values and join results.
Save, reopen and retest the supported handover workflow.
5. Make identity preservation an acceptance check
Record the application version, locale, import route, delimiter, encoding and assigned column types. Compare row count, unique identifier count and exact representative values with the reference fixture. Include the supported refresh path so a later import does not reinstate automatic conversion.
Save to the agreed working format, close it and reopen it. Repeat the intended join or upload in a test environment. Investigate missing, extra and many-to-one matches before permitting operational updates based on the file.
For a ProSight Software reporting discussion, provide the supported export method, a sanitised example, the receiving application and expected identifier rules. Agree who owns the data dictionary and the import procedure. The practical goal is a traceable path in which the same identifier continues to refer to the same asset.
Related guide and project resources
Application selection and next steps
Recommended equipment / related solutions
For this project, review ProSight Software platform overview. Use the article’s checks as acceptance questions; the listing alone does not establish the behaviour of every connected device or integration.
For an alternative project scope, review ProSight Custom project scope. Ask ProSense to confirm the required inputs, data handling and deployment options. This is a selection starting point, not a compatibility guarantee.
Need help with your application?
Send the relevant equipment documentation, field definitions and a sanitised example of the behaviour you need to verify. Confirm the available functions and integration requirements for the exact equipment and deployment.

.png)
Comments