Comments
-
Hi there, Hmm it didn't work. I'm not sure what would be helpful for you to see. Here's a snap shot of the top of the card, and the beast mode that's calculating the second column as a sum for the total YTD terms.
-
Hi Rahul, Right now the YTD terms are being figured by using this beast mode in the data set: Case when YEAR(`dateOfTermination`)= YEAR(CURRENT_DATE()) then 1 Else 0 End What would be the best way to input that into the formula you gave me? Thank you! Becki
-
Sure thing, thanks for all your help. So this is just an Excel with the raw data from two of our 500 locations. The first tab has Palatine has a total of 19 lines, so 19 employees over all of time. However when we set the date range for 2018, it will be ytd or for this purpose, we can just say Jan. 1 2018 to March 1…
-
Miles would be ideal, we keep zip codes of our employee's address and our shop locations and I'd like to map out where techs we retain live compared to techs that don't make it to the 90 day mark live in comparison to their home shop. We keep full addresses of both home and shops but I figured that may be asking for too…
-
Okay, this worked. Initially... However, I think that some of the data is really skewed because it's using a current count of employees or those marked as active instead of doing a historical snapshot of the average number of employees between the date range that I am wanting to view. So we are looking at 1/1-3/1 of 2018,…
-
Hi Scott, Thanks for the help! We have a field in the current data set that returns either active or inactive called status. Every employee only has one line and they are either active or inactive. If someone transfers it doesn't count against the turnover rate. Ideally, we'd track both at the location level and all the…
-
Did a new thread for this get opened? I am curious to see how to add the targets in the dataflow. Thanks! Becki
