One option set determining the next option set

Need help
1

I am creating a repair app for powersports and I am trying to wrap my mind around option sets - I’m new to this world and reading as much as I can, but I’m obviously missing something.

I want to create a year-make-model option for repair orders. The year chosen will determine the make options available. Then the year AND make option chosen will determine the model options available.

Is this all done through conditional settings? Any help is greatly appreciated.

2

Are you intending to add all this data yourself?

3

Unfortunately, yes, as I haven’t been able to find a plugin for it.

4

Are there no APIs you can use?

5

Possibly, but I haven’t discovered them yet. Like I said, new to this world, so I’m not 100% where to find everything.

6

What exactly do you need?

7

Year, make, and model of powersport vehicles (motorcycles, quads, ATVs, side by sides…) and, if it exists, flat rate repair times for each vehicle

8

If you decide to do it yourself, you need to filter an option set by the relevant option set’s value when setting up the RG/dropdowns’ datasources in your order form.

for example: your make dropdown’s datasource will be All Makes:filtered:this make’s year is dropdown year’s value.

9

Great, thank you!

10

Hi, I think in your situation you should not go with option sets but datatype.

  1. Because maybe you will find an API to populate your database
  2. Maintenance when you need to do bulk operations to your datas
  3. Option Sets are fully load wherever on your app. And for big list of options sets/attribute it will slow down your app.

You should go for 2 datatypes here: Make and Model

  • With a field model for Make with a list of model children
  • with a fiel make for model with a list of make parents
  • And integrate the year as a field (list of number might be the best field type… but not sure)

After that, yep it’s conditionning and filtering when you call data.

  • Like a dropdown with a list of number from 1900 to current date’s year:formated as yyyy
  • a dropdown with a search on Make with year’s field that contains year’s dropdown value
  • and a dropdown with a search on Model with year’s field that contains year’s dropdown value and make contain make’s dropdown value

That’s just my opinion. Hope this help :slight_smile: