Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hi @ERing I hope this helps. Thank You!!
In Power BI, when you are using DirectQuery mode, the data model relies on the underlying database's capabilities for processing and transforming data. This means that certain data transformations and type changes that you can perform in Power Query's Power BI Desktop may not be supported when using DirectQuery.
DirectQuery mode is designed to leverage the processing capabilities of the data source, like Snowflake in your case, rather than pulling all the data into the Power BI engine. As a result, some data transformations, especially those that involve changing data types or complex transformations, might not be possible to perform directly in Power Query when using DirectQuery.
Thank you for the detailed explanation.
What considerations should be made when deciding between import and direct query? I find myself using direct query frequently, because my tables often have over 3 million rows, however I find myself challenged by the limitations in direct query.
Should I be using import? At what point is it necessary to use direct query rather than import?
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
15 | |
11 | |
8 | |
8 | |
7 |
User | Count |
---|---|
14 | |
13 | |
9 | |
7 | |
6 |