Failed refresh case
Owner: Fernwick Services report owner.
Question: Which current invoices have positive net amounts after the export schema changed?
Data: Fictional sales exports with Invoice, AmountText, Region and an extra ExportBatch field.
Done: Restore the named schema, type the amount, deduplicate Invoice and rank positive invoices by net amount.
Fernwick Services changes a monthly invoice export by renaming the text amount field. A saved report still expects the old field and fails. The reporting owner needs a repaired workflow and evidence of the invoices whose cleaned amount is positive. Guessing a replacement from column position would risk using the wrong measure when the export changes again.
Read the current input metadata, select the new field by name and rename it to the report contract. Then parse the numeric text and continue the intended business logic. The project preserves credits and zero amounts until the requested positive-only filter. A run that completes on the visible file is only part of the evidence; the hidden file changes the row count, identifiers and amounts. Finish with a ranked table that the owner can inspect.
input: {"source":"main"}
select: {"fields":[{"name":"Invoice"},{"name":"AmountText","rename":"NetText"},{"name":"Region"}]}
Worked example: Resolve the named schema change explicitly. A positional guess could select an unrelated new field.