← 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": "Debug or write DAX measures by investigating context and intended totals before editing formulas.",
"included_files": [],
"name": "dax-debugging",
"skill_md_contents": "---\nname: dax-debugging\ndescription: Debug or write DAX measures by investigating context and intended totals before editing formulas.\n---\n\n# DAX measure analysis\nDefine expected metric at row, group and grand-total level. Reconstruct filters from slicers, visual, report, relationships, CALCULATE, iterator and context transition. Read `../../references/dax-context.md`.\nStart with simple base measures (numerator, denominator, row count, distinct count); only propose SUMX or altered ALL/REMOVEFILTERS when the business definition requires it. Percentages and ratios may aggregate as ratios-of-sums rather than averages of displayed percentages. Make the desired total explicit.\nWhen given DAX, return minimally revised copy-ready code, explanation of filter-context change, and a small synthetic test table or DAX Studio query if possible. Never claim measures were executed or numbers observed unless genuine tools ran them.\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: 446c6cc6964652c261dfb6e186638d3e6181d73af9a8112533db94dcdcaea153