Filter parameter table on other slicer

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

A field parameter only switches columns when the parameter table is actually part of the visual’s evaluation context. Once you remove the parameter slicer, the parameter table stops being filtered, so Power BI has no way to know which parameter row should be active. That’s why every automatic attempt ends up with a blank table.

To make it work, the parameter table just needs to participate in the visual. The simplest way is to add the parameter’s Order column to the table visual and hide it, so users never see it. With that column present, you can use a small measure to decide whether row 0 or row 1 should be active based on how many Regions are selected and then apply that measure as a visual level filter. The field parameter will switch instantly and you keep its native performance.

If you’d rather not include even a hidden parameter column in the visual, then the parameter can’t be sliced indirectly. In that case the practical alternative is a measure that checks the Region selection count and returns Column1 or Column2 text for each supplier row. It doesn’t use the field parameter, but it avoids the context problem entirely and performs well even on large supplier tables.