{"id":79594,"plugin_id":"plugins_6ab409346c7c8191bacd83080aee170d","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-04T00:11:27.219Z","digest":"8acc6378e25f4112e1385ffff25ac7d73085d74ae4ea7815c56a9bc607cbb29d","against":null,"payload":{"description":"Design or implement a Power BI Report Builder RDL report with correct datasets, layout and export behavior.","included_files":[],"name":"build-paginated-report","skill_md_contents":"---\nname: build-paginated-report\ndescription: Design or implement a Power BI Report Builder RDL report with correct datasets, layout and export behavior.\n---\n\n# Build a paginated report\nDefine audience, data sources, expected grain, parameter UX, row volume, export format, page size and access boundary. Define a sample report contract before building: measures, row groups, sorting, subtotals, page name and expected numbers.\nPrefer a narrow dataset with typed fields and deterministic ORDER BY when output order matters. Identify source/provider and whether queries are SQL, DAX or other before authoring parameter syntax. Create report parameters, dataset mappings, tablix hierarchy, header/footer, page settings and export-specific layouts; consult `../../references/paginated-architecture.md` and `../../references/renderer-matrix.md`.\nUse a representative fixture for empty/all/filtered results and for page overflow. No claims of actual PDF rendering or `.rdl` generation without matching tools. Deliver RDL or exact creation steps, dataset query, parameter map, page-layout settings and acceptance cases.\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"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}