kindly request you to elaborate on your questionâ€¦ just a point but there can be multiple combinations of the sales type in production so i consider that it cannot be a feasible approach

Hi,
I have looked at several options, but the point is that a slicer originates from a column of unique items. A and A+B are 2 different things. If you do not have too many permutations I would recommend adding them to the Simtype list. Alternative, create groups (assuming all Sim types are in the Sales- and Simtype table) .

So production there are seven sim type and the permutations would too many.

Can you give me clarity on the groups part. basically note that the sales amount mentioned is a combination of A+B and we are not aware how much does individual sim type contributes.(information till that gran is not available)

So 49 different types possible, assuming A+B and B+A are possible combinations.
Not that many, but if you create groups of them they can be reduced.
You can create groups by right clicking on the field and select group.

Alternatively, see attached file, I have added a CONTAINSSTRING calculated column to the sales data to show records with a combination, play around with this. sample _multiple column value slicer.pbix (66.0 KB)

Whilst typing I realise that you could also create a table (in Excel) with the possible permutations and a category or group and merge this with the sales data file.

Based on the pbix shared by you i see blank values against the sales amount because of the relationship created.

Agreed with the groups logic but user wants to see A+B as well as A & B individually as well. In that case how the groups going to work.

however i have modified my formula to some extent using concatenate function which filters the data based on multiple selection if that combination exists in fact table, but doesnt search the string individually.

With respect to creating a excel mapping , if at all in future additional values are added in dimension , in that case it would be a manual activity to maintain the table. Client basically trying to avoid manual maintenance.

Nice, I slightly misinterpreted your requirement. Many ways to solve a problem in PBI.
As far as the simtype table is concerned, you could also automate building the distinct types table in PowerQuery. Duplicate the Sales query, drilldown the type column, remove duplicates and it is done.When values are added to the sales data, the list would then be refreshed.