Workforce export merge
Owner: Marrowfield Logistics operations manager.
Why: Compare active planned hours with paid hours without multiplying duplicate HR rows.
Data: Fictional HR roster and payroll period export.
Done: Worker, Team, Hours, Paid and signed Variance for matched active workers.
Marrowfield Logistics uses one HR export for planned hours and a second export for paid hours. The operations manager needs a comparison for active workers who appear in both files. The source files contain padded worker identifiers, a repeated HR row and records that occur on only one side. Those details decide whether the totals can be trusted.
Build the comparison in six steps. Each step starts from your own previous workflow, so keep the earlier preparation when you add the next tool. A positive Variance means planned hours exceed paid hours. Leave that sign visible in the handoff. Join's unmatched outputs remain available for a separate audit, but the requested deliverable here is the matched worker table with an explicit output schema.
input: {"source":"main"}
formula: {"field":"Worker","expression":"Trim([Worker])","type":"V_WString"}
Worked example: Whitespace is part of a join key until you remove it. Keep the complete worker identifier.