← 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 audit Power BI semantic models, dimensional grain, relationships and reusable measures.",
  "included_files": [],
  "name": "semantic-model",
  "skill_md_contents": "---\nname: semantic-model\ndescription: Design and audit Power BI semantic models, dimensional grain, relationships and reusable measures.\n---\n\n# Semantic model architecture\nInventory fact/dimension grain, primary keys, relationship cardinalities and direction, active/inactive relationships, date role, null/unknown member behavior, security and measure definitions. Read `../../references/semantic-grain-star-schema.md`.\nPrefer clear star schema where it fits the business process; don't use many-to-many or bidirectional filters as generic fixes. Keep business definitions separate from display formatting. Make a model diagram or a table contract with one row per table and its join keys.\nFor unexpected report totals check model relationships and filter flow before rewriting DAX. Return proposed model, justification, assumptions, DAX impacts, migration plan and evidence needed to validate.\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: b5c5dabe2e91ed5936e454504e90d382c6931d61d52be2d1e238110644fda24c