Forum Discussion

DamoUK's avatar
DamoUK
Frequent Visitor
1 year ago
Solved

Error when selecting a semantic model to build from

Our setup: Fabric Capacity (F64). Developers (around 40) assigned Power BI Pro licences. All other business users (around 1,000) assigned Fabric Free licenses. I am the Fabric and Power BI tenant/ca...
Need Help
  • v-pnaroju-msft's avatar
    v-pnaroju-msft
    1 year ago

    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:

    1. Instruct the user to sign out completely from Power BI service and Microsoft 365 across all browsers.
    2. Clear the browser cache, cookies, and site data.
    3. Reopen Power BI in a new browser or incognito window.
    4. 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.




v-pnaroju-msft's avatar
v-pnaroju-msft
Community Support
1 year ago

Hi DamoUK,

Thank you for your update.

Please note that even with Build permission and App access, Power BI still requires the user to have Viewer or higher workspace role to enable semantic model discovery when initiating a new report. App access does not replace the need for workspace level permissions when building reports.

Kindly follow the approach outlined below to resolve the issue:

  1. Assign the user temporary Viewer or Contributor access to the workspace that hosts the model.
  2. Once the report is saved, remove the assigned role. The user will continue to have access via the App.

This method allows you to maintain your App based permission strategy effectively.

We hope this information will assist in resolving the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.