Forum Discussion
Deployment Pipelines & Front End Visual Failures
Hi again burakkaragoz ,
So this was solved by Microsoft - something as simple as once it had been deployed through the pipeline (re-allocated to service principal & pointed to gateway etc), I had to go into the report in service - Edit it, refresh the visuals & then re-save it. Which seems a bit laborious for deploying through pipelines, but who am I haha.
Thank you all for your input though regardless. This has been an insightful learning journey
Hi burakkaragoz
The dataset itself doesn't use parameters - I've checked through the back end and also validated under manage parameters within the pbix file itself, as well as within the service looking at the Parameters option once deployed.
When manually reloaded in Dev, it's working fine - but the second it hits Test it doesn't like it. The gateway is pointed and allocated correctly, scheduled refresh works in Dev. It's almost like the deployment pipeline changes something when it moves to Test?
To note, the test (pardon the pun) I've performed here is that I can deploy the dashboard & semantic model directly to the Test workspace without issue - it refreshes without issue and doesn't have these challenges. It's solely when it's deployed through the deployment pipeline that the issue arises.
Additional note, once we deploy to the service we allocate all dashboards & reports to our service account to ensure that all correct gateways are allocated. This ensures a unified approach (for us) and mitigates instances of someone leaving and the report falling over.
From looking at our gateway settings, the gateway will be the same regardless of the workspace it's deployed to given the service account is what owns it
Community SupportHi NikTheRussian ,
Thank you for reaching out to Microsoft Fabric Community Forum.
Below are thr few points that can resolve your issue let us know if you need anything
-
When deploying via the pipeline, Power BI creates a new dataset ID in Test, and it may not retain gateway or credential bindings from Dev.
-
After deployment, please go to Test workspace > Dataset settings > Data source credentials and re-authenticate, even if the credentials appear correct.
-
In the Power BI Service, navigate to Manage Gateways > Datasets tab and make sure the deployed dataset in Test is explicitly mapped to the correct data source and gateway.
-
You can also use Data Source Rules within the deployment pipeline to automatically manage data source mapping across Dev, Test, and Prod.
-
If you're not currently using parameters, consider creating dummy parameters just for managing environment-specific connections.
-
Manual deployment works because it retains the credential and gateway settings, while the pipeline resets them unless manually reconfigured.
-
Reassigning the reports to the service account after deployment is a good practice, but the credentials might still need to be revalidated in the Test workspace.
Regards,
Chaithanya.