Practice DAX by helping someone.
Browse open debug issues posted by the community. Fork into your sandbox, fix the measure, propose your fix back. The OP gets notified. Real data never in the room.
Pick an issue that catches your eye.
Every open issue has structured context: failing measure, expected vs actual, the synthetic data model, optional screenshots. Filter by concept — userelationship, time intelligence, filter context — or by what looks most interesting to solve.
- Concept-tagged for fast discovery
- Sort by oldest unanswered or most recent
- Free-text search across title, symptom, measure
Your own sandbox in one click.
Forking clones the synthetic model + the failing measure into your account. You can rewrite, run, test, and iterate in your own workspace without touching the OP’s session.
- Fork without leaving the issue page
- Full access to inspector + side-by-side compare
- Daxie’s diagnose-first mode active by default
-- Active path was wrong
CALCULATE(
[Total Sales],
USERELATIONSHIP('Sales'[ShipDate],
'Date'[Date])
)
The OP gets notified. The loop closes.
Once you’ve got a fix working, click “Propose as fix”. Your fork becomes publicly viewable and appears on the original issue’s page as a proposed solution. The OP gets a notification in their DAX Solver inbox — no Reddit-monitoring required.
- OP sees diagnosis + fixed measure side-by-side
- OP clicks “Accept” to merge the fix into their workspace
- Your fix lives as a permanent reference on the issue page
Common questions.
Do I need an account just to look?
Is helping just charity, or do I get something?
What if the OP’s measure references real data I shouldn’t see?
.pbit templates, which carry schema only. The synthetic data you query against is generated by us; it respects the OP’s relationships but contains none of their real numbers.Can I report an issue that looks off?
Open the feed. Pick a problem.
The fastest way to get better at DAX is to debug someone else’s code.