Comments
-
@MarkSnodgrass I'm a little confused on two parts: The filter rows: I'm a little unsure what exactly we're doing in this part. I have hire dates going back 50+ years and termination dates starting about 7 years ago. Do I need to filter to include these date ranges? I'm also unsure what to do for the Use Lead to Get End…
-
@ColemenWilson I think your explanation would get us to the right solution, but there's a bit of work that will be need to be done to properly execute. The problem is that there is no data/rows for some of those criteria (year/department). So I think we'd have to manually input department data for those particular…
-
@ColemenWilson What did you mean by using a calendar dataset? More context: In these plots, I was using a COUNT of the employee id. The dataset I've been using has employee id, employee type, termination date, department, and some other info. If I create a card from a different dataset, I'm assuming the dropdown filters I…
-
@ColemenWilson I figured I might need to utilize beast mode or ETL, but was hoping there'd be a quick fix- like a box to check- before I went down that path. Yup, each line refers to a department. I have dropdown filters at the top of my dashboard, so the user can easily filter the department. Appreciate the insight :)
-
@pauljames Looks like it's working for me. Thanks!
-
@MarkSnodgrass I'll give this a try. Thank you!
-
oh, and the non-python solution is definitely appreciated. In my student license version, I'm not seeing the scripting tiles to do python :(
-
@MarkSnodgrass Thanks so much for the quick response. I think I understand what you're saying. Would I need to have a row for each vacancy spot within an organization/department to do that? Here's a couple screenshots of what I'm working with right now (I filtered out some other columns for simplicity):
