When creating column-level security on a table, these columns are no longer usable for users in the group with this limitation.
However, when running a SELECT * statement, the error reveals the ' hidden' columns.
The default SELECT TOP 100 rows error occurs for the same reason.
When you click on the table, it shows an error, but no really understandable message.
I would suggest a code change that detects the column-level security and automatically applies it to the user, preventing this user from ever gaining any knowledge of the hidden columns.
frithjof_v
on:
Job scheduler API: List failed runs
SriV
on:
Connecting to AML Workspace from Fabric Notebook u...