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
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.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 39 | |
| 37 | |
| 33 | |
| 33 | |
| 29 |
| User | Count |
|---|---|
| 132 | |
| 90 | |
| 78 | |
| 66 | |
| 65 |