This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreGet Fabric Certified for FREE during AI Skills Fest. This week only. Secure your voucher 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?
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 1 | |
| 1 |
| User | Count |
|---|---|
| 9 | |
| 7 | |
| 3 | |
| 3 | |
| 3 |