Forum Discussion
Migration SSRS to POWERBI
- 9 months ago
Hi Roomie117 ,
When you are deploying paginated reports through GitHub, the process works a bit differently from publishing directly in the Power BI Service. Publishing from Report Builder is fine for quick, manual work, but in a Dev environment where you want repeatable deployments, GitHub becomes the source of truth.
The RDL files stored in your repository should be the versions that move through your environments, and your GitHub workflow can publish those reports to the workspace using Power BI’s APIs or PowerShell modules. The one thing GitHub cannot do is create data sources in the Service, so those need to be set up manually in the workspace ahead of time, along with the gateway connection for your on-prem SQL Server. Once the data source exists, your pipeline can publish the RDL and rebind it automatically.
This way, you keep a clean CI and Dev process while still supporting manual publishing if you ever need it, but GitHub should be considered the main deployment path when you're managing environments.
Best Regards,
Tejaswi.
Community Support
Roomie117 , I am assuming you are using Github actions for the deployment and using either FabricPS module or the older PowerBIMgmt module. In either of them, you should be able to deploy rdl files to the service.
As for datasource connection creation, you need to create the connections in Power BI service and this cannot be created programmatically yet. You should be able to bind the report to the appropriate connection programmatically.
Hope it helps!
I am using an older Power BI model. However, when I publish the report to the workspace, I don’t see the source/report available to update in the Power BI workspace.
- alish_b9 months agoSuper User
Hey Roomie117 ,
Since you said the report itself is not present in the workspace, then maybe there is an issue in the deployment script. It could be possible that the deployment script was written with only pbix files in mind. If that is the case then you will have to extend the deployment script to consider the rdl files.
Hope it helps!