Establish what is happening
Choose an unambiguous reference value
Find a controlled source value with a known magnitude and fractional part. Record the original string, expected number, grouping convention, and unit. Compare it with the preview and saved value, using a second example without grouping to distinguish a separator problem from a general field-mapping mistake.
Separate field splitting from number parsing
Check whether the CSV parser produces one complete field before numeric conversion begins. A comma may be a delimiter in one context and a decimal separator inside a quoted field. Record which stage first changes the value rather than adjusting both parsing and numeric settings together.
Compare stored value with display
Inspect whether the saved numeric value is incorrect or only rendered with an unexpected format. Compare a supported calculation or retrieval using the known example. A different display convention may preserve magnitude, while stripping punctuation during parsing can create a materially different number that still looks neatly formatted.
What to carry forward
End with the original string, intended magnitude, selected convention, and first changed stage. Keep ambiguous source examples explicit. The next investigation should target field splitting, numeric interpretation, or display separately instead of treating every comma-and-period difference as the same formatting defect.
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