FileMaker Pro 26.1.1: The Features That Stand Out to Me

FileMaker Pro 26.1.1 is out. Claris’s release notes list everything that changed, so this post doesn’t try to repeat them. Instead, it covers the features that stood out to me, with an example of each that you can try in your own files.

Calculated Value Lists

Value lists have worked the same way for a long time. The values come from a field, from a hard-coded list of custom values, or from a value list in another file. If you needed a list that changed with context, you usually ended up with a helper table, an extra relationship, or a global field filled in by a script.

In 26.1.1, the Edit Value List dialog has a new option: “Use calculated value list.” You give it a calculation, and the result becomes the value list. The calculation can return one of two things:

  • Return-delimited text, for a simple list with one column.
  • JSON, for a list where each item can have a second value.

The JSON looks like this:

{
  "ValueList": {
    "values": [
      { "display": "Acme", "enterSecond": "1001" },
      { "display": "Globex", "enterSecond": "1002" }
    ]
  }
}

Every item needs a display key. You can optionally use a second value, depending on what you want the list to show and what you want it to put in the field.

Second keyThe value list showsThe field gets
(none)The display valueThe display value
displaySecondBoth valuesThe display value
enterSecondThe display valueThe second value
displayAndEnterSecondBoth valuesThe second value

An Example: A Pop-up Menu of Mondays

Let’s look at an example. Say you want a pop-up menu with three dates: last week’s Monday, this week’s Monday and next week’s Monday. Before, you’d need a script to refresh those values, or a table of dates and a relationship to filter them. Now a calculation can work them out every time:

Let ( [
  ~today = Get ( CurrentDate ) ;
  ~monday = ~today - Mod ( DayOfWeek ( ~today ) - 2 ; 7 )
] ;
  List ( ~monday - 7 ; ~monday ; ~monday + 7 )
)

Returns something like:

11/9/2026
11/16/2026
11/23/2026

To show a label next to each date, return JSON instead. With displayAndEnterSecond, the list shows both the label and the date, and the field gets the date:

Let ( [
  ~today = Get ( CurrentDate ) ;
  ~monday = ~today - Mod ( DayOfWeek ( ~today ) - 2 ; 7 )
] ;
  JSONSetElement ( "{}" ;
    [ "ValueList.values[0].display" ; "Last week" ; JSONString ] ;
    [ "ValueList.values[0].displayAndEnterSecond" ; GetAsText ( ~monday - 7 ) ; JSONString ] ;
    [ "ValueList.values[1].display" ; "This week" ; JSONString ] ;
    [ "ValueList.values[1].displayAndEnterSecond" ; GetAsText ( ~monday ) ; JSONString ] ;
    [ "ValueList.values[2].display" ; "Next week" ; JSONString ] ;
    [ "ValueList.values[2].displayAndEnterSecond" ; GetAsText ( ~monday + 7 ) ; JSONString ]
  )
)

Returns something like:

{
	"ValueList" : 
	{
		"values" : 
		[
			{
				"display" : "Last week",
				"displayAndEnterSecond" : "11/9/2026"
			},
			{
				"display" : "This week",
				"displayAndEnterSecond" : "11/16/2026"
			},
			{
				"display" : "Next week",
				"displayAndEnterSecond" : "11/23/2026"
			}
		]
	}
}

The Calculation Controls the Order

The list shows the items in the order the calculation returns them. The value list’s sort option doesn’t apply, and neither does “Include only related values”. The calculation decides both what’s in the list and the order.

When is the value list recalculated?

Field-based value lists are cached, and FileMaker only rebuilds them when the data behind them changes. Calculated value lists aren’t cached. FileMaker runs the calculation every time it needs the list.

That means an expensive calculation, such as an ExecuteSQL query that targets a table with an open record, runs every time the value list is referenced.

Which context is it evaluated in?

The Specify Calculation dialog for a calculated list has no “Evaluate this calculation from the context of” setting. Instead, the context is derived from whatever the current record happens to be.

More Indirection

Indirection means that a field, table occurrence, script or layout is referenced by a name (a text value) instead of by pointing directly at it. Set Field by Name has done this for fields for a long time. In 26.1.1, the same idea comes to three more places. This means one step can do what used to take a chain of If and Else If branches.

Set Variable by Name

Set Variable by Name has three options: Name, Value and Repetition. Unlike the regular Set Variable step, the name is a calculation, and it has to include the $ or $$ prefix itself. If the name evaluates to empty, lacks the $ or $$ prefix, or isn’t a valid variable name, the step returns error 5. One exception: a name with a space in it, such as “$first name”, is accepted without an error, but you can’t refer to that variable in a calculation afterwards.

For example, here’s a loop that turns every key in a JSON script parameter into a local variable:

