On the list of features which are missing from SSRS (in Model Driven Apps, at least), I’d rate this #1. And, of course, where there is Rest API, there can be a Power Automate Connector: It’s more than Power Automate – it’s just that there is Rest API we can use with Power BI.
#Power bi report builder vs desktop update#
Update (Jan 26): there is a follow up on the security topic in the next postĪnd I think here is the kicker, really… Power Automate Integration Once I’ve managed to share this, I’ll probably be able to see how it works with the datasource access, too. Could it be because of the TDS datasource? Possibly, have to track it down yet. I have to admit I was not able to share my report yet, since there is always an error. There are two sides there:Īccess to the report is controlled through report sharing: Once there, there is no need for the report builder anymore – report users can run this report directly from the Power BI website: This report can be stored in the Premium Power BI WorkspaceĪnd, once it’s saved, we can go to the Power BI web site in the browser and see the report there: That easily leads to the following report:Īnd we can run it in the Report Builder right away to see the output: I mean, it seems to be a no-brainer that writing a SQL query is much easier than creating FetchXML: Still, if and when it does go to the GA, this comparison will make even more sense. But, since Power BI Paginated Reports are not solution aware, this may mean deployment is not going to be as easy.Īlso, so far TDS endpoint is still in preview, so, as much as I’d like to be able to say we can rely on this kind of reporting moving forward, I think we’ll need to wait and see if/when TDS endpoint goes to the GA. This may give numerous advantages – using SQL instead of Fetch is, well, a dream came true. There is a direct SQL connection (to the TDS endpoint)
So, assuming SSRS has been covered so many times and you probably know what’s doable with SSRS, let me cover some of the Power BI Paginated Reports features. Most likely, if you are thinking of getting SSRS reports developed, you’ll need to start paying the developer, and this is not cheap either, so, in the end, if you tried comparing licensing fees only, it might not give you an accurate picture.
This is not to say that Power Apps licensing in general is cheap these days, and this is not to say that everybody can develop SSRS reports. That last one can be a big deal if you are thinking of switching to Power BI Paginated Reports, since the first thing you’ll probably realize is that you need a Premium Power BI workspace.Ī Premium Workspace will cost you, quite a bit. Meaning that it comes with model-driven apps. That said, we have to use FetchXML to build those SSRS reports, and that kind of limits us in terms of the capabilities, since FetchXML, even though quite powerful, does not offer the same capabilities as SQL.Īnd SSRS is “free”. However, we can go to the model-driven app and run reports from there. SSRS will run on the reporting server, and, as far as model-driven applications go, it’s always been the case that reporting server would have been hidden from us, developers. Although, it will probably look surprisingly familiar to anyone who had some experience with SSRS: Unlike SSRS, Power BI Paginated Reports are supposed to be designed using a tool called Power BI Report Builder. They are both meant to deliver pixel-perfect reports, and, actually, Power BI Paginated Reports are using the same “rdl” format as SSRS. To start with, both are somewhat the same. So, how do Paginated Reports fair against SSRS? Now that SSRS authoring tools have finally been updated (and there is a great article Nick Doelman published the other day on this topic), it might be the right time to ponder on which technology we should be using moving forward since there are two now:
0 kommentar(er)
