Best Practice for SN Variable Options

[VasukiS]

We’re in the early stages of configuring ServiceNow Catalogs and need to store custom options for record producer variables. Since there’s no existing table for this, I’m considering creating a custom table to manage and retrieve these values. While it’s clear we need a centralized place to store these options, I’d like to know—would using the sys_choice table be appropriate, or is creating a dedicated custom table the better approach?

[Chaitanya ILCR]

HI @VasukiS ,

question_choice is the table where the choices are stored for catalog item select box and Multiple Choice options are stored

Please mark my answer as helpful/correct if it resolves your query.

Regards,
Chaitanya

[VasukiS]

@Chaitanya ILCR 

If the options are limited, we can use the same ones. However, since there are many options and they change depending on the previous question's selection, I need to retrieve the variable options based on the previous answer.

So, I need to store this information in a table and use a reference qualifier to pull data depending on the previous variable selection.

[GlideFather]

Hi @VasukiS,

all the variables are stored in a ServiceNow table - navigate by typing "All variables" and you will find it.

That is where the definitions of variables are stored, their type and relation to record producers or catalog items or variable sets.

Then you have another table where you can see what values were ever inserted upon submission.

Do not create custom table!

[Zach N]

Personally I would recommended creating a custom table. If you know this is going to be a large use case with multiple catalog variables, I think it would be easier to manage in the long run. If you start adding options to the sys_choice table you will likely encounter some ACL issues with visibility, especially if it is going to be end-user facing.