All work
Alteryx · Python
Alteryx Workflow Automation
Two production Alteryx workflows behind recurring forecast and backlog reporting. Data is pulled from database and spreadsheet sources, cleansed and matched, reconciled against actuals, and written back out — replacing a manual monthly assembly process.
- Multi-source inputs
- Data cleansing
- Process automation
What it demonstrates
- Multi-source consolidation
- Database tables, spreadsheet inputs, and mapping reference files enter one pipeline and are conformed before anything downstream joins them.
- Part number matching and cleansing
- A dedicated branch standardizes part numbers first, so the joins that depend on them are not absorbing dirty keys.
- Actuals reconciled against backlog
- Actualized milestones are matched back to open backlog lines and removed from them, which is the step that keeps the two reports agreeing.
- Numbered, containerized steps
- Each stage sits in its own labelled container, so the workflow can be read, handed over, and re-run a stage at a time rather than end to end.
- Python inside the workflow
- A Python step handles the file retrieval the native tools do not cover, kept inline instead of as a separate manual pre-step.
The build
The workflows
100%
Loading
Backlog orders and recognized revenue are pulled, cleansed, and matched on part number, then consolidated into a single data source that aligns forecasted revenue with actuals.