Forum Discussion
Helper IVDeployment Pipelines - Reports cannot be open onthe deployed workspace if calc fields in the report
Hello
I have this scenario:
- Created a reports on PBI desktop (many visuals/Pages). One table has a calculated field which just switch case (if this then show this and that) . I have few DAX measures as well.
- Pubished that report to PBI workspace which is assigned a fabric Capacity. All is working. I can see the reports in Power BI service just fine.
- I created a Deplpoyment Pipeline to move reports from DEV to UAT workspace as below. Only decided to deploy this particular report. Report has been refreshed and has the latest data.
- Although this is the same env in fact (DEV and UAT) they come from the same Oracle DB server and I don't have a choice to change the user name . Not sure how the Rule can be applied. Never the less this report is deployed to new UAT workspace.
However when I try to open the report I get error message as this:
What have I missed?
Thank you,
When you deplooy through the deployment pipelines, it does not trigger an automatic refresh of the semantic model in the workspace. You just need to refresh the UAT semantic model and the data will flood in for you.
4 Replies
- d_m_LNK
Super User
When you deplooy through the deployment pipelines, it does not trigger an automatic refresh of the semantic model in the workspace. You just need to refresh the UAT semantic model and the data will flood in for you.
XhevahirMehallaThanks mate!
I wasted few good hours.
I have another questions though if know it.
Reports created on Oracle Dev db env on the same db server as UAT but difference schema with different user name and password. How do I got around this?
If you're confident that your Power BI version has been deployed to UAT, you just need to refresh the dataset. Since this is a calculated column, it must be refreshed for the values to be recalculated.
- d_m_LNK
Are you using an on prem gateway? If so you will need to create a new connection with this new user to that server/db combo. Then when you create your query to the new table you will need to specify that different username/password. Are these different reports or on the same model? Same model will be tricky not sure how you do that.
