Build a Regional Revenue Flow
Use the canvas to prepare one row per region with revenue for January and February in each of two years. Start with the table from Load the sample table. You need Data Flows enabled and a connection that can read the table.
Create the current and prior branches
- Open Data Flows and choose New flow. Name it
Regional service revenueand select the connection for the sample table. - Add a Source table step and choose the catalog, schema, and
studio_orderstable. Name the stepCurrent orders. Choose Preview step and check that the source has 12 records. - Add Filter rows to that branch. Keep records where
report_yearequals the number2026. The preview should have six rows. - Add Group and measure after the filter. Under Group by, select
region. Change the default measure to aggregationsum, fieldrevenue, and namecurrent_revenue. The preview should have three rows. - Start a second Source table branch that reads the same table. Name it
Prior orders. Add Filter rows for the number2025, then Group and measure byregionwith a sum ofrevenue. Name this measurerevenue.
Join the branch results
Add Join inputs after the current branch's grouped step. Select the prior branch's grouped step as Right input and configure the join:
| Control | Value |
|---|---|
| Join type | Keep all left rows |
| Required key relationship | Both keys are unique |
| Left and right keys | region on each side |
| Right field prefix | prior_ |
| Left output fields | region and current_revenue |
| Right output fields | revenue |
Use Compare row counts to check that each side and the join output have three rows. For a real dataset, a region missing from the prior period can produce a missing prior_revenue value. Check Inspect exceptions to distinguish a missing key from a duplicate key.
Add Check rows after the join and add a Unique key rule on region. Choose Use as output on this last step if needed, then Validate output. Preview the output and compare it with the expected rows:
| Region | Current revenue | Prior revenue |
|---|---|---|
| Central | $2,300 | $1,700 |
| East | $3,000 | $2,200 |
| West | $1,700 | $1,350 |
If the join shows more than three rows, check that each branch aggregates by region before the join. If a sum is unavailable, check the load types and confirm the measure uses the revenue field.
Make the result available to a dashboard
Choose Publish version and record the version shown in Published output. Select Add to live dataset library for that version. It will run on demand using the viewer's source access when attached to a dashboard. This tutorial uses the live output.
Next, build and publish a revenue dashboard with this dataset. See Publish, Share, and Use Flow Outputs for destination mappings and stored refreshes.