List edit dot walked fields

rlehmann
Kilo Sage

Looking for a way to allow some users to be able to list edit dot walked fields.

Example:
I have added a new field to the RITM form and created an ACL to be able to list edit the field.
That same field has been added to one of the list views for Catalog Tasks.
I'd like to be able to allow some users to list edit the field from the Catalog Tasks list view.
Because I've created the list view ACL for the field on RITM, they have no issues list editing the field on the list view of RITMs, but cannot do it via the dot walked field from the Catalog Tasks list view.

Is this possible?

Thanks for any assistance.
Cheers
Ron

1 ACCEPTED SOLUTION

rlehmann
Kilo Sage

After working with ServiceNow Support via HI, the solution for this is to remove the read-only option for the Request Item field on the catalog task form itself.

They referenced the following community article to explain why:
ServiceNow Community - Read-only reference field makes dot-walked fields read-only as well?

By removing the read-only option and controlling access to the field via UI Policy, this then allowed the ability to create the list edit ACLs required for each field on the RITM.

Using a UI Policy isn't the ideal way to handle it, but it meets our requirements to allow list editing dot walked fields.

View solution in original post

12 REPLIES 12

I could not get this working, so I opened a support ticket on HI and they have confirmed that although it should be working, it in fact is not working as expected.
The last update I received indicated that they are still investigating.

I will definitely post an update, once I have something to share.

rlehmann
Kilo Sage

Unfortunately still getting the same message, even after clearing cache and trying different ITIL users.

Also tried as Admin and received the same security message.

rlehmann
Kilo Sage

After working with ServiceNow Support via HI, the solution for this is to remove the read-only option for the Request Item field on the catalog task form itself.

They referenced the following community article to explain why:
ServiceNow Community - Read-only reference field makes dot-walked fields read-only as well?

By removing the read-only option and controlling access to the field via UI Policy, this then allowed the ability to create the list edit ACLs required for each field on the RITM.

Using a UI Policy isn't the ideal way to handle it, but it meets our requirements to allow list editing dot walked fields.