Forum Discussion
Deployment Pipelines & Front End Visual Failures
- 1 year ago
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
Hey again!
Thanks for the extra details—super helpful!
Since you’ve confirmed that:
- No parameters are involved,
- Manual deployment to Test works fine,
- Gateway and service account setup is consistent,
…it really does sound like something in the Deployment Pipeline process itself is causing the issue.
A couple of thoughts:
- Deployment Rules: Even if you’re not using parameters, are there any dataset rules defined in the pipeline that might be altering something silently? Sometimes even a small rule (like changing a connection string or table mapping) can break relationships or cause tables to not load.
- Model Binding: Pipelines might be re-binding the dataset in a way that breaks the internal metadata or relationships. That could explain why the Calendar table seems disconnected and the Fact table appears empty.
- Refresh Timing: After deployment via pipeline, is there an automatic refresh happening? If not, the dataset might be in a stale state until manually refreshed.
Since manual deployment works fine, one workaround (for now) might be to deploy manually until the root cause is clearer. But I’d definitely recommend raising this with Microsoft support too—it feels like a pipeline bug or unexpected behavior.
Let us know if you dig up anything else!
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
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