I am trying to set cascaded selections between a regular selection field (Product Category in the image below) and a selection field on a subtable (Spec Name in the image below). Unfortunately, it seems this is not supported, or am I just doing something wrong? Or maybe there is a workaround using a lookup table or similar?
What I am trying to accomplish is a web form where the user selects a product category, then a list of relevant specs for that specific product category only will be selectable in the first field of every subtable row below. The user can then choose each spec name one by one on the left, and enter a value for each on the right (see example specs in the attached screenshot). Only the relevant specs for that particular product category selected at the top would be available for selection in the subtable.
Is there really no way to have a selection field cascade options to the selection fields in a subtable right below it? Seems like a pretty common use case…
Thanks for sharing your use case and the detailed description — it makes the setup very clear.
To confirm: cascaded selections currently only support referencing another selection field within the same subtable, so linking a subtable selection field to a regular field is not supported at this time. We’ve recorded your use case and will provide an update on this thread if this becomes supported in the future.
That said, there is a workaround worth trying. If you restructure Spec Name as a link & load field pointing to a separate spec lookup table (with a Category column and a Spec Name column), you can then apply Dynamic Filtering on that field using Product Category as the filter condition. This would give you the same result — only the specs relevant to the selected category would appear as options in each subtable row.
The main trade-off compared to cascaded selections is that available options come from records in another sheet rather than the field setting under design mode, so there is some additional setup involved in maintaining the lookup table. On the other hand, having the parent-child spec relationships laid out as rows in a referenced sheet can actually make them easier to manage over time.
I see. Maybe there is a technical reason to not support cascading selections from a normal selection field to a subtable, but this is definitely a feature that would be useful for many users. If it’s not too difficult to implement, I really hope Ragic can make the change sooner than later.
Hi Pax, thank you for the feedback. We understand this would be a useful addition and will share an update on this thread as soon as there’s any progress to report.
Hi Pax, great news — the feature you requested is now available in our latest update! Cascaded selection fields in subtables can now reference a regular selection field outside of the subtable.
