← 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": "Design and troubleshoot Power Query M transformations and query-folding correctness.",
  "included_files": [],
  "name": "power-query",
  "skill_md_contents": "---\nname: power-query\ndescription: Design and troubleshoot Power Query M transformations and query-folding correctness.\n---\n\n# Power Query and data preparation\nAssess source connector, types, locale, joins, transformations, privacy levels, row volume and folding. Read `../../references/power-query-folding.md`.\nRecommend folding-friendly transformations where supported but do not claim folding for an untested step. Preserve IDs as text, control timezone conversion and distinguish null, empty string and missing columns. Identify which shaping belongs in source, Power Query, or model with tradeoffs.\nReturn exact M transformations when requested, annotated folding boundaries/risks, refresh implications and validation samples. If provided M is broken, reproduce the type or expression error conceptually; execute only when a real M engine is available.\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: 841bfcce445a4ef6e49830c8c06e653493cbdbf02e23565693dded3ff7b9e889