Often when I am writing queries I end up having multiple queries within the same script in Fabric Warehouses/ Lakehouse SQL endpoints. This results in this nice dropdown for navigating between each of those queries but as more queries are included in the script, it gets to be a lot. Currently I leave comments in my code like "Result 1: Query Subject" but that means I need to track down which query is which still and if I reorder the queries then I need to update the query numbers. What if there was a command or a wrapper that could be a flag to name these something set by the user (or dynamically) so that it would be easier to click through results?
No CommentsBe the first to comment
Recent ideas
Allow us to rename fabric data agents published to m365
If we use deployment pipelines to promote fabric data agents between dev, test/UAT, and prod fabric workspaces, we need to keep the name of the fabric agent the same in each workspace. If we want to ...PeterDaniels5 minutes agoAdvocate IIINew172Views0likes2CommentsMake workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen1 hour agoAdvocate INew292Views47likes2CommentsSupport Encrypted Sensitivity-Labeled Excel Files in Power Query
Description Currently, Power Query Online and Power Query in Excel are unable to access encrypted Excel files. Excel files with sensitivity types other than Public or Non-Business can be encrypted a...ewarstdhyjugkhi1 hour agoMicrosoft EmployeeNew16Views6likes0CommentsAuto-propagate Lakehouse (Direct Lake) permissions to users assigned to a Power BI App audience
Problem When a Power BI report uses a Live Connection to a Direct Lake Semantic Model, end users must have explicit ReadAll / ReadData permissions on the underlying Lakehouse (or its SQL analytics e...majofv4 hours agoNew MemberNew5Views1like0Comments