Problem with field parameter and empty slicer

PBI_VL 

Workaround:

Add a separate "None" option to the parameter.

Use a blank measure or blank column for that option.

Set that as the default state.

Hi PBI_VL 

It is unusual to have repeated values in the "Fields" column of a field parameter table with different display names in the first column.

With a default field parameter table setup, this causes odd behaviour when using a slicer on the first column of the field parameter table (due to the Group by Columns property that is automatically set).

 

What is the reason for repeated values of 'Coverages'[COVER_AGE_CATEGORY]?

What behaviour do you expect for each type of selection made on the slicer?

Hi PBI_VL 

This is caused by the Field Parameter behavior rather than by the blank value in the Cover slicer. Microsoft states that when no field is selected in a Field Parameter slicer or filter, Power BI treats it as if all fields are selected. That explains why, after selecting a Cover and then clearing the slicer, the visual ends up showing categories from both AGE_CATEGORY and COVER_AGE_CATEGORY.

I would not try to solve this by adding a blank value to the Field Parameter table, because the parameter itself cannot interpret “no Cover selected” as “use Age only”.

If the required logic is strictly:

no Cover selected → group by AGE_CATEGORY
one Cover selected → group by COVER_AGE_CATEGORY

then a more robust design may be to avoid using a Field Parameter for this axis and instead use a disconnected category table together with a dynamic ClientCount measure that switches its calculation based on whether a Cover is selected.
This approach requires a different setup, but it gives full control over the fallback behavior instead of relying on the Field Parameter’s “no selection = all fields” behavior

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly

Hi PBI_VL , Thank you for reaching out to the Microsoft Community Forum.

 

The issue is coming from the way the field parameter is modelled. You are repeating the same field (COVER_AGE_CATEGORY) multiple times in the parameter and then filtering that parameter through DimCover. After you select a Cover and then clear the slicer, Power BI no longer resolves the parameter to a single row, so it behaves like multiple parameter rows are active and shows both AGE_CATEGORY and COVER_AGE_CATEGORY on the axis. That is why the visual works correctly on first load, but not after clearing the slicer.

 

I would not try to solve this with a “None” or default parameter option, because that is only a workaround. Stop using the field parameter for this logic and instead use a disconnected axis table with a measure that switches between AGE_CATEGORY and COVER_AGE_CATEGORY depending on whether a Cover is selected. That gives you stable behaviour where no Cover selected shows AGE_CATEGORY and selecting a Cover shows COVER_AGE_CATEGORY.