slittle4782
1 year agoAdvocate I
Status:
Needs Votes
Provide error information within the Gen2 dataflow Power Query window
When a Gen2 dataflow fails in Fabric, the Power Query editor provides no in-context error details. You must exit the editor and open the “Recent Runs” pane to see diagnostics—interrupting your workflow. Please surface run errors (messages and logs) directly within the Power Query interface so users can troubleshoot without leaving the editor.
Diagnostic information in the "Recent Runs" window is like hanging a toilet paper roll holder in the garage instead of the bathroom. Maybe kind of nice, but it's not where I do my business.
1 Comment
- miguelCommunity AdminStatus changed:NewtoNeeds Votes
Recent ideas
Deployment Pipelines - Remember selected stage
Every time we go into a deployment pipeline, it defaults to selecting the Development stage. I believe that it would be very rare to have a user select the Development stage. It would be helpful if d...PeterDaniels4 minutes agoAdvocate IINew1View0likes0CommentsDisable auto-restore previous session's tabs in new Fabric sessions
Description: Since a recent update, starting a new Fabric session — for example by opening Fabric in a new browser tab — automatically reopens all the item tabs that were left open from a previous s...MathieuVr6 hours agoFrequent VisitorNew56Views5likes1CommentExported PDF from PowerBI to not have any indents/borders
Currently, using the "Export to PDF" option in PowerBI results in two consistently buggy results: A white border/indent is generated, increasing the size of the page from 8.5x11 to 9x11.5 Sometime...EliShalev10 hours agoNew MemberNew12Views0likes0CommentsAdding a Container for Logical Grouping of Activities in Data Pipelines
Dear Team, I would like to propose a feature enhancement for Data Pipelines in Microsoft Fabric that allows the logical grouping of activities into a container. This container would serve to: Im...lukas_karlovsky10 hours agoNew MemberPlanned876Views15likes5Comments