Decide where the work belongs
Identify the value at risk
Find which imported fields legitimately contain line breaks, such as notes or descriptions. Determine whether the failure truncates text, shifts later columns, or only rejects the record. Do not assume every newline is optional formatting that can safely be removed.
Measure producer and field exposure
Group examples by exporting tool and affected field. Compare attempts containing multiline values with successful single-line imports. Use available import outcomes to estimate scope and retain uncertainty when the system records only a generic validation error without the underlying structural classification.
Evaluate the cost of recovery
Try the documented correction flow with a sanitized file. Record whether users can identify the damaged record and preserve its content. A workaround that requires manually flattening every note may be expensive even when it avoids an immediate parser error or blocked import.
What to carry forward
Choose a priority based on content loss, mistaken row acceptance, affected workflows, and recovery effort. Name an owner and an escalation trigger, such as evidence of shifted identifiers. Keep unsupported quoting styles separate from valid multiline records the product intends to accept.
Technical background: DuckDB 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