YevgenyM
Advocate IV
5 months agoStatus:
New
Make experience=fabric-developer the default and persistent user experience
When working in the Fabric Developer experience (experience=fabric-developer), navigation should consistently preserve this experience across all pages and links.
Today, many internal links redirect users back to experience=power-bi, which breaks context and requires manual switching back to the Fabric Developer experience. This is especially noticeable in Monitor, but also occurs in other areas.
Requested behavior:
- Automatically retain the active experience when navigating within Fabric, or
- Provide a user-level preference to set a default experience (e.g., always open links in Fabric Developer).
Persisting the selected experience would significantly reduce friction, avoid repetitive context switching, and improve overall developer productivity.
No CommentsBe the first to comment
Recent ideas
- fbcideas_migusr36 minutes agoNew MemberUnder Review378Views12likes4Comments
Display Table[Column] instead of Column Name in Conditional Formatting Dialogs
In large-scale Power BI semantic models, it is common to have identical column names across multiple fact and dimension tables. Examples include columns such as Status, Category, Region, Employee ID,...Manickambeeie2 hours agoNew MemberNew3Views0likes0CommentsNative SAP SuccessFactors and Active Directory Connectivity for Simplified Data Integration
Having native connectors for SAP SuccessFactors and Active Directory would eliminate the need for workarounds such as notebooks, custom scripts, or complex integration setups. Users should be able...João_Cristo3 hours agoNew MemberNew3Views0likes0CommentsAllow Azure Databricks streaming tables to be mirrored into Fabric
Mirroring an Azure Databricks Unity Catalog into Fabric silently drops streaming tables. They are not greyed out, not flagged, not explained. They simply do not appear in the picker, so there is no w..._taab4 hours agoNew MemberNew5Views0likes0Comments