Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
akito
Frequent Visitor

Why I cant see my Direct Query tables in Power Query - (Power BI Dataset)

Hi All,

 

I am not able to see tables in Power Query that are from Direct Query stoarge connection that is linked to Live Power BI Dataset. I only can see my tables from excel as I have mixed storage connection (Direct Query and Imported).

I am trying to create a new table from tables (Append or Merge) that are in Direct Query storage. 

 

Note: I am pretty new in Power BI -  who is trying to switch from Tableau to Power BI 🙂

 

akito_0-1646195963501.pngakito_1-1646195973142.png

akito_2-1646196043054.png

Regards,

Akito

2 ACCEPTED SOLUTIONS
BA_Pete
Super User
Super User

Hi @akito ,

 

In Power BI, you only see tables in the Data section if those tables are going to be stored in a static state (i.e. IMPORTed) within your report. This Data screen is showing you all the tables/data that are stored within your report after refresh.

 

With Direct Query, no tables/data are stored within the report after refresh, so you can't see them here.

When using Direct Query, each of your report visuals generates its own SQL query specific to what that exact visual needs to show and sends it directly to the source when the report loads and/or when filters/slicers are changed. This allows for reports to display near-live data in visuals, but also significantly restricts the transformations and general control/visibility of the data between the source and visuals.

 

If you are happy to display data that is not up-to-the-second live, then you should be using IMPORT as your data acquisition method, which allows you full control over data structures and transformations.

If you need to have up-to-the-second live data, then you will want to use DIRECT QUERY or LIVE CONNECTION, but you will probably need to get the data structured at source, as you will not have significant control over it from within Power Query/Power BI.

 

Transformation operations that you mention, such as Append and Merge, would almost always need to be done on the source when using Direct Query, and definitely when using Live Connection.

 

Pete



Now accepting Kudos! If my post helped you, why not give it a thumbs-up?

Proud to be a Datanaut!




View solution in original post

Hi @akito ,

 

I suspect this is due to the fact that you are using a data acquisition method that DOES NOT store data with the report, so the original fields are not visible. However, calculated columns must be materialised into memory at runtime, so ARE essentially 'stored' with the report and are, therefore, visible.

 

Pete



Now accepting Kudos! If my post helped you, why not give it a thumbs-up?

Proud to be a Datanaut!




View solution in original post

3 REPLIES 3
akito
Frequent Visitor

Thanks @BA_Pete , that make sense. maybe another quick stuipid question :). I cant see all the data fields in DAX but only calculated ones. Is this because of my dataset nature  ?. 

Hi @akito ,

 

I suspect this is due to the fact that you are using a data acquisition method that DOES NOT store data with the report, so the original fields are not visible. However, calculated columns must be materialised into memory at runtime, so ARE essentially 'stored' with the report and are, therefore, visible.

 

Pete



Now accepting Kudos! If my post helped you, why not give it a thumbs-up?

Proud to be a Datanaut!




BA_Pete
Super User
Super User

Hi @akito ,

 

In Power BI, you only see tables in the Data section if those tables are going to be stored in a static state (i.e. IMPORTed) within your report. This Data screen is showing you all the tables/data that are stored within your report after refresh.

 

With Direct Query, no tables/data are stored within the report after refresh, so you can't see them here.

When using Direct Query, each of your report visuals generates its own SQL query specific to what that exact visual needs to show and sends it directly to the source when the report loads and/or when filters/slicers are changed. This allows for reports to display near-live data in visuals, but also significantly restricts the transformations and general control/visibility of the data between the source and visuals.

 

If you are happy to display data that is not up-to-the-second live, then you should be using IMPORT as your data acquisition method, which allows you full control over data structures and transformations.

If you need to have up-to-the-second live data, then you will want to use DIRECT QUERY or LIVE CONNECTION, but you will probably need to get the data structured at source, as you will not have significant control over it from within Power Query/Power BI.

 

Transformation operations that you mention, such as Append and Merge, would almost always need to be done on the source when using Direct Query, and definitely when using Live Connection.

 

Pete



Now accepting Kudos! If my post helped you, why not give it a thumbs-up?

Proud to be a Datanaut!




Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors