Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
Wanted to get some input on this in light of "enhanced metadata" feature.
Switching from import to direct query has not been possible earlier in Power BI Desktop. One has to make a new table in PowerQuery instead, adding all relationships/calculated columns/ column settings again manually, delete the old table and rename the new one. Moreover visuals that use the table will give errors (even though the name of the table is the same).
However, now I see that I am able to change the table partition from Import to DQ in "TabularEditor". And it seems to work...
Is this now "safe" in light of "enhanced metadata" feature?
Hi, it became a feature in October update i think...
It reverts when using "External tools in PBI Dekstop", but when editing the .pbit itself directly in Tabular Edtior it works.
@Anonymous , if "enhanced metadata" is under preview then you need a bit careful. But if it already came as feature. Should be more trustable in that case.
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Fabric Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 22 | |
| 20 | |
| 14 | |
| 13 | |
| 13 |
| User | Count |
|---|---|
| 63 | |
| 41 | |
| 40 | |
| 39 | |
| 38 |