One of the most anticipated Power BI features is finally there! No, it’s not new fancy Small multiples improvements, or another fresh AI thing…It’s not even DirectQuery support for Dataflows, neither dataset discoverability (which are both, by the way, very cool additions). Guess what – Paginated Report visual has just arrived into Power BI Desktop! At this moment, it’s still in preview, but the excitement around is huge.
I hear you, I hear you…Who needs this thing at all?! Why would one use the (almost) deprecated technology in super modern shiny Power BI solutions?! Even more, Paginated reports are almost exclusively boring tables + matrices. We have these two in Power BI with waaay more customization options and properties to make them lot nicer and better looking.
We, old people, tend often to say: “you know how it was done in my younger days…”, or “we did exactly like that X years ago…” And, Paginated reports came into our lives way before Power BI. In 2004, Microsoft introduced SQL Server 2000 add-in called SQL Server Reporting Services, and this tool became a reporting standard for the first decade and a half of this century (some will argue even longer, till nowadays).
Things in the data area evolving fast! Extremely fast! So, new challenges required fresh solutions, and Power BI was introduced in 2015 to answer as many business reporting questions as possible, in the most efficient and eye-catching way. However, same as SSAS Multidimensional, which still resists giving up (even though Microsoft pushes everything to Tabular in recent years), SSRS is an integral part of many legacy BI solutions that still work – and not just work, they work quite good!
Ok, the number of visualization types and their customization might look awkward compared to Power BI, but, hey, we could’ve written Visual Basic to extend built-in features! Raise your hand everyone of you who used something like the following code snippet to make your table rows color alternating:)
=iif(rownumber(nothing) mod 2 = 0,"LightGrey","Transparent")
Yeah, I know, it’s much easier to format your table in Power BI and just click on Alternate rows option, but VB is much more fun:)) (just kidding, of course)
I myself thought 2-3 years ago that SSRS is dead…Oh, how wrong I was! Do you know the movie: “No country for old men”? In my case, it could’ve been easily translated to: “No SSRS for old (data) men”… Even though most of the companies migrated to Power BI and adapted their reporting solutions to fit into a new cloud environment, there is still a significant number of clients who are not willing to discontinue using good old paginated reports.
No SSRS for old (data) men
And, believe me, I saw a lot of hybrid solutions, where the majority of the reports were migrated to Power BI, but certain reports remained in paginated form, without any intention to recreate them in Power BI…Why is that way, I hear you ask? Isn’t Power BI a more robust, more efficient, and more powerful tool? Of course, it is! There is no single doubt about it. If you look from a performance perspective, VertiPaq is a beast that can compress and process enormous amounts of data blazingly fast…From a data modeling perspective, I can bet that Power BI is the most comprehensive solution at this moment. You can extend traditional data modeling principles using various powerful features, such as Composite models, role-playing dimensions, Dataflows, and so on.
Not to tell about the capabilities for data transformation and data shaping, to prepare your data in an optimal way for the final reporting solution.
Paginated reports is not an alternative to Power BI!
Of course, if you put Power BI vs SSRS head-to-head, the winner is obvious! But, if you compare these two tools head-to-head, feature by feature, you are missing the point. Paginated reports are not here to be an alternative to Power BI – they are here to complement Power BI! Simply put, there are some certain features that SSRS offers, which Power BI simply can’t replicate. For example, if your users insist on pixel-perfect, printable, or easily exportable reports, there is no better option than a paginated report! Their name says all – they are called paginated, because they are designed to fit well on the page!
Up until now, integration between paginated report and Power BI report was not possible. It was either one or the other. Now, with Paginated Report visual, you can take advantage of the best features from both worlds!
Creating Paginated report
To be able to use Paginated report visual, you first need to build a paginated report itself. So, let’s go and build a very basic paginated report, using Adventure Works sample database. I’m intentionally keeping things simple, as the purpose of this article is not to go deep into Paginated report creation process, but more focus on integration between Paginated report and Power BI.
If you plan to use Paginated reports, you MUST have some sort of Premium license – EM1-EM3 SKUs, P1-P3 SKUs and A1-A6 SKUs. It also is available on a per-user basis with Premium per user, which is built on Premium Gen2 and also in public preview. It’s important to keep in mind that the workspace you are publishing the Paginated report to, must be defined as a Premium workspace
In order to build a Paginated report, you’ll need a separate tool, called Power BI Report Builder. If you used to work in SSRS Report Builder, the whole environment will look familiar. Here is the query I’ll use to create a dataset for my Paginated report:
SELECT p.Color, fsi.SalesAmount, d.FullDateAlternateKey AS [date] FROM FactInternetSales fsi INNER JOIN DimProduct p ON p.ProductKey = fsi.ProductKey INNER JOIN DimDate d ON d.DateKey = fsi.OrderDateKey WHERE d.FullDateAlternateKey >= @dFrom AND d.FullDateAlternateKey <= @dTo;
Basically, I want to show product color, sales amount and date for every single transaction from my FactInternetSales table. As I said, quite basic setup.
Since my query is parameterized, I need to map parameters (in my case, those are starting and ending date). In case you’re using additional parameters (for example, color), make sure that you map them too. I’ve put a simple matrix on the report canvas, and I’m ready now to publish the report to my workspace:
You can immediately notice that the Paginated report differs from the “classic” Power BI report by looking at the icons next to the report name. And, if I run the Paginated report, it renders nice to show me results based on date parameters I’ve set:
So far, nothing special, as you had to decide whether you want to use Power BI or Paginated report…
Run Paginated report INSIDE Power BI report!
And, here is where the real magic happens! Now, you can integrate Paginated report into your Power BI report and run it from there! Let’s go step by step to see how it’s done…
Within Power BI Desktop, I’m using exactly the same dataset (AdventureWorksDW2017) and I’ve created the same matrix as in the Paginated report previously. Now, I’ll drag brand new Paginated Report visual on the report canvas and follow the instructions to connect to the My Paginated Report.
Now follows the interesting part, as you’ll need to configure a few things. After I’ve selected the paginated report I want to connect to (in my case, My Paginated Report), I need to provide parameter values, so that the visual can be cross filtered from within Power BI! Therefore, I’ll create two measures to use them to feed the parameter values:
dFrom = MIN(FactInternetSales[OrderDate]) dTo = MAX(FactInternetSales[OrderDate])
I will drag these measures as Parameters for the Paginated report visual and assign those values to my original parameters:
And once I click on See report, you can notice that I’m getting my Paginated report rendered within Power BI directly! How cool is that! And results are the same between two matrices:
There are also additional formatting options for the Paginated Report visual. Obviously, not as many possibilities for customization as with “regular” Power BI visuals, but still useful, especially Toolbar and Parameters properties:
How it works in the background?
Since the visual is fully responsive in terms of cross-filtering, let’s check what happens if I change the slicer values:
As you would expect, Power BI visual immediately reflect the changes, but for Paginated report visual nothing changed. By default, you need to explicitly click on this Apply changes button for new slicer values to be propagated to an underlying data source. You can change this behavior by enabling Auto-apply filters in Format pane, but I would suggest not to do it, as default setup was specified with query reduction in mind. We will come soon to explain what is going on in the background when you change the slicer values…
So, I was curious to see what happens under the hood when you render paginated report within Power BI and how the data is being retrieved. Let’s first launch DAX Studio and capture the queries generated by Power BI:
Hm, that’s strange, as there is no SQL code generated, and I would expect to see something like a SQL statement. This query basically calculates only our measures for dFrom and dTo parameters. So, I’m turning on a good old SQL Server Profiler to check what is really going on down there.
And here it is! This is the SQL statement that retrieves the data from the AdventureWorksDW2017 database. Looks familiar? Yes, exactly, that’s the query we’ve used to create our original dataset for the paginated report! However, Power BI generated a dynamic SQL statement, wrapping our original query with parameters grabbed from the Power BI slicer (that’s the query we saw in DAX Studio)!
If I change the slicers values, we should see the new dynamic SQL query with different parameter values (I’ll set starting date to June 25th). Let’s check if that’s the case:
BAM! There you go! As expected, we have a new SQL statement – in fact, the base statement is the same, but parameter values were changed and new dynamic SQL was generated and executed.
Which leads to a conclusion that Paginated Report visual works in a DirectQuery mode!
Exporting the data
Well, that was all nice, but I hear you asking: why do I need Paginated Report visual in my Power BI report in the first place? I’ll publish our Power BI report that includes Paginated report visual to a workspace and I’ll show you the use case.
Let’s imagine that one of the users requests is to export the data from the visuals.
When you’re exporting the data from Power BI original matrix, the only available format is xlsx. On the other hand, if I click on Export within the Paginated Report visual, look what I have at my disposal:
Wow! Not just Excel! I can export to a whole range of different formats, including pdf if I need to print out something (oh, yes, believe me, there are a lot of people around that still prefer to print their reports), or pptx in case I need it for my fancy PowerPoint presentation! Don’t forget why are Paginated reports called Paginated at first place:)
Next, what happens if I have more data in my visual than it can fit on one page and want to export it to pdf? Let’s check how Power BI matrix renders to pdf:
Oh, man, I’m missing data! Why is that? Where are my dates between June 3rd and June 30th? I saw them in my Power BI report. Yes, you did. But, you can scroll the table in the Power BI report, and you can’t scroll the image in pdf!
Let’s check what happens if we export data from the Paginated Report visual:
Oh, how nice and clean that looks!
The possibility to render Paginated Report directly within Power BI report is an immense addition to the already wide range of capabilities that Power BI offers. Having another (very powerful) tool under the belt can only increase the business value your reporting solution provides.
There will always be users that insist on pixel-perfect, print-friendly data, and Power BI on its own couldn’t address these requests properly. But, now, by integration of mature and established technology, such as Paginated reports, you can satisfy all requests from within a single location, even applying all the filters to the data at once!
Despite some limitations, I believe that Paginated Report visual is one of the greatest improvements in Power BI recently!
Thanks for reading!
Last Updated on July 2, 2021 by Nikola