← 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": "Troubleshoot paginated tablix grouping, sorting, aggregates, VB expressions, visibility and repeated headers.",
  "included_files": [],
  "name": "tablix-expressions",
  "skill_md_contents": "---\nname: tablix-expressions\ndescription: Troubleshoot paginated tablix grouping, sorting, aggregates, VB expressions, visibility and repeated headers.\n---\n\n# Tablix, grouping and Visual Basic scope\nConfirm dataset grain and the actual row/column group hierarchy, Details group, filters, sort expressions, dynamic/static group members, aggregates, visibility toggles and page breaks in that order. Read `../../references/tablix-expression-scopes.md`.\nExpressions are Microsoft Visual Basic (VB), not DAX. Scope must be a known dataset or group, not a guessed object. For totals diagnose wrong group scope and row amplification before wrapping in First/Sum. For repeated headers inspect static member properties, not only textbox styles.\nGive concrete properties and paths where known, a before/after expression example if justified, and validation with representative data and target renderer. Do not silently use `Distinct` to conceal duplication or break subtotals.\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: d057983c004f09b8cbb00fc8046feaaa04bd12f6f78ba23306e95eebd6c95f5b