← 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": "Validate Power BI report/model changes and exports before release or sharing.",
"included_files": [],
"name": "release-validation",
"skill_md_contents": "---\nname: release-validation\ndescription: Validate Power BI report/model changes and exports before release or sharing.\n---\n\n# Reporting release gate\nList exact artifacts (`.rdl`, `.pbix`, model definitions, M/DAX scripts), deployment target, owner, required parameter variants, renderer targets, security recipients, performance baseline and rollback path. Read `../../references/testing-reconciliation.md` and `../../references/security-governance.md`.\nUse `templates/release-evidence.md`. Mark each gate PASS only with observed evidence; use FAIL or NOT RUN otherwise. An unexecuted test is not a pass. Production publication, subscription edits, permission changes and regulated-data exports require explicit approval and supported tool actions.\nThe offline XML checker can identify obvious RDL layout risks but cannot certify a Power BI or Fabric deployment. Report the next real validation actions and outstanding blockers.\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: ee9c4331095d88bc6bc9e54917c36fa56b98701ff94bc8d07aa3ec9250d96376