Filter with union instead of intersection Issue

Hi DatamirHub ,

Thanks for reaching out to the Microsoft fabric community forum. 

At the moment, there is no official Microsoft documentation that describes a supported way to achieve UNION / OR behavior between slicers for table visuals.

The commonly shared approaches (including SQLBI examples) all use measure-based logic. While this works for cards and aggregated visuals, it causes performance issues for tables because the measure is evaluated row by row.

So the behavior you are seeing is expected and not related to an issue in your DAX. To avoid performance problems, the UNION logic needs to be handled at the model or data preparation level, or by redesigning the slicer approach.

If I misunderstand your needs or you still have problems on it, please feel free to let us know. 

Best Regards, 
Community Support Team