Monthly reconciliation case
Maple Field's lead asks whether the monthly Ready output can be handed off despite duplicate rows and a missing archive.
Use /Input/current.json only. Inspect the available folder, convert the JSON rows, remove exact duplicates, publish Ready rows to Reconciled and choose a recommendation that preserves the missing-file exception.
Maple Field's operations lead received duplicate records in the current monthly file. The archive file mentioned in an email is absent from the supplied folder. You need a publishable Ready table and a recommendation supported by the files that are present.
Inspect the folder, read the current file and convert its JSON text, then remove only exact duplicates. Keep Held work out of the published table without pretending it vanished from the source. The hidden fixture has a different ID and zero Units, so do not use a fixed list of rows. The final question checks the operational recommendation after the transformation: publish the supported Ready output, retain an exception record for the missing archive and investigate it separately. A missing file cannot be treated as an empty month without evidence that the two states mean the same thing.
Desktop flow: Monthly reconciliation case
Trigger: Desktop flow
Get files in folder [files]
Folder: /Input
Produced variable: Files
Display message [count]
Message: %Files.Count%
Only current.json exists. The absent archive is not a zero-row file.