Make a FileMaker dashboard count agree with its detail list

Start with the records behind the number

A card says “2 overdue tasks,” but its action opens three records. The number may use a different date, include completed work or ignore a selected project. Repair the definition before changing the card’s formatting.

For this example, overdue means: the task belongs to project P01, is not completed, has a due date, and that date is before 21 October 2026. Today’s tasks are not overdue. Blank dates belong in a separate missing-date view. These are explicit choices for this example, not universal rules.

Make the membership visible

On a small screen, scroll the table sideways to see every column.

The expected membership is D01 and D06, so the expected count is two. Use these IDs as review labels; production records should have immutable keys. Define IsCompleted as a validated number, 0 or 1, and require ProjectID. Ambiguous status text should be normalized before reporting.

Share the selection contract

not IsEmpty ( Tasks::DueDate ) and
Tasks::DueDate < $asOf and
Tasks::IsCompleted = 0 and
Tasks::ProjectID = $projectID

The provider and action should receive the same project ID and as-of date. A timestamped dashboard snapshot can also record the selected IDs for comparison. Do not quietly recompute “today” halfway through a report that remains open across midnight.

{
  "projectID": "P01",
  "asOf": "2026-10-21",
  "expectedIDs": ["D01", "D06"],
  "count": 2
}

This small JSON object is a teaching contract for your own worker. It is not a replacement for Filesoft Dashboard’s documented provider schema. Validate it and construct a Date value explicitly when the worker receives it.

Connect the existing provider and action slots

Filesoft Dashboard’s configuration guide separates FSDASH | Data Provider from FSDASH | Action Router. Adapt the provider to your schema, and connect an available native action slot to the detail-list script. Preserve the router’s existing guards. Do not assume a KPI card itself is an automatically connected drill-down.

The provider supplies the card value using its documented payload. The action script applies the same membership rule on the correct Tasks layout and reports its own success or failure. A successful Perform Script call alone does not prove the correct list opened.

A live list may change after the snapshot: another person can complete a task. Choose an honest policy. Either label the card as a snapshot and explain the change, or refresh the card and list together. Do not force a stale count onto new data merely to make the screen look consistent.

Compare IDs before comparing appearance

Load the six fixture rows and capture the card count and detail IDs. Complete D01, refresh and expect only D06. Change the filter to P02 and expect D05. Use a project with no matching tasks and expect a zero card plus an explicit empty list.

Repeat under a restricted account; both views must respect the same authorized scope. Open a task and return, confirming that the chosen project remains selected. Then change the as-of date and confirm both surfaces refresh together.

The fixture checks the reporting rule, not the add-on’s native rendering. The downloadable configuration guide and your installed version remain authoritative for integration. Record native UI results separately from checking the expected IDs in the CSV.

Try the small review fixture

The fictional data and review notes below accompany this article. They are not a FileMaker application, and they do not establish native test results.

• dashboard-tasks.csv
• Expected record IDs and counts (JSON)
• Setup and native review instructions

References

Documentation checked on 21 October 2026. This review does not establish native execution or hosted compatibility.

• Filesoft Dashboard configuration guide
• Get ( FoundCount )