Weekly Challenges

Solve the challenge, share your solution and summit the ranks of our Community!

Also available in | Français | Português | Español | 日本語
IDEAS WANTED

Want to get involved? We're always looking for ideas and content for Weekly Challenges.

SUBMIT YOUR IDEA

Challenge #417: Evaluation of Employee Working Hours

braveraj
11 - Bolide
Spoiler
Shift workflow.pngShift Results.png
Deleshae
5 - Atom

My shot at it.

Spoiler
image.png
Spoiler
 
ed_hayter
12 - Quasar
Spoiler
image.png
erike601
7 - Meteor
Spoiler
alteryxchallenge417.jpg
robbinrv
8 - Asteroid

Thanks for the challenge @DataNath, worked up an appetite.

 

Spoiler
image.png
bodee8
8 - Asteroid

Solution

mmontgomery
11 - Bolide

C417

Spoiler
c417.png
AGilbert
11 - Bolide
Spoiler
To handle csv format, parsed header and data separately and rejoined using field info and dynamic rename to create dataset.
Included a Boolean test on > 4-hour shifts and aggregated by count of results into the view. 
The dataset does not include days the store is not open (no employee was paid). To count these days in non-working days, find employee's first shift date (assumes the employee's first shift is first date of employment) and join to view.
Datetime delta of start date to EOM less total shifts taken is non-working days. 

Straightforward with assumptions. 
Spoiler
Screenshot 2024-03-11 164132.png
gawa
15 - Aurora
15 - Aurora

In my case, [Percentage below 4 hours] = 0 in last 3 months 😭

Spoiler
As @AkimasaKajitani said, total days should be 90 days,  not so in output file though.
image.png
Qiu
21 - Polaris
21 - Polaris

@DataNath  Congratulations!

Surprisingly there are a few catch in this "Simple" flow 😁

Spoiler
  • Exceed 4 meaning larger than 4 and below 4 means smaller or equal to 4 (maybe just me)
  • Each Employee ID Start date might be different.
  • End date is 2023-03-31
Spoiler
challenge_417.PNG