You can get type-ahead filtering and true record IDs from a single FileMaker field without building a portal. Kyo Logic’s free Type-Ahead Value List add-on does it with a small web viewer, and you configure it entirely with FileMaker scripts.

Here is the moment it exists for. An order entry layout has 2,000 customers in the value list. Your user types “Acme.” With a pop-up menu, they scroll. With a drop-down, they can type, but drop-downs do not handle a hidden ID well, so teams often end up storing the name instead of the customer ID. The first time two customers share a name, the order attaches to the wrong one. With a portal, it works, after someone builds a new relationship, a global field, three script triggers, and a card window to hold it all.

Why do FileMaker’s built-in pickers make you choose?

FileMaker gives you three standard ways to let someone pick from a list. Each one solves part of the problem.

• Pop-up menus store the underlying ID cleanly, but their type-ahead is limited. On a long list, users end up scrolling.
• Drop-down lists let users type to filter, but they do not handle underlying IDs well. You end up storing a name where you wanted a key.
• Portals can do both, but usually only after extra plumbing: new relationships, script triggers, global fields, and often a card window to present the list.

For a short list of statuses, any of these is fine. For customers, parts, SKUs, employees, or any list that grows, you feel the gap every day. Either users fight the picker, or a developer spends hours wiring up a portal for every field that needs one.

What the add-on does out of the box

The add-on uses basic web code inside a FileMaker web viewer to bring the strengths of all three options into one control:

• Type-ahead filtering. The list narrows as the user types.
• Value or ID selection. Return the value the user sees, or the underlying ID you actually want to store.
• Works anywhere a web viewer does. Popovers, portals, and card windows included.
• Multiple configurations. Set up different pickers for different fields and lists in the same solution.

Because the selection can return an ID, the field that matters stores a real key. Two customers named “Acme Supply” stop being a data problem.

Setup lives in FileMaker scripting

Each configuration is customized through standard FileMaker scripting, so you control what the list shows and what it returns the same way you control everything else in your solution. You do not need to know HTML, CSS, or JavaScript. The web code ships with the add-on; you only touch FileMaker.

Where it helps most

• Order and quote entry: pick the customer by name, store the customer ID.
• Line items in a portal: choose parts or SKUs from a long catalog without a second portal inside the first.
• Popover filters: a searchable picker inside a popover keeps the layout clean.
• Card window lookups: reuse one configuration across several card windows instead of rebuilding the lookup each time.

Tips before you roll it out

Decide what you are storing first. If the field is a foreign key, return the ID. If it is a label or a note, return the value. Mixing the two across fields is how bad data starts.

Keep one configuration per list, not per layout. Multiple configurations are supported, so reuse them. Fewer configurations means fewer places to update when the list changes.

Test with your real list size. A picker that feels instant with 50 rows should be checked against your full customer or parts table before you put it in front of the team.

If you have used our older technique, Replace DropDown Lists with a Faster Type Ahead, this add-on packages the same idea into something you can drop into any solution and configure with scripts. It pairs well with the Custom Import Tool for getting clean data in, and the Audit Log & Version History add-on for seeing what changed afterward.

What this could look like in your solution

For most teams, the first picker worth replacing is the one people complain about: the customer field on the order screen, or the part number on a line item. Once that field filters as people type and stores the real ID, mismatched records stop showing up in reports, and nobody has to remember which “Acme” is which.

Kyo Logic builds custom Claris FileMaker and manufacturing software for businesses across New England and beyond. If you want help deciding which fields to convert first, or wiring the add-on into a complex layout, reach out.

Frequently asked questions

Can a FileMaker drop-down list store an ID but show a name?

Not cleanly. Drop-downs are built around the value the user sees. Pop-up menus can show a second field while storing the ID, but their type-ahead is limited. The Type-Ahead Value List add-on gives you both type-ahead and the stored ID.

Does this add-on require JavaScript knowledge?

No. The web code is included. All configuration happens through standard FileMaker scripting.

Can I use it inside a portal or popover?

Yes. It runs in a web viewer, so it works in popovers, portals, and card windows.

Can I set up more than one type-ahead picker in the same solution?

Yes. The add-on supports multiple configurations, so different fields can use different lists and return different values.

Quick takeaways

• Find the longest value list your team picks from every day and convert that field first.
• Return the ID for any field that links records; return the value for labels and notes.
• Reuse one configuration per list across layouts, popovers, and card windows.
• Download the add-on and test it against your full list size before rolling it out.