Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hello. Can you please tell me that if the data which is fetched as a direct query into power BI is not a table but a VIEW created in the source.. In my case it is Snowflake tool... Still does Dynamic M query parameter can be applied on the same with the help of slicers? Or is it compulsory to fetch data from Table only?
Hi Hari. Thanks for reaching out... However my query is still not resolved. Actually we have our data source as SnowFlake tool.... So my data is available in various tables in it and Big Data team created a Non Materialistic VIEW to clubbed the data at one place and we are using that VIEW to call the data into Power BI in direct query mode. It gives an awfull performance in Power BI as just to load the data we have to wait for like 1 to 2 hrs. My data has 73 million records and growing. On checking found out that Power BI runs every column available in the VIEW as a seperate query and not as one... And this VIEW is called into Power BI for like 2 times as directed query and 1 time as Import Mode for every individual column of the VIEW... So when we open the report again created on VIEW it is running same SQL query for all the columns present in the VIEW individually and not as one. For ex. If I have 100 columns in the VIEW, the SQL query not run for 2 VIEW but for 200 columns... But the same is not the case when there is a Table. In Table the SQL query run as 1 only. Can anyone tell me why is it happening and how to resolve it?
Check below for reference.
Thanks
Hari
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
Check out the November 2025 Power BI update to learn about new features.
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |