Forum Discussion
Migration SSRS to POWERBI
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
hi Roomie117
please check this short blog for migration steps :
SSRS → Power BI: Practical Migration steps
Analytic Pulse Blog
Docynx Productivity Tools
Tool to Generate Realistic Sample Data Instantly online
I am using GitHub for deployments from local to Dev. How should this be handled, considering that we can publish reports directly to the Power BI Service?
Roomie117
do you have deployment pipiline for dev to QA and QA to prod?
if yes then its sorted already, if not then create a pipeline.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 SupportHi Roomie117 ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you.