Quick Follow up to this. This applies to both Fact...
# gooddata-cloud
d
Quick Follow up to this. This applies to both Fact and Dimension tables Lets say we have a Dimension table called feature id Name 1 Feature A 2 Feature B 3 Feature C Workspace A uses only 1 and 2, Workspace B uses just 2 and 3 We added the Feature as a Drop down on each workspace dashboard If we wanted the drop down to only show the ID's they use. Instead of a dimension table like the one above we would need. WDF filter on BOTH Fact and Dimension and Dimension would look like this id. WDF_filter. Feature Name 1 Workspace A Feature 1 2. Workspace A. Feature 2 3. Workspace B. Feature 2 4. Workspace B. Feature 3 Is that correct, or is there a better set up
m
Hi Doug, if this is more about a convenience than a security (i.e. it is not that important that user in workspace A never ever sees the value of "Feature C" but you just want to not show it in dashboard dropdown, you can use IMO a simpler setup: • do not use WDF for this dimension • for each Feature dropdown use the Filter by Metric feature to pre-filter the dropdown to only values existing in some fact dataset (i.e. use SUM of some fact from the fact table) Users with ability to create visualizations and dashboards will still be able to create one that will show "Feature C" (i.e. in visualization or filter using juat the feature attribute. But in yoir dashboard they will only see the valid values. Depending on the complexity of the filtering metric and data volume, it might take longer to display the filtered filter values.