Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Enable Dot Walking for users when personalizing

smacleod
Tera Contributor

I need to grant all (or many) of my high-level users the ability to add any column they need from any related record to their list view without me having to add it to the list view for them, especially when it would only be relevant for a handful of users. We were able to do this in every previous system we used and it is baffling that ServiceNow does not allow users to add (FOR EXAMPLE): the assigned user's department field to the computer list without me having to make the field default for everyone.

Is there a setting somewhere that I am missing!?

6 REPLIES 6

GlideFather
Tera Patron

Hi @smacleod,

 

can you provide more details? is it in native UI (backend) or Workspace?

 

In general, you can add dot walking but only in the View:

GlideFather_1-1763667416236.png

 

 

Users can personalise their list view but then dotwalking is not available:

GlideFather_0-1763667274585.png

GlideFather_2-1763667503002.png

 

- it will be edited for only the logged in (or impersonated) user.

 

So the best way is to create new or update existing view(s)..

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */


I need to give them the ability to add fields that could just be relevant to their work in that moment in any version (legacy, workspace, native ui), without messing up the default view for everyone and without having to build new views every time someone needs a new set of fields.

(not trying to be snarky or rude, it just seems like a huge oversight from SN that users can't do this without some kind of admin help beyond just granting a role that gives them dot-walk rights)

@smacleod Then I'm worried there's no solution for your requirement.

 

You either need to create Views with dot-walked fields (you can add there more fields then needed) and each one user will select needed ones in the personalisation to keep the relevant ones only.

 

But adding and removing fields to a list view based on random and irregular needs is not supported :((

 

Also, it will be extra effort for Workspace, extra for list view in backend, ... there's no chance to do it in one modification for all.

 

Can you please give a business justification - what kind of fields we are talking about? You can add it on the form/list without having people doing it themselves

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */