Build a useful investigation brief
Construct a numeric format matrix
Represent the same known magnitude with the supported decimal and grouping conventions. Include negative values, fractional values, and an ambiguous short string. Keep units and expected numbers explicit. Separate quoted CSV fields from unquoted delimiter collisions so the matrix does not mix two different parsing failures.
Trace normalization and conversion
Inspect the complete field string, any punctuation removal, selected numeric convention, parsed number, and destination type. Record the first changed magnitude. Compare automatic handling with an explicit supported format choice; an unconditional separator replacement may happen before the selected convention has a chance to apply.
Check ambiguity and neighboring values
Test the implicated change against ordinary integers and values that legitimately use grouping. Define whether ambiguous inputs require a choice or follow a documented rule. Avoid repairing one decimal style by silently changing the meaning of another supported style that shares the same punctuation characters.
What to carry forward
Deliver the format matrix, selected rule, first lossy transformation, and results of the bounded comparison. State which ambiguous inputs remain undecidable without source context. A supported fix preserves intended magnitude and makes uncertainty visible rather than simply removing punctuation until every cell becomes parseable.
Technical background: Google Cloud 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