← 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": "Plan incremental refresh, partition boundaries, change detection and backfill safety.",
"included_files": [],
"name": "incremental-refresh",
"skill_md_contents": "---\nname: incremental-refresh\ndescription: Plan incremental refresh, partition boundaries, change detection and backfill safety.\n---\n\n# Incremental refresh & partition safety\nIdentify data source query, RangeStart and RangeEnd parameters, Date/Time types, inclusive/exclusive bounds, time zone, change detection, source immutability and retention requirements. Read `../../references/incremental-refresh.md`.\nCheck query folding where applicable, late-arriving corrections, reprocessing windows, partition overlap, deletes and reconciliation. Design a small controlled backfill with rollback and duplicate/omission tests before large changes.\nReturn partitioning approach, boundary examples, verification SQL/logic, data correction plan and restart/rollback path. Don't silently reset refresh policy, drop partitions or trigger long-running refresh without tools and approvals.\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: 7a8a49fea96e38a70c7e2e9159788d21cb616891e32377d067ed3a4ac7277370