Claris released FileMaker Pro 26.1.1 in November 2026. The release notes list everything, and Soliant Consulting's review covers the detail for developers. This guide is for the people who run a business on a FileMaker system and want to know what it means for them. We have left the code out. Where a feature replaces something we used to build by hand, we say so, because that is where the time and cost go.
Drop-downs that change with the situation
Until now, a drop-down list in FileMaker came from a fixed list of values or from a field in a table. If you wanted a list that depended on the situation, such as the engineers who are free on the day you are booking, your developer built a helper table, a relationship and often a script to keep it fresh. It worked, but every list like that was a small piece of plumbing to maintain.
In 26.1.1 a list can be worked out by a calculation each time it opens. Some examples of what that lets a system offer:
- A delivery date drop-down that shows only the next three working days, and skips bank holidays.
- A product list that shows only what this customer's contract allows them to order.
- A "send to" list of the people on this job, pulled from the job itself, not a global list of staff.
- A list of reasons that changes with the status the record is in, so a cancelled job offers cancellation reasons and a completed one offers sign-off notes.
Each list can show a friendly label and store the code behind it, so the user sees "This week" and the system stores the date. The one thing to know is that these lists are worked out every time they are needed, so a list built on a slow query will feel slow. We keep them simple and fast.
Many FileMaker systems replace a paper form, and some still print one. Risk assessments, inspection sheets, consent forms, a delivery note with a line of tick boxes down the side. Matching the paper layout was fiddly, because a tick box in FileMaker always carried its own label and you had to hide or crop it.
26.1.1 adds a plain tick box with no label. You put the box exactly where the form has it and the wording sits beside it as ordinary text, styled however the form needs. The screen looks like the sheet people already know, and the printed version matches the original. For a team filling in a form on a tablet in a van or a ward, that familiarity is the difference between a form that gets used and one that gets worked around.
Notes and logs that go in at the top
A notes panel, call log or activity list usually wants the newest entry first. FileMaker has always put the blank row for a new entry at the bottom, so you scrolled past everything to add something, or your developer wrote a workaround. Now the new-entry row can sit at the top, and the list stays in order after you save. Small change, used fifty times a day.
Two more small ones in the same spirit:
- You can see when a field has more in it. When a notes or address field holds more text than it shows, three dots appear along its bottom edge. Nothing is silently hidden any more. In WebDirect, clicking the field expands it.
- Read-only screens stop nagging. A screen built for looking things up, where the fields are locked on purpose, used to pop up "this field is not modifiable" every time someone clicked into one. That alert, and the "no records are present" one, can now be switched off for the whole screen. It works in FileMaker Pro, FileMaker Go and WebDirect.
Status icons that follow the data
A button's icon used to be fixed when the screen was designed. If you wanted a star that filled in when a record was a favourite, or a traffic light in each row of a list, it took a stack of hidden buttons and a rule for each. In 26.1.1 an icon can come from the data. What that gives you:
- A status icon in every row of a job list, read from the job, so the list reads at a glance.
- A flag on a customer record that changes with their account status.
- Icons kept in a table, so a new status gets its icon without a change to the screen.
Messages are tidier too. A confirmation such as "Saved" can now show for a couple of seconds and close itself, rather than waiting for someone to click OK. A system can also tell the difference between a user who pressed OK and one who walked away, which matters on a shared screen in a warehouse or a reception.
Modern screens inside FileMaker that talk back properly
Some of the best screens in a FileMaker system are not FileMaker screens at all. They are web pages shown inside FileMaker's web viewer, built with modern tools, with the kind of list, chart or map FileMaker's own layouts struggle with. We did this for Travel Places, where new web pages took over single screens inside the existing system, such as lists whose columns each person chooses and a flight list that opens level by level, before the operations platform moved to the web. You can read how that went in our work.
The awkward part was getting an answer back. The page could ask FileMaker to run a script, but to get the result it needed a named object, a callback and some bookkeeping to match replies to requests. In 26.1.1 the page can ask for a script's result and wait for it, with a timeout if it does not come. Screens like this are quicker to build, easier to keep working and fail more gracefully. The catch is that the page has to check the feature exists, because a machine still on 26.0 will not have it, so this one is best done once everyone is on the update.
Safer imports and cleaner exports
Two changes people have asked for over years. If your team updates records from a spreadsheet, such as a supplier price list or a customer list from a mailing house, a blank cell in the file used to wipe out the value you already had. There is now an option to keep what is there when the incoming cell is empty, which makes updating from a part-filled spreadsheet safe. It works in WebDirect too.
Going the other way, a CSV export can now carry the field names as a header row, which only Excel exports could before. If you send extracts to an accountant, a courier or a reporting tool that expects a header, that is one tidying step gone.
Exports and sort lists can also show a field's friendly display name rather than its database name, so "Customer name" instead of "cust_nm_01". The 2026 release introduced display names; 26.1.1 carries them into imports, SQL and the OData interface that integrations use, and lets you hide a field from the export and sort lists altogether.
Changes that take an hour instead of a day
The rest of the release is for developers, but you will feel it in the invoice. Three script steps can now refer to a field, a table or a screen by a name worked out at the time, rather than being fixed when the script was written. In practice that means one script where there used to be a dozen near-identical ones: one navigation script instead of one per module, one "clear this column" button instead of a button per column. Fewer scripts means fewer places for a change to go wrong and less time to make it.
There is a trade-off, which Soliant's review is right to flag. A reference built from a name is just text, and if someone renames the field later, nothing warns you that the script now points at nothing. We use these steps where they pay for themselves and keep the names in one place, so a rename has one spot to check. If you have had a health check from us, this is the kind of thing it looks for.
Scripts can now also read the sort a user has applied, so clickable column headings in a list behave the way people expect, sorting one way on the first click and reversing on the second, even after someone sorted from the menu.
AI features for the systems that use them
Two additions for systems already using FileMaker's built-in AI. Semantic find now works on images as well as text, through Google's image embedding model, so a system holding photographs, such as site photos or damage photos, can find pictures that look like the one you are holding rather than relying on a typed description. And a system's custom functions can now be described in a form that AI models understand as tools, which is the groundwork for letting an assistant act inside your system rather than only answer questions about it. For what works in production today, read AI and LLMs inside FileMaker, and for connecting an assistant to your data, how to build a FileMaker MCP server.
What has to be in place to use them
These features need FileMaker Pro 26.1.1 on the machines that use the system. A file that has been changed to use them still opens in an earlier 26 version, but the new behaviour is not there, and the web viewer feature has to be checked for before it is used. The sensible order is the same as for any release: update the server first, then the clients, then start using the new features in the system. If you are still on FileMaker 2024 or 2025, FileMaker 2026, what's new and should you upgrade covers the bigger move and the licensing questions.
For the systems we look after under FileMaker support, we plan the update with you and tell you which of these are worth putting into your system first. Usually the quick wins are the lists, the notes panels and the import option, because they touch what people do every day and take hours rather than days to put in.