raym85
1 year agoAdvocate I
Status:
New
Dynamic Lakehouse Attachment When Merging Feature Branch to Main
As a Microsoft Fabric user, I’ve noticed an issue when merging code from a feature branch to the main branch. My notebook retains the lakehouse that was attached in my local development environment, even after publishing to main. This creates extra manual steps to reattach the correct lakehouse, which can be error-prone and disrupt workflows.
It would be great to have a way to dynamically update the lakehouse attachment when merging from a feature branch to main. This isn’t about deployment pipelines for different environments but rather about ensuring that the correct lakehouse is automatically linked when the code is merged.
This feature would help streamline collaboration and prevent issues
No CommentsBe the first to comment
Recent ideas
Accessibility 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...abigb18 seconds agoNew MemberNew0Views0likes0CommentsF5 for presentation mode in POWER BI DESKTOP
F5 for presentation mode in POWER BI DESKTOP. In design time when we press F5 . 1) The canvas goes to fit to screen mode. 2) Visual headers will be hidden for visual components which set to hidden in...ndaneshi2 hours agoNew MemberNeeds Votes104Views3likes2CommentsExpose Card Visual Reference Values to DAX via SELECTEDREFERENCEVALUE() or similar
Description The new Card visual introduces Reference Values and Reference Labels, which are excellent for displaying targets, benchmarks, prior periods, and other contextual metrics alongside a KPI....SEMattis3 hours agoAdvocate IIINew2Views0likes0Comments