Skip to content

Dependent/filtered relation/field aka parent & child relationship/field #8708

@derrickmehaffy

Description

@derrickmehaffy

Feature request

Please describe your feature request

  • I have created my request on the Product Board before I submitted this issue
  • I have looked at all the other requests on the Product Board before I submitted this issue

Summary

This feature request comes from various community requests (Forum, meetups, Slack, ect) and I will do my best to link to those to hopefully make the request clear.

The easiest example to explain is laid out like this, we have the following models:

  • Make
  • Model
  • Sales

In this context we are talking about cars, so the make would contain a list of car manufacturers (Subaru, Toyota, Ford, Chevy, ect). Thus the model would contain some options like WRX, GT86, Mustang, Corvette.

The way we would setup the sales model would be a oneWay relation to each make/model, and in the context of this request when we create a new "sale" we would select the make (say subaru) now when I go to select the model I should only be able to see/select the "WRX" model since it's made by Subaru.

I should not be able to select "Toyota" "Mustang" as that car doesn't exist.

Why is it needed?

Simply put, requested by our users

Suggested solution(s)

Discussed in various places, effectively there needs to be a link between the two models and a filter pre-applied in the admin where the 1st option (parent) is included as a filter in the 2nd option (child).

Related issue(s)/PR(s)

https://forum.strapi.io/t/customize-relations/1260
https://forum.strapi.io/t/limiting-relational-options-in-admin/1173
https://forum.strapi.io/t/get-all-model-in-custom-field/795
(There are more, I'll add them when I find them)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions