- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2016 11:23 AM
I have a table that that stores basic employee information (1) and another table (2) that has a reference field referencing the basic employee info table. Through that reference field, I've also dot walked and picked up some additional fields from the basic employee info table. I want to make some of these fields in table 2 read-only, but not read-only in the base table 1 (basic employee info). Is there a way to do that?
I tried following the logic in this post: https://community.servicenow.com/thread/173149#734008, but couldn't find how to get to Dictionary Override as the instruction indicates.
Thanks!
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2016 12:19 PM
I see what you are saying. You want to dot-walk to place them on the form. Correct. You would have to make them read-only on the original field.
In that case, the UI policy (or client) script is going to be your best solution unless you make new fields on table2 and copy the values from table1 instead of dot-walking. This is similar to how the OOB functionality works on the incident form when you see the caller's location. It takes a bit more scripting to copy over the values.
Thank you for your clarification.
FWIW, best practice suggests limiting the number of dot-walked fields from a reference table as it can be confusing to the user where the information actually resides. Using the hover-over icon is a better way to view information on a referenced record.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2016 01:02 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2017 09:49 AM
Hi Guys,
By using either Ui Policy or Client script, the dot walked field becomes readonly on the form for an existing record, how about making the same read only when clicked on New?
Thanks
Tanay Bedia
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2017 10:14 AM
I was mistaken, the fields were mandatory hence the hassle, once made non-mandatory then read only works perfectly.