Protocol

Import identifiers as text before a spreadsheet can reinterpret them

A customer code is a name wearing digits, not necessarily a number.

When it fits

  • Identifiers contain leading zeros, long digit strings or number-like codes.

When to avoid it

  • Formatting a damaged value as text is too late. Reimport from an intact source rather than guessing lost digits or zeros.

Why it matters

Set the import column to text before values enter a numeric representation. Excel can remove leading zeros or lose precision in long numeric strings. Changing the display afterward does not recover information that has already been discarded.

Steps

  1. Use a controlled import route and declare identifier columns as text.
  2. Include test values with leading zeros and more than 15 digits.
  3. Compare the imported and exported strings with the untouched source.

An example

The code 000742 must remain six characters when exported for a matching job; displaying 742 with padding is not automatically the same preservation route.

Check your result

A round trip preserves the exact identifier strings, including length and final digits.

Keep this limit in mind

  • Formatting a damaged value as text is too late. Reimport from an intact source rather than guessing lost digits or zeros.

Connected ideas

Useful with
Match the identifier together with its issuing namespace

Evidence and sources

Supports

Excel can remove leading zeros and lose precision beyond 15 significant numeric digits; formatting afterward does not restore already lost information.

Preventing conversion must happen before the affected values enter a numeric representation.

Keeping leading zeros and large numbers · Import as text; long numbers and custom formatting

All sources (1)