How to display events by category

[cheol.rim]

I am new to bubble and currently taking a stab at building the an eventbrite clone.

I followed the steps on the blog post and created a static category dropdown on the event upload page with three list items (Art, Fitness, Wine) and have been able to display all the events I created on the home page using a repeating group.

How can take this a step further and display only the events belonging to a specific category?

I read some other posts about categories and dropdowns and tried forking my clone app to create a dynamic dropdown by creating a category type and creating the same categories as separate text entries in the Name field.

When I run the preview, the category values are populated in the dropdown (from what I can tell by looking at the debugger), but categories are not visible to the naked eye.

Ideally, I’d like to display a dropdown that lists the existing categories and an option to create a new category.

Any help or suggestions would be much appreciated.

[Jici]

Choose an option caption

[cheol.rim]

That worked. I chose “Current option:capitalized words” and the dropdown options are now visible in the forked version of the app.

Any tips on how to display repeating group results for a specific category instead of all events in the DB? Can’t figure this out in either version.

[Jici]

You add a filter in RG based on the dropdown selection. You can check the checkbox “Ignore constraint if empty”

[cheol.rim]

That’s the part I was having trouble with. I started with Data Source: “Search for Events”, started building a constraint as “Category contains” and couldn’t figure out how to dynamically insert the dropdown selection into the constraint.
So I tried manually typing in the category text name, which also didn’t work. I finally figured out that I the type category name is case sensitive. This is what it ended up looking like:

Would be great if there was a way to dynamically pick from a set of existing database entries for the category (or any other field), but I guess I can move on from this point as I got the desired functionality albeit in a less elegant way than hoped for. Thanks for your input.