Cascading custom fields

English Forum Product Feedback
1

Hi All :slight_smile:

Within my organisation, we’re using custom fields to show project categories and individual product groups.

There are probably around 8 categories, but when we drill down to individual product groups, there are hundreds. I’ve had some internal feedback that the user selects their category, and then has to scroll through every categories’ IPGs to find theirs (via a form, so they are not able to type to search)

For example:

  • Category (parent field)

    • Category A - 60 IPGs
    • Category B - 40 IPGs
    • Category C - 70 IPGs

  • IPG (Individual Product Group) (child field)

    • Product Group 1
    • Product Group 2
    • Product Group 3
    • Product Group 4
    • etc.

What we’d like is the ability to create a dependency between fields so that:

  • If Category = Category A, only the relevant IPG options are shown.
  • If Category = Category B, a different set of IPG options is shown, only relevant to cat B
  • Users only see valid choices based on their previous selection.

From what I can see, I could do this with branching - but I would require a separate custom field for each category IPGs, which would make the custom fields within the project quite messy within the main project containing all.

This would help:

  • Reduce data entry errors
  • Simplify forms and task creation
  • Reduce the maintenance burden of managing very large dropdown lists

Is this something that could be supported either through:

  1. Native dependent/cascading custom fields, or
  2. Rules/Branching logic that dynamically filters the available options in another custom field?

If not currently possible, I’d be interested to hear how others have approached parent/child dynamic within custom field selection.

Thanks!

2 Likes
2

The only way I’ve found to “simplify” a field in a form is to create a local field(s) with limited options that lives in just that intake project, then automate updating the main Library/Shared field(s) based on those selections.

1 Like
3

Thanks Beth, will have a play with some rules :slightly_smiling_face:

I’ve actually got it as optional in the form so to save time scrolling through multiple non applicable IPG, they can just submit the form and then type it in within the project in the search single select.

4

@Rebecca_Hassett,

May I merge this topic into:

Thanks,

Larry

5

oh yes please @lpb - apologies, I did search for related topics but didn’t come across this one. Thank you!

1 Like
6

Thanks, @Rebecca_Hassett. I’ve merged this topic into an existing topic where you can click the title to scroll to the top and vote by clicking the Vote button at the top-left. Existing votes will be merged.

Thanks,

Larry