raym85
Advocate I
1 year agoStatus:
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
- fbcideas_migusr53 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,...Manickambeeie3 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..._taab5 hours agoNew MemberNew5Views0likes0Comments