Choice list with multiple dependent values?

[Jake Berkes]

This has had me stumped for a while and I'm hoping someone can help.

I have a Symptoms dropdown list that I'm trying to make dependent on the Incident Category. Any one symptom may need to appear in the list for several categories, which is where I'm running into problems.

Example:

Category	Symptom
Cat1	Sym1 Sym3 Sym5
Cat2	Sym1 Sym2 Sym3
Cat3	Sym2 Sym3 Sym4
Cat4	Sym2 Sym4 Sym5

The symptoms list is about 30 items long, with several symptoms needing to appear based on each category. Using a standard dependent value requires multiple instances of each symptom in the choice list, which is tedious and gets out of hand quickly (around 200 items in choice list).

Is there a better way to do this? It almost seems like I need to reverse the dependency, but I'm not sure how to go about it - Sym1 = Cat1, Cat2; Sym2 = Cat2, Cat3, Cat4, etc.

Hope this makes sense, please let me know if I can clarify at all. Thanks!

[jkishore]

Hi

I wish for the above problem this following link will be helpful:

ServiceNow Choice List Dependencies - JDS Australia

Thanks,

Kishore

[pabitras]

Hi Jake,

Just wondering, did you figure out in defining your choices multi dependency value.

Can anyone please tell me that can we configure one choice field which can have more than one dependent value in it, like 750 will have 700,600 choice values?

Please suggest, I am little new to snow world now..

Thanks,

Pabitra

[lexifouts]

Hi Pabitra,

I'm sure you've figured out a solution/workaround to your specific problem by now, but I just came across this post while attempting to do the same thing.

It turns out you can simply add multiple sys_choice entries for each dependent value they should be shown for. For example, I have one choice option "Option 1" that should be able to be selected if the dependent field's value is either "Value1," "Value2," or "Value3."

I can create three sys_choice entries, each with the label/value of "Option 1", but each can have a separate dependent value specified ("Value1", "Value2", "Value3"). This produces the desired behaviour, and since the values of the choices are all the same (and choices are really boiled down to strings anyway)--the system treats them as the same option in terms of reporting or grouping by the field in list view.

Hope that helps someone if they come looking with the same problem!

-Lexi

[Greg42]

So far this is the best way I found of using the multiple dependencies with no overhead of scripting.

So if anyone else is looking for this solution, follow Lexi's example.

Regards

Greg

[michaelcory]

Thank you very much for the post and information Lexi, very helpful!  Saved me a ton of research time trying to figure out a way to do this.