KB article

Measure Branching Done Right: Reuse Without Confusion

Branching keeps complex measures readable and consistent when done carefully.

arf-kbsemantic-integritymeasure-branchingcanonical-metriclineage

TL;DR

  • Base measures first, then layered variants.
  • Branching improves maintainability and clarity.

The problem

  • Complex measures become unmanageable and inconsistent.
  • AI struggles to interpret embedded logic.

Why it matters

  • Reusable base measures reduce errors and drift.
  • AI explanations are easier when logic is modular.

Symptoms

  • Measures with hundreds of lines of DAX.
  • Same logic repeated in multiple measures.

Root causes

  • No base measure patterns.
  • Local fixes copied across reports.

What good looks like

  • Measures built from a small set of base metrics.
  • Clear naming of base vs derived measures.

How to fix

  • Identify common logic and extract base measures.
  • Replace repeated logic with base measures.
  • Document the branching tree.

Pitfalls

  • Branching without documenting assumptions.
  • Excessive layers that hide intent.

Checklist

  • Base measures defined for key KPIs.
  • Derived measures reference base measures.
  • Branching documented and reviewed.

Framework placement

Primary ARF layer: Semantic Integrity. Diagnostic bridge: semantic-reliability, change-reliability.