Use Dependant Field

[Community Alums]

Hi guys, 

I have 180 Business Services each using the same ootb Cause code choice list of around 12 choices. 

A new Service is inbound but has a requirement for its own unique Cause Codes. 

I thought this would be a simple case of create the new choices utilising the 'Use dependant field' option in the Dictionary, and add the New Service name to the new choices. 

This is working for the new service but any other service has a blank choice list. 

Surely there is a simpler way to show the ootb choices for all other services other than creating a choice for each service which would mean managing a choice list of over 2000 choices? is there not some script I can add in the Dependant value field for all other services other than the new one? 

Thanks all. 

[bammar]

OK the first way your thinking would require you to literally fill in the choices 180 times in the dependency setup in additon to the new one , and every time you add a new business service.

Alternatively i guess you could add the new options to the existing menu but dont use dependency- instead write a client script to only show the ones you want, the reverse of that may be needed for the other 180..

If it looks like in the future youll get a totally new set up options that are tied to another group of Business Services, maybe make a new field for these and hide the original choice list for those and vice versa...

[Jim Coyne]

One way to do it, without client-side code, which is usually the better idea, is to add another field and use it as the dependant field.  Like the Incident Category/Subcategory combination.

That would mean you would have just 2 sets of choices: one for your existing Business Services and another for the new one.  And the ability to add new choices for any new Service that may come along.

[Community Alums]

So in the end I switched the dependant value from the Business Service to the Company reducing the overhead from 2000 to 200, imported the new choices from Excel. 

This means im still using OOTB functionality rather than scripting or creating a client script. 

[Jim Coyne]

Always good to avoid code where possible.  Usually easier to maintain and avoids possible issues.