Set Variable [ $param ; Value: Get ( ScriptParameter ) ]
Set Variable [ $keys ; Value: JSONListKeys ( $param ; "" ) ]
Set Variable [ $i ; Value: 0 ]
Loop
    Exit Loop If [ Let ( $i = $i + 1 ; $i > ValueCount ( $keys ) ) ]
    Set Variable by Name [ "$" & GetValue ( $keys ; $i ) ; Value: JSONGetElement ( $param ; GetValue ( $keys ; $i ) ) ]
End Loop

Replace Field Contents by Name

Replace Field Contents by Name works like Replace Field Contents, with the same options, but the target field comes from a calculation. The calculation has to return a fully qualified field name (Table::Field), or the step returns an error.

For example, a “Clear this column” button in a list view can pass the field name as a script parameter, and a single Replace Field Contents by Name step clears that field across the found set.

This one isn’t a new step. The existing Go to Related Record step has a new choice in its “Get related records from” menu: “Table by Calculation…”. The calculation returns a table occurrence name. Once you choose it, the layout is either the current layout or a layout name by calculation.

For example, a single navigation script can take a table occurrence name and a layout name as its parameter, instead of having one Go to Related Record step per table inside an If chain.

Beware of Indirection

This flexibility has a cost. When a step refers to a field, table occurrence or layout directly, FileMaker stores the reference by its internal ID. A rename carries over, and tools that analyze a file (the Database Design Report, Save a Copy as XML and the third-party tools built on them) can show you where each thing is used.

A name built by a calculation is just text. If someone renames the field, the reference breaks without any warning, and an analysis tool can’t tell what the step points to. The more a solution relies on this kind of indirection, the harder it gets to understand and change.

So use these steps where the flexibility pays off, and keep the references visible where you can. For example, GetFieldName ( Contacts::Status ) returns the text "Contacts::Status", but it’s still a real field reference. It follows a rename, and analysis tools can see it. Passing it to Replace Field Contents by Name is safer than typing "Contacts::Status" as a literal. Where you do need literal names, keep them in one place, so there’s one spot to check after a rename.

Getting a Script Result Back in a Web Viewer

If you’ve built anything interactive in a web viewer, you know the round trip. JavaScript calls FileMaker.PerformScript, and the script does its work. To send a result back, the script then uses the Perform JavaScript in Web Viewer script step on a named web viewer object, which runs a function on the page. That requires naming the object, writing a callback, and keeping track of which reply belongs to which request.

In 26.1.1, web viewer code can call FileMaker.PerformScriptAsync instead. It returns a promise, so the JavaScript code can wait for the FileMaker script to finish and get its result directly. Let’s look at an example:

async function loadCustomers() {
  try {
    const json = await FileMaker.PerformScriptAsync("Get Customers", {
      scriptParam: JSON.stringify({ status: "Active" }),
      timeoutMs: 10000
    });
    renderTable(JSON.parse(json));
  } catch (err) {
    showError(err.message);
  }
}

Here’s the play-by-play:

  • The page calls the Get Customers script with a JSON parameter, the same way it would with FileMaker.PerformScript.
  • The script finds the active customers and ends with Exit Script, returning them as JSON text.
  • await hands that text back to the page, which parses it and draws the table.
  • If the call can’t finish, for example because the script doesn’t exist or it runs past the 10-second timeout, the promise rejects and the catch block runs.

Beware that the function doesn’t exist in earlier versions. A file you’ve worked on in 26.1.1 still opens in 26.0, but there FileMaker.PerformScriptAsync is undefined. If some of your users haven’t upgraded yet, check for it before you call it:

if (typeof FileMaker.PerformScriptAsync === "function") {
  loadCustomers();
} else {
  // fall back to FileMaker.PerformScript and a callback
}

Layout Options That Replace Workarounds

Five of the new options in 26.1.1 replace tricks that a lot of us have been using for years.

A Single Checkbox Without a Value

When a field is formatted as a checkbox set, FileMaker draws one checkbox per value in the value list and uses the value as that checkbox’s label. To get one plain checkbox, you’d have to make a one-value list and then hide or crop the label.

The Inspector now has “Display single checkbox without value” for fields shown as a checkbox set. The field still needs a value list. With one value in the list, checking the box stores that value, and unchecking it clears the field. With two values, checking stores the first value and unchecking stores the second.

This is handy when you’re recreating a paper form. Many solutions have layouts that copy an existing paper form, often for printing a filled-in version. Think of government, medical or legal forms, with a small box to tick next to each printed line: “☐ Address has changed”, “☐ Patient is a minor”. On the paper form, the label is just printed text, laid out however the form designer chose, and the box sits exactly where it sits.

With a normal checkbox set, the label comes from the value list and is tied to the field’s position and formatting, so matching the form’s layout is fiddly. With “Display single checkbox without value”, you get only the box. You put it exactly where the form has it, and the label is a separate text object you can place and style freely.

An Indicator for Clipped Contents

