Question 580
A role is added to a field ACL but users still cannot read values because the table-level ACL denies access. Which configuration or administrative response BEST addresses the primary issue?
Explanation
Correct Answer
Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. For protected records, appropriate table-level and field-level ACL checks both matter; form visibility is not server-side authorization. Verify prerequisites with: Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context. Scenario: A role is added to a field ACL but users still cannot read values because the table-level ACL denies access.
Incorrect Answers
Define a reference field to a suitable target table and validate stored sys_id and display-value behavior, rather than treating a text label as a reliable relationship key. This approach instead addresses Reference fields and display values in the data dictionary. A ServiceNow reference is stored as a record identifier, while users commonly see the referenced record's display value. The targeted response is: Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. Scenario: A role is added to a field ACL but users still cannot read values because the table-level ACL denies access.
Model fulfillment with appropriate catalog approval stages, requested-item ownership, and downstream catalog tasks so the request lifecycle is auditable and recoverable. This approach instead addresses Catalog approval fulfillment and lifecycle. REQ, RITM and catalog task are distinct records with different scopes; notifying a manager does not imply a requested item was approved. The targeted response is: Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. Scenario: A role is added to a field ACL but users still cannot read values because the table-level ACL denies access.
Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. This approach instead addresses Scoped application permissions and cross-scope access. Application scope boundaries and user-level ACLs are separate checks; a cross-scope grant does not automatically make table data public. The targeted response is: Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. Scenario: A role is added to a field ACL but users still cannot read values because the table-level ACL denies access.


