Forum Discussion

sled1419's avatar
sled1419
Regular Visitor
1 year ago
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. ...
Need Help
  • Deku's avatar
    Deku
    1 year ago

    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.

Deku's avatar
Deku
Icon for Super User rankSuper User
1 year ago

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.