When a field holds more text than it can show, nothing used to tell the user. Some of us built our own indicators for that.

Edit boxes now have “Show indicator for clipped contents” in the Inspector. When the text doesn’t fit, three dots appear along the bottom edge of the field, in the field’s border color. It shows in Browse mode, in Form and List view, and also on fields with a scroll bar. In WebDirect, a clipped field also expands when the user clicks into it.

The New Record Row at the Top of a Portal

For portals where the newest record should be first, such as notes or activity logs, the blank row for a new record has always been at the bottom. The usual fixes were a reverse sort, a dummy record, or a script that creates the record.

Portal Setup now has “Place row for new record at top”. The blank row sits at the top, and the portal keeps its sort order after the record is created. The option is only available when the relationship allows creating related records.

Turning Off the “Not Modifiable” and “No Records” Alerts

If a field is read-only and a user types into it, FileMaker shows the “This action cannot be performed because this field is not modifiable” alert. That gets in the way when you make fields read-only on purpose, so users can scroll and copy without editing. The usual fix was an OnObjectKeystroke script trigger that swallowed the keystroke.

Layout Setup now has “Show alerts when field isn’t modifiable or no records are present”. It’s on by default. Uncheck it, and that layout shows neither that alert nor the “No records are present” alert. It applies to the whole layout, not to individual fields, and it works in FileMaker Pro, FileMaker Go and WebDirect.

Button Icons From a Calculation

A button’s icon used to be fixed in Button Setup. To make an icon change with the data, you’d use a button bar with one segment per icon, all hidden but one.

Button Setup and Button Bar Setup now have a “Calculated icon” option. The calculation returns SVG as text. For example:

  • A favorite button that shows a filled or an empty star, depending on the record.
  • A status icon in each portal row, taken from the related record.
  • Icons kept as data in a table, so you can change them without editing layouts.

Icons can be up to 200 pixels, and only the SVG that FileMaker’s renderer supports will draw. Invalid SVG shows a warning icon, and Layout mode shows a placeholder.

A Custom Dialog That Closes Itself

Show Custom Dialog has a new “Close after (seconds)” option. The number of seconds is a calculation, so a variable works. A value of 0, a negative number, or anything that isn’t a number falls back to 3 seconds.

With the timer on, you can leave all three buttons blank. This gives you a message that shows for a moment and goes away, such as “Saved” after a commit. Without buttons and without a timer, FileMaker still shows an OK button, so a user can’t get stuck.

When the timer closes the dialog, Get ( LastMessageChoice ) returns 0. For example, a dialog with an OK button and a 10-second timer can tell the difference between a user who clicked OK and one who walked away.

Beware that on Windows, a dialog with an input field and no buttons doesn’t close on its own. If you use input fields, keep a button.

Reading the Current Sort With Get ( SortOrder )

Get ( SortOrder ) returns the current sort as JSON. It looks like this:

{
  "Sort": {
    "field": [
      { "fieldName": "Contacts::LastName", "sortOrder": "Ascending" },
      { "fieldName": "Contacts::FirstName", "sortOrder": "Ascending" }
    ],
    "maintain": "true"
  }
}

Each entry in field has the field name and its sort order: Ascending, Descending, or the name of a value list for a custom order. An entry can also have overrideLanguage and summary. Where there’s no found set, such as on the server, the function returns nothing.

For example, take clickable column headers in a list view. Clicking a header should sort by that column, and clicking it again should reverse the order. Until now, the script had to remember the current sort in a variable or a global field, and that got out of step as soon as a user sorted from the menu. Now the script can read the actual sort with Get ( SortOrder ) and choose the next one from that.

There’s no matching step that applies a sort from this JSON, though. To restore a sort, your script still needs a Sort Records step for each sort order it might apply.

Two Import and Export Options

Two smaller changes that people have wanted for years:

The “Use field names as column names in first row” option moved from Excel Options into the Specify Field Order for Export dialog, and it now works for CSV as well as Excel. This means a CSV export can have a header row without any post-processing.

When an import updates matching records or replaces the found set, there’s a new option: “Preserve target field data if source field is empty”. With it on, an empty value in the import source file no longer wipes out the existing value in the target field. That makes it safer to update records from a file where only some columns are filled in. It works in WebDirect too.

Takeaways

Most of these features replace a workaround that FileMaker developers have been building for years. The name-based steps and PerformScriptAsync go further and change how you can structure scripts and web viewer code. Use the name-based steps with care, though, because they hide references from the tools you use to analyze a file.

If you have questions about upgrading to FileMaker 26.1.1, or want help putting these features to work, contact our team.

Get the Demo

By submitting the form, you agree to our Privacy Policy. We will not contact you via text message.

Leave a Comment

Your email address will not be published. Required fields are marked *

Close the CTA

GET OUR INSIGHTS DELIVERED

Scroll to Top