Showing results for 
Search instead for 
Did you mean: 

Get Table information from dataset Programmatically

Hi All,


Is there a way to programatically get the information of datasource & tables used in a dataset (like some kind of metadata). 
I saw there is a GetDataSet API, but that works on the datasets that are published using REST API. It will be practically impossible for us to publish a report using REST API given the amount of data we have. 

Any suggestions please?  

Super User
Super User

You can use any XMLA client (like SSMS, DAX Studio, ALM Toolkit etc) to connect to the XMLA endpoint of the dataset (assuming, of course, that you have access to the dataset) and pull down all the meta data.

That is good information. Thanks @lbendlin . I see that it is only supported for PowerBI premium subscriptions. 
Currently we don't have PowerBI premium. Do you know of a way which can work for us with Standard PowerBI subscription & workspace.

Apologies, i did not qualify that. I have no experience outside of Premium. Maybe you need to be made a workspace member?

So I got hold of a premium workspace and am able to connect to the XMLA endpoint. 
So far, I could get information like tables and columns from dataset perspective.

We want to actually find the source table information, not the ones created in powerbi report/dataset. Sorry if that was not clear in my initial post.
@lbendlin is there a way to get the source table information and the actual queries which are used to create the dataset tables.


Thanks @lbendlin. I tried that at I dont see information of actual source in response. 
I still see the information about dataset tables, not the actual source SQL tables.

Now you got me really confused.  Are you after the schema information?


See if this blog helps you.

Sorry for the confusion @lbendlin .
My need is to programatically find the list of source tables which are backing a given powerbi report.

That's what I gave you with the DMV query.  You need to take that M code and parse it. It contains the server, database and query.


Annotation 2020-07-17 170405.png

Frequent Visitor

I had the same problem as @pgelli when using @lbendlin 's suggestion of SELECT * FROM $SYSTEM.TMSCHEMA_PARTITIONS; I was receiving the DAX QueryDefinitions and not the M Query defintions (super useful, just not what I needed).  What solved it for me was instead using  SELECT * FROM $System.DISCOVER_M_expressions.  Hopefully this saves someone else some time for this use case.

@lbendlin , I am afraid I am getting different results for that query:



These are not the tables present in our Source. Am I missing something? 

Most likely you connected to the wrong endpoint. Different dataset maybe?

I verified that I am looking at right dataset. However, PowerBI report is built using "import" and not "direct query".
Does it make a difference @lbendlin ?

No, once you access the dataset it doesn't matter much if  the query connection type is import/ direct query or mixed.  


I just tried it with one of my direct query datasets and got the expected result. 


As expected it will not work at all with live connections.

Helpful resources

June 2022 update 768X460.jpg

Check it out!

Click here to read more about the June 2022 updates!

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

Power BI Dev Camp Session 23 768x460.jpg

Check it Out!

Mark your calendars and join us on Thursday, June 30 at 11a PDT for a great session with Ted Pattison!

June 20 episode 7 with aka link 768x460.jpg

The Power BI Community Show

Join us on June 20 at 11 am PDT when Kim Manis shares the latest on Azure Synapse analytics, the Microsoft Intelligent Data Platform, and notable Power BI Updates from Microsoft Build 2022.

Top Solution Authors