← 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": "Reconcile report data and measure totals to an authoritative source before publication.",
"included_files": [],
"name": "reconciliation-testing",
"skill_md_contents": "---\nname: reconciliation-testing\ndescription: Reconcile report data and measure totals to an authoritative source before publication.\n---\n\n# Data, model and report reconciliation\nDefine source-of-truth grain, expected totals and scope for each metric. Validate count, distinct keys, missing values, fanout, aggregation and important boundary cases across source → model → report → export. Read `../../references/testing-reconciliation.md`.\nUse labeled fixture rows to test duplicates, totals, time boundaries and parameter combinations; distinguish source errors from renderer-only defects. For regulatory reporting capture signed-off source report and tolerance policy.\nOutput a reconciliation table with expected, actual (only if measured), difference, evidence and owner. Do not invent values or pass validation based on empty checks.\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: bd8fe5a9f3963c57ffbd86a2621f6c650cd446edc56df6cde8e3f9f148386b3a