Establish what is happening
Compare the original identifier text
Choose a controlled identifier with leading zeros and one with enough digits to reveal rounding. Inspect the original export as text and compare it with the preview. A spreadsheet display can hide the stored representation, so preserve the file rather than trusting its formatted cell view.
Follow type choices to storage
Record the detected field type, explicit mapping type, validation output, and saved value. Check whether the importer converts to a number before a later text conversion. Turning a rounded number back into a string cannot recover digits that were already lost during that earlier step.
Check one affected lookup
Use a known source-to-destination relationship to see whether the changed value breaks a lookup or creates an unmatched record. Keep the scope limited to that example. A matching failure supports impact, but it does not establish whether export formatting, parsing, or storage caused the alteration.
What to carry forward
Finish with the exact original and observed strings, first changed stage, and one demonstrated downstream consequence. State whether the source export is already damaged. The next investigation should target the type conversion boundary rather than guessing the missing digits or broadening a matching rule.
Technical background: PostgreSQL documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow