Forum Discussion
Error when selecting a semantic model to build from
Hi DamoUK,
Thank you for the update.
Based on my understanding, since other free users can access the same semantic model without any issues, and the affected user is able to work with existing reports but cannot create new ones from the same model, this appears to be an issue specific to the user’s cached session or legacy licensing token.
Kindly follow the steps mentioned below with the affected user to resolve the issue:
- Instruct the user to sign out completely from Power BI service and Microsoft 365 across all browsers.
- Clear the browser cache, cookies, and site data.
- Reopen Power BI in a new browser or incognito window.
- Ensure that the user starts a new report from within the correct Fabric-backed workspace, and then connects to the semantic model.
This process helps to reset cached license artifacts, which may be lingering from the expired PPU trial.
We hope the information provided will help resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.
Hi DamoUK,
Thank you for the update.
Based on my understanding, the license prompt shows up right after selecting the semantic model, even before saving the report. This means Power BI checks the license at the time of connection, not only when you save or publish the report.
Please follow these steps to help fix the issue:
- Make sure the user creates the report directly inside a shared Fabric backed workspace, not in a personal workspace or on the browser landing page.
- The user should click the New report button inside the correct workspace and then select the semantic model. This ensures the right context and capacity.
- Confirm that the semantic model is hosted in a Fabric backed workspace.
- Ensure the user has Build permission on the semantic model and Viewer or higher role on the workspace where the semantic model is hosted. Both are required for Free users to discover and use the model in report building.
This approach is very important because trying to connect from outside the capacity context, like from Personal or My Workspace, will cause the license check to appear.
We hope this information helps you solve the problem. If you have any more questions, please feel free to contact the Microsoft Fabric community.
Thank you.
v-pnaroju-msft we use Apps for permissions to reports to simplify management of audiences. Because they're permissioned to the report through the App, I've only added build permissions to the model. Could you confirm this negates the need for viewer permission to the workspace please? I would prefer not to have to start messing with permissions at the workspace level as well as App!