Forum Discussion
Kudo KingpinHelp with Shift Slicer
I probably wouldn't have a column for each shift, I'd have a single column for all shifts and then a second column to identify the shift_id
Would then just need a measure to sum and a slicer to filter down from overall total to which ever shift you wanted to show.
I would also then have a shifts lookup table which would be linked to shift_id to hold meta data about shift such as name etc. This approach would also future proof the system for when management decide to implement a third shift ;)
If you want to achieve this you can use the "unpivot" function (which is a brilliant feature for normalising datasets) to reduce multiple columns into 1.
Only in reports
Impactful IndividualI probably wouldn't have a column for each shift, I'd have a single column for all shifts and then a second column to identify the shift_id
Would then just need a measure to sum and a slicer to filter down from overall total to which ever shift you wanted to show.
I would also then have a shifts lookup table which would be linked to shift_id to hold meta data about shift such as name etc. This approach would also future proof the system for when management decide to implement a third shift ;)
If you want to achieve this you can use the "unpivot" function (which is a brilliant feature for normalising datasets) to reduce multiple columns into 1.
