Forum Discussion
ReportEmbed URL filters not working for Field Parameters
Hi,
I am trying to pass filters for field parameters Dimension and Metrics but filters are not applied properly
App.powerbi URL -> &filter=Dimension/Dimension%20in%20('subcat_name'%2C'pmcat_name')%20and%20Metrics/Metric%20in%20('Engagement'%2C'CTR'%2C'Conversion') ---- This is working fine
ReportEmbed URL ->
&filter=Dimension/Dimension%20in%20('subcat_name'%2C'pmcat_name')%20and%20Metrics/Metric%20in%20('Engagement'%2C'CTR'%2C'Conversion') --- Metrics Filters are applied and for dimension only last value filter is applied(in this case only pmcat_name)
I have also tried encoding also but results are same.
Hi Ashish29,
Why does it work in the Power BI App but not in Embed?
- Field Parameters are implemented as calculated tables with DAX behind the scenes.
- When you pass multiple values in the filter via URL, Power BI Service (App) interprets them correctly because it uses the full report context.
- In Embed scenarios, the filter syntax is applied at the dataset level, and Field Parameters do not behave like normal columns—they are dynamic selections. As a result:
- For one parameter (Metrics), the filter works because the engine resolves the mapping.
- For the other (Dimension), only the last value is applied because the parameter table does not support multi-select via URL in embedded mode.
Is this expected?
Yes. Currently, URL filters do not fully support multi-select for Field Parameters in embedded reports. This is by design because Field Parameters are not standard fields—they dynamically swap columns in visuals.Workarounds
- Use a slicer in the report for Field Parameters
Instead of relying on URL filters, expose slicers for Dimension and Metrics. This ensures proper multi-selection. - Switch to standard columns for filtering via URL
If you need URL-based filtering, consider using actual columns (not Field Parameters) for Dimension and Metrics filters.
Official References:If this response was helpful in any way, I’d gladly accept a 👍much like the joy of seeing a DAX measure work first time without needing another FILTER.
Please mark it as the correct solution. It helps other community members find their way faster (and saves them from another endless loop 🌀.
4 Replies
Hii Ashish29
ReportEmbed URL filters do not fully support Field Parameters. Field Parameters are resolved at runtime, and when multiple values are passed through the embed URL, Power BI applies only the last value for the parameter. This works in the Power BI Service URL but is not reliably supported in embedded reports. The recommended approach is to handle Field Parameter selection inside the report (using slicers or bookmarks) or use standard columns instead of Field Parameters for URL-based filtering.
Hi Ashish29,
Why does it work in the Power BI App but not in Embed?
- Field Parameters are implemented as calculated tables with DAX behind the scenes.
- When you pass multiple values in the filter via URL, Power BI Service (App) interprets them correctly because it uses the full report context.
- In Embed scenarios, the filter syntax is applied at the dataset level, and Field Parameters do not behave like normal columns—they are dynamic selections. As a result:
- For one parameter (Metrics), the filter works because the engine resolves the mapping.
- For the other (Dimension), only the last value is applied because the parameter table does not support multi-select via URL in embedded mode.
Is this expected?
Yes. Currently, URL filters do not fully support multi-select for Field Parameters in embedded reports. This is by design because Field Parameters are not standard fields—they dynamically swap columns in visuals.Workarounds
- Use a slicer in the report for Field Parameters
Instead of relying on URL filters, expose slicers for Dimension and Metrics. This ensures proper multi-selection. - Switch to standard columns for filtering via URL
If you need URL-based filtering, consider using actual columns (not Field Parameters) for Dimension and Metrics filters.
Official References:If this response was helpful in any way, I’d gladly accept a 👍much like the joy of seeing a DAX measure work first time without needing another FILTER.
Please mark it as the correct solution. It helps other community members find their way faster (and saves them from another endless loop 🌀.
Hi Ashish29
Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to rohit1991 and Zanqueta for sharing valuable insights.
Could you please confirm if your query has been resolved by the provided solution?If you have any more questions, please let us know and we’ll be happy to help.
Regards,
Microsoft Fabric Community Support Team
Hi Ashish29
We have not received a response from you regarding the query and were following up to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank You.
