When applying Object-Level Security (OLS) in Power BI using columnPermission = none, the protected column is completely unavailable to the user. As a result, if that column is used in an existing visual, the visual may break or display an error.
It would be useful to have an additional column-level permission that masks or suppresses the column values without removing the column itself from the semantic model.
This way if the column (or measure) is available in a visual it would not break but simply it's value will not be visible for roles who do not have permissions on the column. This way there is no need to make separate visuals (or separate report) for every role. Any measure built using such column (or measure) should carry this permission rendering the resultant measure as masked.
This would be similar to the OMIT functionality available in Qlik, where sensitive values can be hidden without negatively affecting the overall user experience.
