I have a dashboard with two views. A slice view where a single column is referenced in the sheet table with a ValidIf expression that references the unique values in a column of that sheet table. That column should be used to filter data in the second table view below. However, when anything is selected in the first view, it just shows yellow triangles and red writing below that says โThis Entry Is Invalidโ. (Which is impossible because its pulling unique values from the same table used in the second view.) And also that able below remains unfiltered. Please help.
This means that the specific data inside that column does not match what is expected;
Thanks for that! Couple things though,
Why make it the key? As I understood the Key, the ref column in the child table does not have completely unique values.
When I mark it as the Key, the field disappears in the view. Which creates another hole in my understanding lol
But Im excited to untangle this. Thanks for your help!
It is critical you fully understand the following:
Steve, thanks again for responding! However, I fear we may not be on the same page. I feel Im pretty aware of what a Key is at this point. I donโt think I can make this column the Key without causing other problems down the line because the entries are not unique. Maybe some greater context would be helpful:
The Parent sheet data I am filtering is called EVENTS and the column is โDepartmentโ- so (Sales, Marketing, Support, IT, etc) and as you might imagine, multiple people can be part of the same dept (haha) so I canโt make this the Key as all the values are not unique.
I will likely have dozens of users customizing their views at the same time. So I decided to add a โDepartmentโ column on my USERS sheet. So when people filter and view the data from the EVENTS sheet, the documentation code (the โ1โ that appears in the sheet as a result of the filter) only affects a userโs row on the Users sheet (instead of overwriting anything on the EVENTS sheet).
Lastly, the โDepartmentโ column on the Users sheet wont have completely unique values either. So I cant make it the Key at the child level either.
Maybe this helps, maybe it doesnt. This is all putting my brain in overdrive tbh lol
An extremely wise move; otherwise youโd have all sorts of cross-talk andโฆ man things get weird for the users quick.
This post might be of help:
This would give you your user record in the slice, then you can easily pull that and use it in your Dashboard Slices.
INDEX(Current_User[User_View_Dept], 1) = [DeptID]
User | Count |
---|---|
15 | |
11 | |
11 | |
8 | |
3 |