Forum Discussion
Multiple client names for the same client.
- 4 years ago
Ok, It would be possible to use the many to many relationship. You can set the filter direction to be single and then use the column 'Client Name' and it will filter like normal. You'll need to check no calculations have changed (such as a SUMX over the client table would be 3x as many now) but overall you can get the same result.
Another way would be to create one more table, just with the list of client names, each once. Then you can link this table to both the table in my other response and your clock in table and use that for the slicer.
Now when you select John Doe from this new table:
- John Doe is filtered from the clock in table
- John Doe is filtered in the name variations table (Client Name)
- The name variations table filters sales by all of the different John Doe variants (Client Name in Data).
I would create a table only with two columns, one for the Client Name and the other for the different ways it appears.
| Client Name | Client Name in Data |
| John Doe | John Doe Europe |
| John Doe | John Doe USA |
| John Doe | John Doe Asia |
| PowerBI | PowerBI Europe |
| PowerBI | PowerBI USA |
Create a relationship between Client Name in Data and the name column in your data, then you can use Client Name in any slicers or tables.
Hi,
This solution doesn't work 100%. Because I connect my sales data through a relationship with Client name in Data. Then I can use the slicer like you said and it works. But the clock in data I have uses the "client name" names. Which means that if I connect my clock in data and "client name" it will give me a many to many relationship because there is mulitple John Doe in Client name.
- AntonioM4 years agoSolution Sage
Ok, It would be possible to use the many to many relationship. You can set the filter direction to be single and then use the column 'Client Name' and it will filter like normal. You'll need to check no calculations have changed (such as a SUMX over the client table would be 3x as many now) but overall you can get the same result.
Another way would be to create one more table, just with the list of client names, each once. Then you can link this table to both the table in my other response and your clock in table and use that for the slicer.
Now when you select John Doe from this new table:
- John Doe is filtered from the clock in table
- John Doe is filtered in the name variations table (Client Name)
- The name variations table filters sales by all of the different John Doe variants (Client Name in Data).