You’re offline. This is a read only version of the page.
Announcements
107
Has anyone successfully set up column permission profiles in Portals? Based on the documentation it sounds pretty straight forward, but I cant get it working.
The documentation states:
"When permissions are evaluated, table permissions are evaluated first. If a user has access to a table, the table's column permissions will be applied. If the user doesn't have access to the table, any configured column permissions will be ignored."
But it seems that the table permissions are granted for all columns, even when a column permission profile is added to the web role.
I have tried the following:
| Table Permission | Column Security | Result |
| Enabled, no privileges checked | "Read" enabled for all columns, "Update" and "Create" for some columns | No records visible |
| Enabled, only "read" privilege checked | Same as above | All records visible. All columns read only when trying to edit. |
| Enabled, all privileges checked | Same as above | All records visible and editable |
| Disabled | Same as above | No records visible |
No matter what I try, the table permissions are applied to every column, and the column permissions are ignored.
Are you working with the usual Portal form configuration, or have customised code using the Web API?
FYI: Column permissions are currently only applicable to the Web API (and your portal needs to be up to a version that supports them - this info is on the page you linked).
Share
Report
All responses (
Answers (
