Hi Martin, my apologies for the delayed response.
This is Son from the Product Team of Holistics, thanks for sharing your thoughts on this. We understand that there are better solutions than masking the value.
Would you mind sharing more about your use case(s), i.e. Apart from the number dimensions and measures case, is there any reason you would prefer hiding fields to just masking the value?
Besides, the use case you are referring to can be resolved when we roll out what we call the Dynamic model in the next year. This feature allows analysts to define dataset/report that can take user inputs or attributes. Let’s see how it works for your case:
For example, if we only want users with a manager role to see the revenue, at first we will define a is_manager param in the model definition and use it to set the condition for the hidden field property.
Model Order (is_manager: boolean) {
measure revenue {
type: 'number'
hidden: '${is_manager}'
}
}
Then in the dataset exploration, we set the viewing permission with the is_manager param and user Attribute pii_access:
As a result, when a manager (with pii_access = true) views a dashboard, s/he will see the full data. When a non-manager views, s/he won’t see the column revenue.
Please be kindly noted that this feature is still in the research phase so the final solution might be different. We are gathering feedback to make sure what we build covers all users’ needs.
Should you have any questions about the feature, please let me know.
Thanks!