powerbi-dashboard-build

Power BI dashboard build

Build an executive-grade report page as PBIR files and deploy it through the powerbi-agent MCP server. Nothing is "done" until every page has been captured as a screenshot and read against a written Done-criteria table — the see-it doctrine, docs/reference/PLAYBOOK.md 1.3.

Procedure

1. Call guardrails() (or read the guardrails://rules resource) and hold to it all session: never touch an item you did not create, never trigger a refresh, the model is read-only, the theme is locked once approved, one render pass per deploy, one batched DAX query — not many.
2. Call connection_status(). Do not proceed on a failed or ambiguous connection; report it back instead of guessing which tenant you are on.
3. Fill docs/reference/SPEC_TEMPLATE.md before writing any JSON: audience, the one question the page must answer, a per-page visual list with positions, and Done criteria — the expected number for every tile, per page. An agent that cannot hit a Done-criteria number reports it; it does not improvise.
4. get_model_schema(workspace, model) to see every table, column, measure and calculation item, then one batched run_dax(query, ...) to build the tie-out table: latest traded day, week-to-date, last year same weekday, budget, per channel. One query, not fifteen — docs/reference/PLAYBOOK_PART3.md Step 2.
5. Start from report-template/ (copy to "ORG-<name>.Report") or call get_report_definition(report, out_dir, workspace) on an existing report into a clone folder. Never edit the original item — that is what the ORG- prefix and the "never touch an item you did not create" guardrail exist to stop.
6. Split by page: one builder per definition/pages/<page id>/ folder. The main thread alone owns report.json, pages.json, reportExtensions.json, the theme and the deploy — this is what stops two builders writing the same file.
7. Set date scope per visual with set_date_filters(visual_json, mode, weeks) — latest-day for latest-day visuals on model measures, window-weeks for trend charts, this-week for week-to-date matrices, none for cards already bound to self-pinning report measures. Never hand-write a date filter: a plain 'Date'[Date] window under a time-intelligence calculation group returns the whole last-year week instead of one day (see Part 4, trap T1/T3).
8. Report-only measures go in reportExtensions.json, prefixed RM , never in the model — the model is read-only. Follow docs/reference/measures/README.md: no RM measure references another; its dataType is "Text", never "String"; test each measure alone before shipping it.
9. Call validate_report(folder, baseline) after every batch. Do not continue past a nonzero error count — fix and re-validate. baseline is report-template (or the original's folder, when you cloned one); it also checks theme byte-identity, overlaps, canvas bounds, date pins present and banned filter kinds.
10. deploy_report(folder, bind=True) the first time (writes the model binding from config); plain deploy_report(folder) after that. It refuses names without the ORG- prefix and models not in the allowed list — that refusal is correct; do not route around it.
11. capture_pages(target, out_dir, headless=True, settle_seconds=60), then LOOK at every PNG and read every .txt against the Done criteria — this is the hand-off to the powerbi-dashboard-verify skill. A clean validator run is not a finished page.
12. At most two fix rounds. After that, report which Done-criteria numbers are still not met and why, instead of a third silent attempt.