Unable to see semantic model in Power BI

[ManasRout]

Hi Team, I am getting a new type of issue I have access to a workspace as Member and I can publish the report but unable to see the semantic model for publish report as well as unable to download other reports and not able to see semantic model as well.

[Olufemi7]

Hello @ManasRout,

This usually happens when Build permission is missing on the semantic model (dataset).

Even if you have Workspace Member access, that alone doesn’t allow you to see or reuse a semantic model. You’ll need the admin to grant Build permission on the dataset via Manage permissions.

Docs:
Build permission for shared semantic models 

[ManasRout]

Hi @Olufemi7 but I can able to publish a report in power bi service but not able to see the pulished report semantic model.

[Olufemi7]

Hello @ManasRout,

 Yes this can happen.

Even if you can publish a report, that doesn’t automatically mean you can see or reuse the semantic model (dataset). Publishing is allowed through workspace access, but accessing a shared dataset is controlled separately.

In most cases, this happens because you don’t have Build permission on the semantic model, so it won’t show up for reuse or connection.

You’ll need to ask the workspace admin to grant Build permission on the dataset.

Microsoft documentation:
Build permission for shared semantic models 

[ManasRout]

@Olufemi7 I am using excel as data source when I publish it doesn't show me semantic model details as well as no delete option for report. 

[Olufemi7]

Hello @ManasRout,

Thanks for the details, that helps.
Even when Excel is used as the source, Power BI still creates a semantic model after publishing, so it should normally appear in the workspace. If it’s not showing and you also don’t have a delete option, it usually points to a permissions issue in the workspace.
You may still be able to publish reports, but not fully manage the underlying items. Worth checking your workspace permissions with the admin.

[v-aatheeque]

Hi @ManasRout 

Have you had a chance to look through the responses shared earlier? If anything is still unclear, we’ll be happy to provide additional support.

[ManasRout · Accepted solution]

Hi @v-aatheeque , @Olufemi7 This issue is resolved it was blocking Zscaler due to some network issue. Zscaler team fix this issue. Thank you!

[v-aatheeque]

Hi  @ManasRout 

Glad to hear the issue is resolved and that the root cause was related to Zscaler/network blocking.

If any of the suggested solutions helped during the troubleshooting process, please feel free to acknowledge them. It will be helpful for other community members who may encounter similar issues in the future.