We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
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.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 57 | |
| 38 | |
| 33 | |
| 19 | |
| 16 |
| User | Count |
|---|---|
| 67 | |
| 66 | |
| 40 | |
| 34 | |
| 25 |