One of the limitations of the use of Power BI field parameters is that they can't be used in a live connection model.
I request this feature to be enabled since field parameters are hyper useful for many of our use cases.
12 Comments
- nazeerul_hazardNew Member
Allow creating field parameters in live connection data sources
- Bartosz_GestwaNew Member
Exactly. Local measures are a thing in 'Thin reports' and it's super useful. Local field parameters without creating a dataset would be a huge deal for 'Golden dataset' environments.
- fbcideas_migusrNew Member
The field parameter is really useful for views to dynamically select the columns or measures in the table. Similar workarounds for parameter like unpivot tables or create DAX data table aren't supported in live connection as well. Please consider adding that feature which would really help a lot.
- fbcideas_migusrNew Member
Important to note that the field parameters created in a dataset are not usable in a live connected report. So if I add one, the option to show field values is not there...this is really needed. Hope this gets added soon!!!
- fbcideas_migusrNew Member
Hello Microsoft Team,
As a Fabric user, we've recently started leveraging Fabric's warehouses and lake houses, utilizing the default semantic model with live connections in Power BI. Currently, when using a live connection in Power BI Desktop, attempting to add field parameters prompts a switch to mixed mode, effectively duplicating the semantic model. While workarounds like Tabular Editor and SQL scripting exist, they aren't officially endorsed by Microsoft, and licensed versions may not be accessible to all.
I would like to request the Microsoft team to implement field parameter creation directly in the default semantic model interface within the Power BI service. This would streamline the process, allowing the addition of field parameters without altering the source or switching to a mixed model, ultimately saving time and avoiding semantic model duplication. This enhancement would empower developers to offer customizable viewing experiences without the need for complex workarounds.
Thank you.
Regards,
Uma M
- fbcideas_migusrNew MemberStatus added:New
- fbcideas_migusrNew MemberStatus added:New
- rubenflores
Microsoft Employee
This is a big limitation and makes maintenance of Live Connections really hard. - jeroenterheerdt
Microsoft Employee
Status changed:NewtoNeed ClarificationYou can use a DQ connection instead.
- GethBBFrequent Visitor
That's a major change from a governance perspective. Generally we dissuade the creation of local models/DQ pointing at live semantic models as it creates lots of other headaches. As noted above, report only measures are a great addition to the thin report structure but then introduces this need to be able to have parameters for those measures. Could there not be a similar report-only structure for parameters?
Recent ideas
Auto-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...majofv1 hour agoNew MemberNew5Views1like0CommentsAdd a Close or “Return to previous page” button to Semantic Model Security and Settings pages
When updating RLS group assignments through Semantic model > Security, there is no consistent in-product Close or Done button that returns the user to the previous workspace view. The browser Back b...Kalaiselvan4 hours agoFrequent VisitorNew2Views0likes0Comments