Implementing slicers to apply 'OR' criteria instead of 'AND'

[v_oneill]

I'm creating a PowerPivot (2010) for teams in my org to use that will show them their complete portfolio of investments. There are multiple ways a team can be associated with an investment (i.e. funding, managing, supporting). I would like to use slicers to allow users to specify which combination of teams and roles define the portfolio they're interested in. So there would be one slicer per investment role and the user could select records where their team was the funding team OR the managing team OR the supporting team. Obviously selecting values from multiple slicers, by default, applies these selections as 'AND' criteria. My question, is there a way to change that behavior to apply the slicer selections as OR criteria or to use selected slicer values in combination with DAX formulas to replicate OR functionality? Thanks.

 

[dhExcel]

See Turning “OR” Slicers Into “AND” Slicers « PowerPivotPro. I think that you are somewhat confused on the logic of slicers.

 

[v_oneill]

See Turning “OR” Slicers Into “AND” Slicers « PowerPivotPro. I think that you are somewhat confused on the logic of slicers.

Thanks for your response. Sorry, I'm not being clear about the situation. In my dataset, there is one record per investment and separate fields for 'Funding Team', 'Managing Team' and 'Supporting Team'. For a given investment these fields may or may not have the same value. The pivot table I've created has one record per investment for the entire organization and there are 3 separate slicers, one each for Funding Team, Managing Team and Supporting Team. I want users to be able to make selections that would filter the pivot to investments where their team is the Funding Team OR the Managing Team OR the Supporting Team. I understand that within a single slicer, selections are 'OR', but selections across multiple slicers are applied as 'AND' criteria. I considered creating a lookup of teams and team roles and having slicers on those, but the taxonomies used to populate these three fields aren't the same, so it doesn't work.