Forum Discussion
Impactful IndividualReport Error
Hi powerbiexpert22,
Since the report is connected to a semantic model hosted in the Prod workspace, I would first check whether you still have access to that semantic model.
A few things to check:
- Confirm you have permission to the Prod workspace/semantic model.
- Open the semantic model directly in the Power BI Service and make sure it is accessible.
- Check whether the semantic model was renamed, replaced, or republished recently.
- In Power BI Desktop, sign out and sign back in with the same account that has access to the Prod workspace.
- If the report uses a live connection, check whether the connection is still pointing to the correct workspace and semantic model.
- If the semantic model was recently redeployed, verify that the report connection wasn't broken during the deployment.
If other users can open the same report successfully, then I would focus on your account permissions or cached credentials in Desktop.
If nobody can access it, then the semantic model itself or its workspace permissions should be checked by the owner/admin.
Also, if this started immediately after a deployment from UAT to Prod, I'd specifically check whether the semantic model ID/connection was changed during the deployment.
Impactful IndividualHi ShahRukhSameer ,
i realized that i do not have prod workspace semantic model permission, I need to analyse data mismatch issue on report, do i need build permission or read is enough? i may create new page on exusting reports and try to add new measures or calculated columns for analysing the issue however i do not want to overwrite existing semantic model on prod workspace
Solution SageHi powerbiexpert22,
If you only need to investigate the data mismatch, I would avoid making any changes to the Production semantic model.
Read access should be enough for viewing the existing report and checking the data. If you want to connect to the Prod semantic model from Power BI Desktop and build your own analysis/report on top of it, then you would need Build permission.
In your case, I would probably request Build access but keep the Production semantic model unchanged.
You can then create a separate report/page for the investigation and add your own measures there. I would avoid creating calculated columns in the Prod model, since those would actually modify the semantic model.
So basically:
Read → view/analyse existing content
Build → create your own report using the Prod semantic model
Modify semantic model → not required for your investigation and should be avoided in Prod
That should let you investigate the mismatch without affecting the existing Production model.