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.
The issue occurs because Free users can’t build reports from semantic models unless both the model and the report workspace are backed by a Fabric capacity. Previously, the user was on a PPU trial, which allowed it. Now that the trial is gone and their workspace isn’t on Fabric capacity, they’re being asked to upgrade. To fix this, move their reports to a shared workspace assigned to the Fabric F64 capacity and ensure they have Build permission on the model. Personal workspaces can’t be assigned to capacity, so they must work in shared Fabric-backed workspaces.
BhavinVyas3003 I don't think this is exactly the case, although useful to know. This is occuring when the free user is trying to build a new report from scratch. As soon as they try to connect to the semantic model, they're getting the license notice. They've not even had a chance to save the report or work from the model.
My talk about the users presonal workspace could just be a red herring as it was my assumption it was caused by this still being trial-[whatever alphanumerics].
Any other ideas? I'd prefer not to have to raise a ticket as I'm leaving the business very soon and won't be able to see it through.
