Measure Model

This FAQ addresses common questions and clarifications that arise while working on Measure Model and Scenarios. It covers formula and native measure mechanics, building the P&L hierarchy in the Measure Model canvas, the Measures in Rows and Tree layouts, and simulating a best-case scenario using Create Scenarios.

What is the difference between a native/DAX measure and a formula measure?

Native/DAX measures come directly from the semantic model — such as Sales Volume or Raw Material Cost. A formula measure is calculated by combining other measures using an expression in the planning sheet — such as Gross Revenue being calculated as Sales Volume multiplied by Avg Selling Price. Formula measures can reference other formula measures too, which is how Net Profit ultimately rolls all the way down to native measures like Discounts and Returns.

Why are all the Fact Transactions measures assigned to Values before the Measure Model is configured?

Every native/DAX measure used in the Measure Model must already be placed in the Values field on the planning sheet. The Measure Model canvas only lists native/DAX measures that are already in the Values field — so assigning them upfront is a required prerequisite before any hierarchy can be built.[

What is the main purpose of the Measure Model?

When semantic model measures are the foundation of a planning model, Measure Model provides a way to organize them into a meaningful hierarchy — such as a P&L structure — so teams can plan, simulate, and analyze the cascade of impacts across the full model in a single structured view.

Does the order in which measures are dragged onto the canvas affect whether the calculations come out correctly?

Canvas placement doesn't affect calculation correctness, since the formulas themselves are independent of hierarchy positioning. What matters is the formula dependency order — COGS's formula must exist in the planning sheet before Gross Profit's formula can reference it, regardless of when either is dragged into the tree visually.

If a measure gets nested under the wrong parent by mistake, does that break its formula?

No — nesting only controls where a measure displays in the hierarchy, not what it calculates. If Labor Cost were accidentally nested under Operating Expenses instead of COGS, its own value would stay correct, but COGS's total would be wrong since it would no longer include Labor Cost in its formula.

If a measure gets placed under the wrong parent by mistake, how can it be corrected?

It can be unstaged and repositioned rather than deleted and rebuilt. In the Hierarchy Builder canvas, each measure has a small cross/remove icon available directly next to it — clicking it unstages that measure from its current parent without deleting it. Once unstaged, it can be dragged again into the correct position under the intended parent.

What is the difference between nesting a measure under a parent in the canvas and adding a measure to the Values field on the planning sheet?

Nesting in the canvas defines the hierarchy structure — how measures roll up under Net Profit for display in Measures in Rows or Tree layout. Adding a measure to Values on the planning sheet is what makes it appear as an editable or viewable column on that sheet. A measure can exist in Values without being part of the hierarchy.

Does every measure need to be dragged into the canvas individually?

Both approaches are used across the exercise — Gross Revenue and Net Revenue are dragged individually, while COGS's three children and Operating Expenses’ four children are added using Select All plus Insert Measure. Which method is used depends on how many measures are being nested under the same parent at once.

Does switching to Measures in Rows change anything functionally, or is it purely visual?

It is a display change only. The same underlying measures, formulas, and data are shown, arranged so that each measure appears as a row rather than a column. It does not alter the Measure Model structure or its values — it simply makes the P&L hierarchy easier to read.

Is the Measure Model tied to the Simple P&L Model sheet specifically, or can the same structure be reused on other planning sheets?

The Measure Model is built and applied on the specific planning sheet on which it was configured. Reusing the same P&L logic on another sheet would require building or referencing the structure on that sheet separately.

Does switching to Tree layout change anything functionally?

It is a display change only — the same underlying nodes, formulas, and data are shown, rendered as connected branches instead of a flat hierarchy. It does not alter the Measure Model structure or its values.