Search View Setup

Based on what you described, the cleanest setup is to stop relying on the default keyword search for this part and use a custom search form with a Team dropdown that filters the Games View by the selected team.

The default [frm-search] search looks for string matches, so a term like men can also match women . A dropdown filter avoids that problem because it filters by the selected team value instead of partial text matching.

How to set it up
Step 1: Create a separate Search Form with a single Team dropdown field.
If your Game form uses a Dynamic field for Team, add a Dynamic field with identical settings in the Search Form as well. That means it should load the team options from your Teams form.

Documentation:

  • Create a Custom Search Form
  • Dynamic Fields

Step 2: Publish your Games View on the page where you want both the dropdown and results to appear with a shortcode like this:

[display-frm-data id=”x” filter=”1″]

Replace x with your View ID.

This allows the View to work with the filters passed in the URL.

Step 3: In the Search Form Settings → Actions & Notifications → Confirmation, choose Redirect to URL.

Set the redirect URL to the same page where your Games View is published. Then add a parameter for the selected team, for example: ?team=[123 show=”ID”]

Replace 123 with the field ID of the Team dropdown in the Search Form. That passes the selected Team entry ID into the page URL after submission.

Step 4: Edit your Games View and add a View filter.
In Filter Entries, add a filter like this: Team field is equal to [get param=team]

That tells the View to display only Games whose Team matches the selected dropdown value.

What the final result looks like
You can place the Search Form above the Games View on the same page.
When someone chooses a Team from the dropdown and submits the form, the page reloads with a URL like: ?team=45
Your View then shows only the Games linked to Team 45 .

A couple of important notes

  • Make sure the parameter name you choose, such as team , matches exactly in both places: the redirect URL and the View filter.
  • Avoid reserved WordPress parameter names.