Support for Parameter Dropdowns in Deployment Pipelines
InPower BI Desktop, you can define parameters with a list of allowed values, allowing users to select from a dropdown instead of typing a value manually.
In Deployment Pipelines, these parameters currently appear as free-text fields, even if a list of allowed values is set. This can lead to errors when entering server names, database connections, or other environment-specific values.
Proposal:
Enable Deployment Pipelines to display allowed values as a dropdown, just like in Desktop.
This would improve reliability, reduce typing errors, and make it easier to configure Dev/Test/Prod environments consistently.
Benefits:
Fewer human errors during pipeline deployment
Consistent environment configuration
Improved usability and clarity
Vote for this idea if you find it useful!
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 ...PeterDaniels36 minutes agoAdvocate IIINew176Views0likes2CommentsMake 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...ewarstdhyjugkhi2 hours 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