Forum Discussion
Solved
Slicer Not Working Across one USERELATIONSHIP field, is Working Across Another
I have essentially 3 data sets that matter for this scenario - Open Orders, Shipped Orders, and Forecast. Each of these tables has a column with the $ value, the sales rep name, and the month name. ...
You can turn this into a star schema and make things more simple, predictable and performant.
I would suggest turning the month name in a date, start or end of month.
Create a date dimension, as a role playing dimension.
Setup relationships from date table to each of your facts and use USERELATIONSHIP to activate then.
Then you don't have to worry about other filters from the tables giving unexpected results.
Additionally I would include a common dimensions for sales rep.
v-ssriganesh
Community Support
Community SupportHi sled1419,
May I ask if you have resolved this issue? If so, please mark it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.