Forum Discussion
CALCULATETABLE slicing alternative
What was the rationale for dividing your data up into separate tables? Were you ever considering leaving everything in one table and have the status just be a column in that table?
lbendlin, yes, this is how I orginially wanted to do things. In order for me to filter down to the 3 states of "Open Positions", "Positions In Progress" and "Positions Filled", I couldn't figure out a way to return multiple rows from a table that I could show in a table. I would try to write a measure and get the expecting a scalar result error message. Essentially this dashboard is answering 3 questions:
1. How many open positions do we have now?
2. How many positions have we identified candidates and start dates but the start date is in the future?
3. How many positions have we filled (completed)?
I have this high level information in 3 cards with a blank button on top that when clicked goes to a bookmark showing the table with the correct information detail. In this table, if it shows open positions, it will show the open positions with fields from the calculated table like when the job post was opened, the job title, the project for the job post, etc. Everything works to this point. Now when I want to add filters that the user can set like which project? or for what date range?, the filters do not work on these calculated tables. Th