Skip to main content

Using Snapshots and Annual Plans in your report components

How to pin a KPI, chart, report or table to a saved snapshot or Annual Plan, and what changes when you do.

Written by Dharm Patel

Most components in Reporting Studio show live dat they follow your Global Date Selector and update as the farm's numbers change. Sometimes you want the opposite: a number frozen at a point in time, so the report says the same thing next month as it does today.

That's what Showing is for. It controls where a component's numbers come from, including pinning it to a saved Snapshot or an Annual Plan so it reports against a frozen position instead of live data.

Where to find it

Open a component's settings or, on a Financial Report, Gross Margin or Custom Table, open an individual column.

⚠️ Showing only appears once the Period is set to a specific year or period. While Period is left on Global Date, there's no Showing dropdown — the component just follows your Global Date Selector. Change Period to a Year, Year to Date, Month or Quarter and the Showing dropdown appears underneath it.

Showing gives you four choices:

  • Actuals — actual figures only

  • Actuals + Forecast — actuals to date, forecast for the rest of the period

  • Annual Plan — pick a year, and the component reports against that year's Annual Plan

  • Snapshots from — pick a year, then a specific snapshot saved on the farm

Annual Plan and Snapshots from both open a further list, so you choose the year first and then the plan or snapshot within it.

What changes when you pin to a Snapshot or Annual Plan

A snapshot is a frozen record, so a few things stop being yours to set and are taken from the snapshot instead:

  • The Actuals / Actuals + Forecast choice no longer applies. A snapshot already captures both, so picking a snapshot replaces that choice rather than sitting alongside it.

  • The component stops following the Global Date Selector. That's the whole point — changing the global date won't move a pinned component.

  • The horizon comes from the snapshot, not from a horizon you'd set manually. The snapshot's own actuals-to date is the source of truth.

Once a component is pinned, its header shows the year and the snapshot name so anyone reading the report can see the numbers aren't live.

Which components support it

  • KPI — the main value and the comparison value can each be pinned to a different snapshot, so you can compare a saved plan against where things actually landed.

  • Charts — all chart types.

  • Financial Report, Gross Margin and Custom Table set per column, so one column can be live and the next pinned to a snapshot. That's the usual way to build a plan-vs-actual view.

Using Annual Plans in org templates

Annual Plans are picked by year rather than by a specific snapshot, which is what makes them work in an organisation template "Annual Plan 2026" resolves to each farm's own 2026 Annual Plan when the template runs.

The catch is that a farm has to actually have one. If a template points at an Annual Plan year a farm doesn't have, the component shows a warning:

Fix it by creating the Annual Plan on that farm, or by pointing the component at a year the farm has.

If a snapshot goes missing

If a snapshot a component points at has been deleted, the component shows an error rather than silently falling back to live data. Re-point it at a snapshot that still exists.

Need a hand? Drop us a message through the green chat bubble in Figured.

Did this answer your question?