Skip to content
Relevance Docs

Scenario simulation

Scenario simulation loads baseline data scoped to your current Qlik selections into an editable version, lets you adjust it freely, and pushes the results into the rest of the app - charts, KPIs, everything downstream - without touching the real underlying data until you choose to. It builds on versioning and importing from a Qlik table.

Before you start

Section titled “Before you start”
  • At least one dimension must be marked Part of record key in the property panel - Scenario Simulation doesn’t appear at all until that’s true.
  • A Table Id must already be set.
  • Baseline Values Source is currently Qlik Sense Table only - an Excel-file baseline source is planned but not available yet.

Steps to set up

Section titled “Steps to set up”
  1. In the property panel, go to Data → Scribe Configuration → Scenario Simulation and turn on Enable Scenario Simulation.
  2. Under Select QS Table, choose the Qlik table object to pull baseline data from.
  3. Select Add Column from QS Table for each field you want as an editable custom column - this generates a matching custom column automatically instead of building it by hand.

Running a simulation

Section titled “Running a simulation”
  1. Make the Qlik selections that define what you want to simulate (a region, a product line, a time period - whatever your app’s dimensions allow).
  2. Select Initialize Scenario. RLV Scribe loads baseline data scoped to exactly that selection into an editable scenario.
  3. Adjust values freely - they behave like any other writeback edit.
  4. When you’re done, either:
    • Calculate - reloads the app so the rest of the sheet (charts, KPIs) reflects your simulated numbers.
    • Reset to Baseline - discards your changes and reloads the original figures.

Changing your Qlik selections after initializing prompts you to initialize again for the new scope - a simulation is always tied to the selection context it was started under.

Worked example

Section titled “Worked example”

A sales director wants to test a price increase for one region before proposing it company-wide. They select Region: North and Product: Widgets in the app, then select Initialize Scenario on the pricing sheet - it loads North/Widgets’ actual current prices as an editable scenario. They raise every price by 5% across the visible rows, then select Calculate; the app reloads and a revenue KPI elsewhere on the sheet immediately reflects the simulated 5% increase for that scope only - nothing outside North/Widgets changed. Concluding the increase would hurt volume more than it helps revenue, they select Reset to Baseline to discard the test before selecting Region: South to try the same idea there instead.

What can go wrong

Section titled “What can go wrong”