Limited Availability
← Gnok home

From a notebook to a regional report

Finance wants to know which regions drove revenue growth. An analyst can explore the orders in a notebook, publish the comparison as a data flow, and give managers a dashboard they can filter themselves.

Revenue increased in all three regions. East rose from $2,200 to $3,000, Central from $1,700 to $2,300, and West from $1,350 to $1,700.
January and February in the sample orders. East contributed $800 of the $1,750 increase.

Explore the orders in a notebook

Load 12 sample orders and sum revenue by year in a SQL cell. The next Python cell receives that result as a data frame. It calculates a 33.3% increase, from $5,250 to $7,000, for the two-month period.

Save the notebook and run all its cells from a fresh kernel to reproduce the analysis. A parameter cell can hold a reporting period or region for a later run. Recreate the notebook

Publish the regional comparison

Branch the orders by year, sum revenue for each region, then join the two branches on region. Check for duplicate keys before you publish. The resulting dataset has one row per region and a measure for each year.

Two fiscal-year branches on the flow canvas each group by region and feed a join called Match fiscal years by region.
A separate fiscal-close example shows the same pattern on the flow canvas. Each branch aggregates one year before the join.

Build the regional data flow

Let a reader explore the result

Attach a published flow version to a dashboard and bind its fields to a chart. In the tutorial, selecting East changes the revenue metric from $7,000 across all regions to $3,000 for East.

A region selector changes the question a reader is asking. Their data permissions determine which rows the query can return. When the business rule changes, attach the new flow version and republish the dashboard. Publish the revenue dashboard