Pricing, Licensing, and System Requirements for On-Premise Power BI Report Server Deplyment
I'm planning to deploy Power BI Report Server on our on-premise servers. Could someone provide details on the total pricing, the type of licensing required, and the system requirements for this setup? Thanks in advance!
Deploy Power BI reports programatically with different SSAS connections per tenant
Hello, we develop and manage a software as a service platform using PowerBI embedded with Analysis Services in Microsoft Azure. Our CI/CD pipeline process provides an SQL database, Analysis Service Database, Web Application, PowerBi Embedded Workspace and multiple services per customer. Everything works fine for these steps. But the report deployment is still a manual process: - Open PowerBI Desktop - Open the report in question - Connect to the QA SSAS server and select the database for the customer for this specific deployment - Publish the report and select the PowerBI embedded workspace for that specific customer - Check visually that the report is working via Power BI Portal We would like to deploy the reports using PowerShell, but we could not find a way to change the connection string. We found multiple ways to change connection strings if no SSAS is involved, but we need SSAS. Any ideas how to solve this? Kind regards, Michael
Deployment failed for file for PowerBI Tier2 Environment Dynamics 365 Finance and Operations
There are 3 ways to connect PowerBI with Dynamics 365 Finance and Operation. OData (Direct call data entity) Azure DB (Export from BYOD) Entity Store (Create Measure to direct query from D365 Finance and Operations) I'm using Entity Store to connect their standard (OOB) PowerBI report with D365 Finance and Operations. I have created a new PowerBI app registration in dev instance and configure in Dynamics 365 Finance and Operations. I'm trying to deploy the PowerBI report from the Deploy Power BI files from the D365 Finance and Operations and got the error Deployment failed for file. There is no further detail with this error. Does anyone who how to fix it? Thanks, Wajihullah
Report Server data refresh options
Hi all, We are looking into deploying PowerBI reports to our customers using the PowerBI Report Server. Our master data is in a Sql Server database(s). We are trying to figure out the optimal deployment model. Our main criteria are: - Minimal impact on the master database during business hours. - As up-to date data in the reports as possible, (but not strictly real-time) - Not requiring Azure AD / O365 accounts for our end customers Current plan is - to host Tabular SSAS - schedule an hourly incremental/partitioned refresh, - reports with live connection to the SSAS - embed reports in our software and wrap authentication in our existing authentication Is this a viable solution? Can the plan above be improved in any way? Also, are there better ways to refresh the data, for example to combine live and warehoused portions of data? Thanks for any tips.Enterprise reporting artefact deployment strategies with PBIRS
We have a problem currently with the fact that .pbix files are very different from any other SSRS reporting artefact in terms of enterprise readiness for deployments. We have a full-featured deployment system that can deploy entire trees of reporting artefacts along with replacing datasource definitions at deploy time depending on the target environment (DEV/TRAIN/PROD) etc. This has been working nicely for years but now we are moving to PBIRS and away from SSRS native mode, users want to be able to deploy .pbix artefacts in the same way. This seems to be basically impossible because: The file format of .pbix is not editable programatically (unlike every SSRS artefact) and so data sources cannot be changed directly which means they have to be uploaded to PBIRS and then changed with the REST API .... but ... Datasources inside a .pbix file have no name and even the ids change every time the file is deployed to a PBIRS server. So, there is no way of matching datasources to the database of connections we use to determine datasources for a target environment during deployment. These issues make .pbix files really poor in terms of enterprise deployments. If anyone knows any way around these issues, I would be interested ... It really is a basic part of any enterprise grade managed reporting solution to be able to change reports (datasources, parameters, cacheing etc). during deployment depending on the target enviromnent.Scripting RDL Files to PowerBI Server
We have a number of SSRS reports that we have migrated to a PowerBI site. We are looking for a way to deploy these via a script so that we can manage report changes from our source control automatically. I haven't been able to get RS.exe to write to our PowerBI site as it seems to be looking for SSRS Report Server or a SharePoint server, but not PowerBI server. We can deploy manually via Visual Studio, and this is working, so it must be fine under the hood. Suggestions welcome.
New installation of power-bi on-premises
Hi, A new installation of the power-bi on-premises was installed in our server. I did manage to configure the power-bi part, but now the report server part is giving me an error: Invalid name space. I think it has to do with the fact that there are two ssrs servers installed in one machine, but I am not sure what to do. Also, I am trying to deploy a power bi report into the on-premises server, but I am not sure how. From the desktop it only lets me deploy to the cloud. How do I fix that? Thanks Astrid
Error File too large although File is empty
Hi all, When I try to save a report from my PBI Desktop to my PBI Report Server I always get the error 'The file is too large and cannot be uploaded'. However, if I upload the file manualy on my PBI Report Server it works. I even tried with an empty file and it still says it is too large. My MaxFileSizeMb is set for 2Gb. Has anyone experience something like this and/or has a solution/idea? PBI Desktop Version: 2.56.5023.1043 64-bit - March 2018 PBI Report Server Version: Version 1.2.6690.34729 (Build 15.0.2.402) - March 2018
