Establish what is happening
Choose contrasting source tokens
Use controlled true and false tokens, a numeric-looking form if supported, an empty field, and an invalid word. Record expected handling from the import contract. Compare the exact source strings with preview and saved state, including case and surrounding whitespace where the product documents normalization.
Trace the first boolean conversion
Follow parsing, normalization, field mapping, default selection, and assignment for each token. Record where text becomes a boolean and which rule is applied. A correctly displayed source string in preview does not establish that execution avoids generic string truthiness or a later fallback that changes an invalid value.
Inspect the affected behavior
Check one controlled workflow that uses the saved boolean, such as a filter or visible state. Keep the scope tied to that fixture and avoid changing unrelated records. If storage is correct but the interface labels it incorrectly, separate that display issue from a source-token conversion defect.
What to carry forward
End with the accepted-token contract, before-and-after values, first conversion boundary, and one demonstrated consequence. State any undocumented token behavior. The next investigation should distinguish explicit parsing, normalization, defaulting, and display rather than assuming every nonempty source cell represents a true value.
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