Keep up to date with the latest news and thought leadership.
A dashboard is one of the most useful FileMaker modernization projects because it often uses existing data.
The challenge is not usually whether the data is available. The challenge is organizing that data into a view that helps people make decisions.
In this guide, we will walk through a practical approach to building an operational dashboard in FileMaker. The example is a manufacturing dashboard, but the same pattern can apply to service teams, sales operations, project management, inventory, fulfillment, or internal administration.
The goal is to create a dashboard that helps a team quickly answer questions like:
This should not be just a screen full of charts. A useful dashboard should help users decide what to do next.
Before creating fields, charts, or layouts, define the business decisions the dashboard should support.
For example:
This matters because a dashboard can easily become cluttered. If a metric does not help someone make a decision, it may not belong on the first version.
For a first version, choose three to five high-value metrics.
Example:
Next, map each metric to the FileMaker tables and fields that already contain the data.
A manufacturing dashboard might involve tables like:
Jobs table:
Orders table:
Materials table:
JobMaterials table:
QualityIssues table:
ProductionLog table:
You may not need all of these tables for the first version. Start with the data required to answer the most important questions.
Some dashboard logic can be handled with calculation fields in the source tables.
For example, in the Jobs table:
cIsLate
Returns true when the job is not complete and the target ship date is before today.
Plain-English logic:
Status is not “Complete”
and TargetShipDate is before today
cDaysLate
Returns the number of days between today and the target ship date.
Plain-English logic:
Today – TargetShipDate
cIsAtRisk
Returns true when the job is not late yet, but is close to the target date and still incomplete.
Plain-English logic:
Status is not “Complete”
and TargetShipDate is within the next few days
and QtyCompleted is less than QtyRequired
In the JobMaterials table, you may create:
cShortQty
Plain-English logic:
QtyRequired – QtyIssued
Depending on your data model, you may also need to account for available inventory, committed inventory, or material already allocated to other jobs.
The point is not to overbuild calculations. The point is to make dashboard logic easier to reuse and easier to understand.
There are two common ways to build a FileMaker dashboard.
Option 1: Live reporting from source tables
This approach uses found sets, portals, summary fields, subsummary reports, and charts directly against live data.
This can work well when:
Option 2: A dashboard cache table
This approach uses scripts to calculate dashboard metrics and write them into dedicated dashboard tables.
This can work better when:
For many operational dashboards, the cache-table approach is easier to maintain.
A simple dashboard cache structure might include two tables: one for metric cards and one for detail rows.
DashboardMetrics table:
DashboardRows table:
If multiple users will refresh dashboards at the same time, consider adding a snapshot table.
DashboardSnapshots table:
Then relate each DashboardMetric and DashboardRow to a specific snapshot.
That prevents one user’s dashboard refresh from clearing or changing another user’s dashboard results.
Create a script called something like:
Dashboard | Refresh Operations
The script should:
For example, the script might calculate:
There are several ways to calculate these values.
You can use:
The best method depends on the file, data volume, and performance needs.
For a small dashboard, FileMaker finds and summary fields may be enough. For a more complex dashboard, a scripted cache can be easier to control.
Create a dedicated dashboard layout.
A useful layout might include:
Example metric cards:
Each card should be clickable when possible. If a user clicks “Late Jobs,” the system should show the relevant jobs, not just the number.
That is what turns a dashboard from a display into a working tool.
A dashboard should help users move from summary to action.
Each DashboardRow can store:
Then create a script called:
Dashboard | Open Selected Row
That script can inspect the row type and source record ID, then take the user to the correct layout and record.
For example:
This makes the dashboard immediately useful.
Conditional formatting can help users identify what matters quickly.
For example:
Use this sparingly. If everything is highlighted, nothing stands out.
The goal is to make the next action obvious.
Dashboards should respect FileMaker security.
Before building the dashboard, decide who should see what.
For example:
If the source data is restricted, the dashboard should not accidentally expose it through summary records.
This is especially important if using a dashboard cache table. The cache should not store sensitive details that the user would not otherwise be allowed to view.
Not every dashboard needs to update every second.
For some teams, refreshing when the layout opens is enough. For others, a refresh button may be better. Some dashboards may need a scheduled server-side refresh every 15 minutes, hourly, or overnight.
Ask what the dashboard is used for.
If it supports real-time production decisions, it may need frequent refreshes. If it supports daily management review, refreshing once in the morning may be enough.
Avoid unnecessary refreshes that slow down the system.
The first dashboard should not try to answer every question.
Start with a focused version:
Then watch how people use it.
Do they click into late jobs? Do they care about throughput by department? Are the alert thresholds right? Are there metrics nobody uses?
A dashboard should evolve based on decisions, not decoration.
A practical FileMaker dashboard does not have to be complicated.
Start with the business questions. Map those questions to existing data. Add simple calculations where needed. Decide whether live reporting or a dashboard cache makes more sense. Build a focused layout with metric cards, exception lists, charts, and drilldowns.
The best dashboards help people act.
For many FileMaker systems, the data is already there. The opportunity is to make that data easier to see, understand, and use.
Let’s talk about how we can help you streamline, scale, or innovate—on your terms.
Start the Conversation
