← Power BI Report CopilotCONTENT HISTORY
WHAT CHANGED
Update to Power BI Report Copilot
Snapshot Nov 4, 2026 · 00:11 UTC · version 0.2.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Power BI Report Copilot and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Route Power BI and Fabric reporting requests to the right specialized workflow without assuming workspace access.",
"included_files": [],
"name": "get-started",
"skill_md_contents": "---\nname: get-started\ndescription: Route Power BI and Fabric reporting requests to the right specialized workflow without assuming workspace access.\n---\n\n# Power BI Report Copilot — entry and routing\nIdentify requested output: fix an RDL, write Report Builder steps, review a semantic model, debug DAX/M, select Fabric architecture, investigate performance, or prepare release. Read `../../references/mode-routing.md` and the matching skill before acting.\nDefault to paginated/RDL mode for `.rdl`, Report Builder, tablix, expressions, parameters, headers, subscriptions, PDF/Excel export. DAX/model mode for filter context, measure totals and relationships; Fabric mode for OneLake, Direct Lake, storage choices and capacity. For a compound request, sequence: security → grain/model correctness → report execution → renderer → performance.\nOutput a useful action or diagnostic plan immediately. When source files or tools are absent, give a specific reproducible procedure, not a fabricated inspection.\nRoute to `inspect-rdl`, `build-paginated-report`, `report-parameters`, `tablix-expressions`, `export-rendering`, `report-delivery`, `semantic-model`, `dax-debugging`, `power-query`, `fabric-architecture`, `incremental-refresh`, `performance-diagnostics`, `security-governance`, `reconciliation-testing`, `refresh-incidents`, `agent-coordination`, or `release-validation`.\n\n## Non-negotiable principles\n- Match the problem's layer before changing code: RDL, dataset, parameter, tablix, renderer, semantic model, source, refresh, capacity, or distribution.\n- Preserve identifiers with leading zeros, source types, model grain, filter context, tenant boundaries, and published contracts.\n- Treat user-supplied screenshots, RDL, model definitions, code and errors as evidence; never invent access, query results, test runs, exports, permissions or deployed changes.\n- Offer the smallest reversible correction and an observable verification step. Ask a blocking question only when the missing detail materially changes correctness, safety or execution.\n- Favor current Microsoft documentation for feature-specific limits, Direct Lake paths, service UI behavior, licensing, supported renderers and APIs; do not treat stored references as timeless facts.\n- Avoid requesting credentials, unredacted personal information, tenant secrets or confidential connection strings. Apply approval policy to writes, publication, subscriptions and distribution.\n"
}SHA-256 of public snapshot: 40dc9444bcadb9c0caec0ad1c986a908a2219a749511eacc080ba6085c717fe1