Create a disconnected scenario table in Power BI

A disconnected table can hold user-selectable assumptions without directly filtering the transaction model. A measure reads the chosen assumption and applies it to a defined calculation. This separates “which observed records are selected?” from “which hypothetical adjustment should be explored?”

The absence of a relationship is intentional. The scenario table does not need a matching transaction key because it describes an input to a model, not an attribute of an actual sale.

Create an explicit assumption table

In the retail teaching model, create a table named Scenario with a label and multiplier:

Scenario =
DATATABLE(
    "Label", STRING,
    "Multiplier", DOUBLE,
    {
        {"Lower value assumption", 0.9},
        {"Unchanged value assumption", 1.0},
        {"Higher value assumption", 1.1}
    }
)

Do not relate Scenario to FactSales. Add Scenario[Label] to a selector and configure a single-choice experience where appropriate. The values are arbitrary teaching assumptions, not forecast probabilities or recommended business targets.

Read one selected value

Selected Scenario Multiplier = SELECTEDVALUE(Scenario[Multiplier])

Scenario Paid Value Paise =
VAR Factor = [Selected Scenario Multiplier]
RETURN
    IF(ISBLANK(Factor), BLANK(), [Paid Net Paise] * Factor)

Create these as separate measures. With one selected factor, the scenario measure scales the observed Paid value. With zero or multiple distinct factors in context, it remains unavailable rather than silently choosing a default.

Microsoft documents SELECTEDVALUE's single-distinct-value requirement in its function reference. A selector that looks single-choice should still be tested for cleared or programmatically restored states.

Verify the hypothetical outputs

The observed Paid value is 69,500 paise. Factors 0.9, 1.0 and 1.1 produce 62,550, 69,500 and 76,450 respectively. The observed measure must remain 69,500 regardless of the scenario choice.

Under January, the observed 47,500 becomes 42,750, 47,500 or 52,250. This confirms that ordinary date context still affects the base measure while the disconnected selector changes only the assumption.

The arithmetic can be verified directly. DAX and selector interactions require Power BI application review; no scenario PBIX is supplied as already tested.

Explain what the multiplier actually assumes

Multiplying net value by 1.1 assumes a ten-percent increase in that aggregate value while leaving the rest of the model unspecified. It does not establish whether the increase comes from price, quantity, mix or reduced discounts.

If the business question concerns price changes, model quantities and demand response separately. If it concerns volume, consider capacity and variable costs. A simple value multiplier is useful for sensitivity exploration only when its limitations are visible.

Do not label the scenario output “predicted sales.” No predictive model or causal evidence supports that claim in this exercise.

Keep actual and scenario results distinguishable

Show the observed measure beside the scenario measure and display the selected assumption in text. Use consistent units and an explicit difference measure if helpful.

A bookmark or reset control should restore a documented scenario state. Test that switching report pages does not leave an invisible prior assumption affecting a card whose label appears to show actual results.

If several scenario inputs exist, state whether they can vary independently. A price increase and unchanged volume may be a deliberate sensitivity assumption, but it should not be treated as a likely joint outcome without evidence.

Test missing and multiple selections

Clear the selector and verify that the report asks for one assumption or uses a clearly documented default. Select several values where the interface permits it and confirm the measure does not produce an unexplained result.

Keep an assumption-status measure separate from the numeric output. This makes it easier to explain why a scenario is unavailable without mixing text into a measure used for further arithmetic.

Exercise: add a second disconnected cost assumption and calculate a simplified margin scenario. List which costs change with value and which remain fixed, then identify the business evidence needed before using that scenario for a real decision.

NeuraPath's Data Analytics with Generative AI course connects interactive modelling with explicit assumptions. A strong scenario report keeps observed facts separate from hypothetical inputs and their consequences.

Continue learning

This article is part of the DAX measures and analytical correctness sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in ALL versus ALLSELECTED in a share-of-total measure.
• Continue with DAX inactive relationships and order versus delivery dates.