Field hierarchy/nested dependencies

I’m struggling with this use case. Imagine I have a Widgets object (as a Collection.) A Widget has 3 fields: Type, Size, and Color. The possible Sizes depends on the Type and the Color depends on the Size.

When a user interacts with this Widget object they typically start by choosing the Type, and then Size and Color. I have created Type, Size and Color as collections and set up the proper relationships. But how do I create an experience - like a form or series of forms - to create a new Widget where the hierarchy is preserved? When I create a Widget I can choose any Type. But then when I choose Size the possible selections are dependent on what Type was chosen. Similarly, when I then choose Color, I should only see options based on the selected Size.

Any thoughts on how to implement this functionality? TIA!

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.