How to create a custom choice field and then use in multiple times within a table (i.e. different field labels)?

[ty_roach]

I'd like to create a custom choice field one time, call it 'approval_options', with values:
Not Responded
Approved
Needs Discussion
Rejected

Next I'd like to create custom fields (more than one) that use these same choice values. For example, my custom fields that would use this same choice set are fields that I will call:
Customer Care
Cyber Security
Engineering
Operations
Business Office
Board

I could brute force do this, making custom choice fields for each of the above types (including all the color/style updates), but that seems like alot of work. Is there a way create a custom choice field and then use in multiple times within a table (i.e. different field labels)?

[ty_roach]

for that matter, we may come up with choice fields that would be good to use across many tables (just to expand the scope of the original question). How to do this?

[andrew_kincaid]

I would recommend creating the initial "u_approval_options" choice field on a core form like Task [task] and add the needed choices. Adding this to Task [task] won't cause it to show up on extended forms like Incident; however, it will become an available field on any extended table so just keep that in mind.

To reuse the "u_approval_options" from Task [task] on another form, simply create a new choice field, say "u_customer_care", personalize the dictionary for this new field, and set the Choice table to "Task [task]" and the Choice field to "u_approval_options". This will reuse the choices from "u_approval_options" on the Task [task] form for the new field.

Also be aware that you will have a central place to maintain these options (the Task [task] form) and that any changes to the field on Task will affect the choices available on any field using "u_approval_options" as it's Choice table/field.

Andrew Kincaid
Technical Consultant
ServiceNow

[ty_roach]

would you recommend develop a custom table that extends the task table first and then further enhance my newly created custom task table? I'm just wondering about best practices here. I as because what if numerous users start customizing the task table?

In the mean time, I'll give what you said a try and let you know how it goes. Thanks for your help.

[ty_roach]

I think I may understand now, why you suggested making this update to task and not a custom version of task.

If I create a custom version of the task table (by extending task), then I lose the ability to easily access my newly created custom choice because it is only associated with my custom task table, not the default task table, and it seems that just about everything inherits from task.

Is my understanding correct?