When saving a dataflow in Power BI service, it runs through 3 checking steps for each loaded query. The results are always either green and the save operation completes, or red and it fails. The problem is that one of those checks has the potential to clean up your queries, adding column type changes or outright deleting columns. When this happens, the result is still a green check with no indication of a change. Unexpected behavior may result and it may not be easy to even find where the change took place on larger dataflows.
I would like a yellow-check warning that something happened and to choose to allow it or go back to the editor, similar to how Excel will sometimes suggest a closing parentheses on an incorrectly typed formula.
1 Comment
- fbcideas_migusrNew MemberStatus added:New
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...EversonElias4 hours agoRegular VisitorNew6Views1like0CommentsEnable 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-tsindhu5 hours agoMicrosoft EmployeeNew7Views0likes0CommentsAccessibility bug: Notebook cell text becomes invisible under Windows 11 High Contrast mode
Any text written inside a Fabric notebook is invisible when Wndows High contrast mode is enables. This applies to cell text only (not the UI). In addition, auto-complete windows are not respecting t...abigb7 hours agoNew MemberNew3Views0likes0Comments