Unable to see data tables in query editor when connecting to a shared Semantic model

[Walter01]

I granted build and read to a person in the semantic model under shared permissions.  Within PowerBI Desktop, the person is able to connect to the semantic datasource through PowerBI Semantic Models datasource and then build visuals off of the data in a new workspace not related to the original.  I want the person to create new tables in their workkspace and interact with the PowerBI Semantic Models datasources.  It asks the user to add a local model and then select the connected datasources.  It goes into PowerQuery Editor and they cannot see any of the tables.

How can I allow this user to point to my semantic model and also interact through PowerQuery Editor to see the referenced datasource?  ie =nameofatablefromsemanticmodeldatasource without giving them the ability to modify my data?

[Poojara_D12]

Hi @Walter01 

• Grant read-only access to the semantic model.
• Allow the user to connect via DirectQuery to the semantic model, referencing it in their Power Query Editor without making any changes to the source.
• Use Reference in Power Query to bring in tables from the semantic model while keeping the data model intact.

This will let them interact with the data model for visuals and new tables, but they will not be able to modify the original model or data.

Did I answer your question? Mark my post as a solution, this will help others!

If my response(s) assisted you in any way, don't forget to drop me a "Kudos" 🙂

Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Consider Subscribing my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS 

[Gabry · Accepted solution]

Hello,

When you connect to a semantic model, you establish a live connection. You can find more details here: Live Connections in Power BI.

With a live connection, the Data View is not accessible.

If you need to modify the model, you’ll have to use a DirectQuery connection. This allows you to import the table using DirectQuery, though it comes with certain limitations.

The best solution imho is to copy your Power Query code into a Dataflow and then retrieve the data from the Dataflow.