Custom drop down elements

I personally always use just a repeater, you never know if you may need to adjust the output or classes or add a data-attribute in the option tags that is easy to do in a repeater.

Thanks Trevor...

I'm thinking about using a repeater at this point. I don't really know how to use the dropdown webpart, and all of your points make complete sense to me!

Cheers,

Shawn

Will this be collecting information? Maybe you can use a kentico form, and set the dropdown list data source to use a query. That way you can have multiple dropdowns inside of your form and also rig it up with dependencies.

Thanks Joshua,

EDIT: Some fields will be collecting information (input fields), however some fields will be pre-populated for a user selection (dropdowns). It's basically an advanced search page (think of a goods/services site) with dropdowns/inputs that will allow the user to select things like distance, type of product and price range.

If I were to use a Kentico form, which webpart would I use?

Thanks in advance,

Shawn

Actually then if this is a filter for a search, you should look into actually making / using Kentico's Filters, you can define a filter for an existing repeater (the product listing) and that way when they select, it applies a "where" condition automatically.

Otherwise, if this is not saving information, then i wouldn't do a form. If you were, then you would want to.

if using a Smart Search:

https://docs.kentico.com/display/K9/Using+search+filters

if applying to a repeater or data source:

https://docs.kentico.com/display/K82/Filtering+and+paging+data