← Power BI Report CopilotCONTENT HISTORY

Update to Power BI Report Copilot

Snapshot Nov 4, 2026 · 00:11 UTC · version 0.2.0

Collection source: downloaded plugin package.

WHAT CHANGED

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 JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Find Power BI/Fabric report, semantic-model, source, query and renderer bottlenecks using evidence.",
  "included_files": [],
  "name": "performance-diagnostics",
  "skill_md_contents": "---\nname: performance-diagnostics\ndescription: Find Power BI/Fabric report, semantic-model, source, query and renderer bottlenecks using evidence.\n---\n\n# End-to-end performance triage\nFirst reproduce the slow operation and check correctness. Measure time in source query, Power Query folding, model storage, DAX/visual query, paginated processing, export and service/capacity. Read `../../references/performance-evidence.md`.\nAsk for Performance Analyzer traces, DAX Studio/VertiPaq summaries, Power Query diagnostics, source plans, service refresh history and capacity metrics as appropriate. Do not request all tools for every issue.\nPrioritize fixes by demonstrated bottleneck and regression risk. Distinguish speculation, documented platform behavior, observed evidence and measured improvements. Output baseline, suspect, experiment, safe change, after metric and rollback.\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: 7fc21b3cf308ffaf8d5ae166731e5147cb847139964543b50f9c32e94324c36c