Support changing a dataset query from DirectQuery to import
I'm going to be blasting this same comment in all of these ideas. Idea consolidation is clearly in order. I recommend others who agree to upvote all the listed ideas.
This really needs to happen. The issue of being unable to switch from IMPORT-to-DIRECTQUERY is truly a problem. I know it's possible to switch from IMPORT-to-DIRECTQUERY. The lack of IMPORT-to-DIRECTQUERY is a productivity killer. Field renaming. Measure recreation. Calculated column recreation. Visuals coping and pasting. It's an awfully unproductive exercise.
I understand there are differences between the two storage modes and that there are some things that might break if one switches from one direction to another. That's fair. But why not just alert the developer? As it is, there's no alert or guidance to make it happen because the entire concept of switching is not possible. Stranger still, what of those situations where there are no confounding problems? Even then it's just not possible.Look at all these tickets saying the same thing as early as 2018!
Please, would someone please chart a path forward to finally allow switching from IMPORT-to-DIRECTQUERY as you've previously provided the ability to go from DIRECTQUERY-to-IMPORT?
Recent ideas
Programmatic point-of-failure recovery for Fabric pipelines
The Fabric monitoring UI already supports Rerun → rerun from failed activity. That capability is only reachable by a human clicking in the portal. Please make point-of-failure recovery available to a...EversonElias16 hours agoRegular VisitorNew15Views1like0CommentsEnable Managed Private Endpoints Support for Microsoft Fabric Capacities Below F64
Managed Private Endpoints in Microsoft Fabric are currently supported only on F64 and higher capacities. Customers using lower capacities, such as F8, cannot establish private connectivity to Azure s...v-tsindhu17 hours agoMicrosoft EmployeeNew9Views0likes0Comments