PBIT
Schema and relationships with DAX Solver-generated synthetic rows. Useful for safe practice, not proof against your production values.
Verify
A number that appears is not yet a number you can defend.
DAX Solver records what ran, where it ran, and what the engine returned. Add your own expected outcomes to prove the business behavior that matters.
Two different proofs
First prove execution. Then prove intent.
An execution check answers whether the query ran in a specific model and filter context. An acceptance test answers whether its scalar or table result matches a rule you defined. DAX Solver never calls execution alone “business-correct.”
- Source type and model context recorded
- Bounded result evidence, with limitations shown
- User-defined expected values and comparison operators
- Saved run history for eligible paid plans
VERIFICATION RECEIPT · SAFE FIXTURE
Average order value
- Source
- Hosted practice model
- Execution
- Passed
- Expected
- $247.60
- Observed
- $247.60
- Acceptance
- 1 / 1 passed
- Meaning
- Passed the rules supplied for this run
Source truth
Know what kind of evidence you are looking at.
PBIX
A hosted execution target that can include the file’s real imported data. Upload only models you are authorized to use.
Power BI
A read-only connection to an existing dataset. DAX Solver executes queries but does not publish model changes.
Continue the loop
Need to understand or repair the measure?
Use Explain to inspect supported DAX behavior, or Debug to diagnose a failing result with targeted probes. Availability follows the launch state shown in the app.