Currently, when using Copy Job to transfer Snowflake data into MS Fabric Lakehouse, we can use the variable library to parameterize the Snowflake connection but cannot parameterize the target Snowflake database. This issue arises when switching the Snowflake source system between DEV and PROD environments using the variable library, as these environments may have different database names.
Suggestion: Add this as a parameter in the Copy Job using a variable library to swap the database based on environments OR add a parameter to the Snowflake connection for the database (currently only includes the "warehouse" parameter).
No CommentsBe the first to comment
Recent ideas
Restore Shape Formatting Options in Button Slicer Visual
In the July 2025 Power BI update, the Shape formatting option was removed from the Button Slicer visual. This change has significantly impacted the ability to customize the appearance of slicers, esp...Simon_Howard7 hours agoNew MemberNew411Views0likes1CommentDisplay Delta table and column descriptions in Fabric Lakehouse Explorer/ Fabric on Browser
Microsoft Fabric Lakehouse should provide a visible and editable description field for Delta tables and columns in Lakehouse Explorer. Delta table metadata, such as comments or custom description pr...Darsh_7 hours agoNew MemberNew7Views0likes0CommentsDate picker in slicer - Monday as as start of a week and one date pick
Hello! Since March 2022 date picker week starts from Sunday and there is no way to change it to Monday. It's highly inconvinient Would be more powerful, if there also were week numbers in regional...smazaev18 hours agoNew MemberNew318Views20likes3CommentsSupport Cross-Tenant (B2B/MTO Member) Authentication for Fabric Data Warehouse in Power BI Desktop
Microsoft Fabric Data Warehouse SQL Endpoints currently do not support cross-tenant authentication scenarios when accessed from Power BI Desktop. While B2B/Multi-Tenant Organization (MTO) member u...v-nandagm12 hours agoMicrosoft EmployeeNew9Views0likes0Comments