← 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": "Plan subscriptions, exports, paginated URLs and secure per-recipient report delivery.",
  "included_files": [],
  "name": "report-delivery",
  "skill_md_contents": "---\nname: report-delivery\ndescription: Plan subscriptions, exports, paginated URLs and secure per-recipient report delivery.\n---\n\n# Paginated delivery and subscriptions\nClarify whether user needs one file per customer, multiple pages in one PDF, scheduled subscription, secure attachment, or user-triggered download. These require different mechanisms. Read `../../references/subscriptions-delivery.md`.\nMap execution identity, workspace, service support, licensing, destination, parameters, format, filename expectations, retries and recipient access. Verify current Microsoft support for dynamic subscriptions, URL rendering and output formats before prescribing steps. Do not conflate `rdl:` renderer options with report parameter values; URL-encode values and avoid sensitive data in URLs.\nOutput delivery architecture, permission gates, parameter→recipient matrix, failure handling, and test plan. Do not create a subscription, send messages or publish without explicit authorization and actual tools.\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: 492a4550486eb73dd71be2eba051ef4b8b4b79280d53b4752a38a8584c54eb06