"Configure Choices" option not available on field

[j_jeffcoat]

I have a field (root cause code) on the problem table that was initially set up as type String but had a choice list associated to it.   I have added a new field to the problem table set up as type Choice that the root cause code field will be dependent on.   I have also set up the choice list on the new field.

I changed the root cause code field to be of type choice, and have now flagged it as a dependent field linked to the new field I have created.   Now, when I try to configure the choices on the root cause field, the option for "Configure Choices" when right-clicking on the field label is grayed out.   When I click on the field, all choice options are listed regardless of what value is selected in the new field.   When I set the root cause field to not be f dependent field, the "Configure Choices" option is available to me.

I have tried adding the dependent value to the choices in the root cause code field manually, but that did not work.   This behavior seems to be the same regardless of if the dependent value was manually set or not on the root cause code field.

I have looked at my incident form where we have category/subcategory linked together and I do not have this same behavior, unless the category is set to the --None-- option (once I select a value in Category, I can get the Configure Choices options on the subcategory).   I thought the --None-- thing may be causing this issue on the problem form, but unfortunately it's not.

We are on the latest patch level of Helsinki.

Any thoughts on what may be going on?   I'm hoping not to have to solve this problem through scripting as we do not have scripts driving the similar relationship on Incident.

[j_jeffcoat]

I have tried that as well.   And in fact, when I manually add the dependent value, then the option is not even displayed in the drop down list.   It's almost as if it's having the opposite effect of what should be happening.

I've made sure there are no attributes on either of the fields, and nothing looks out of the ordinary, so I'm completely stumped.

[j_jeffcoat · Accepted solution]

Found the problem...

The field I was depending on had somehow been added to the form twice.   So the system didn't know which instance of the field to use.   I removed the field from the form where it shouldn't have been, and now it's working.

Lesson Learned: Make sure when adding fields to forms, they do not inadvertently get added to multiple areas of the form.

[kiranhegde]

Hi Joe,

Great....Good to hear that you found the issue.  

Regards,

Kiran

Did I help? Please like, tag helpful or mark it as the correct answer. Thanks!