One Expression Halves Your Data Ceiling — Paginated Reports

One Expression Halves Your Data Ceiling Episode 30 • 2026-07-24 Duration: 10:13 Paginated reports carry no data model, and that one design decision explains every limit teams hit in production. This episode traces the consequences from silent data drops to a tenant-wide security door that only opens one way, and lands on the question that makes the tool choice for you. What we discuss How it actually works underneath the abstraction The pattern we keep seeing in the field A real Reddit/Microsoft Q&A question unpacked Where the obvious answer breaks F-SKU realism — what this actually costs When the rejected approach is actually right Risks of the recommended path The architectural principle to take home Key takeaways And a Diagnostics button nobody's pressed is sitting there, ready to explain why. Somewhere right now, a Monday-morning subscription is carrying a Weekday expression nobody remembers, heading for a ceiling that used to be a slope and is now a cliff. Show me the query pattern. If the aggregation's in the right place, the report scales. If it isn't, no capacity tier saves you. That's the decision that actually matters. Resources What are paginated reports in Power BI? When to use paginated reports Paginated reports in the Power BI service Performance and scalability FAQ Paginated Report definition Access the paginated report editor SQL Server Reporting Services (Wikipedia) RDL Schema Specification Plan to migrate .rdl reports Supported data sources Connect via Power Query Create and use the paginated report visual Email subscriptions Export Power BI paginated reports About the show AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon. Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday. Submit your case Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing. This podcast was generated by AI. Brand design based on fabricperiodictable.com.