Display the Most Recent Child Record Value on a Parent Record

What You'll Learn

Knack does not have a built-in way to pull "the most recent" connected child record value onto a parent record through a formula. This article explains the three approaches that do work, and how to choose between them based on whether you need the value for logic or just for display.

The Problem with Text Formulas and Equations

Text Formula and Equation fields operate only on the current record's own fields. They can pull values from a single connected record, but they cannot sort, filter, or pick one record out of many. That means they cannot answer questions like "what was the date of the most recent interaction?" or "what is the latest order total for this contact?"

If you are reaching for a formula to solve this, stop. You need one of the three approaches below.

Example Scenario

You have a Contacts table and an Interactions table. Each Contact has many Interactions connected to it. You want to surface the date and outcome of the most recent Interaction on the Contact record.

This same pattern applies to any parent-child relationship where you need one specific child value on the parent: Customers and Orders, Projects and Tasks, Students and Assessments, and so on.

The Three Approaches

Approach A: Record Actions and Mapping Fields

Use this when the "most recent" value needs to drive downstream logic. Common cases:

• Sending an email that references the last interaction date
• Filtering Contacts by "most recent interaction in the last 30 days"
• Running reports that group or sort by the most recent outcome
• Displaying the value consistently across multiple pages without reconfiguring filters each time

This approach adds "mapping fields" to the parent table that mirror the child field types, then uses a record action on the child form to update the parent when a new child record is submitted. The value physically lives on the parent and behaves like any other field.

See: Store the Most Recent Child Value Using Record Actions and Mapping Fields

Approach B: Filtered Modal View

Use this when users just need to see the most recent child value on demand. You add a link on the parent table that opens a modal showing only the most recent child record, sorted descending and limited to one.

This works well when:

• The value is for viewing only, not for logic
• You don't want to add fields to the parent table
• You want to keep the parent table clean while still giving users one-click access

See: Display the Most Recent Child Record in a Filtered Modal

Approach C: Connected Child Records on a Parent Details Page

Use this when users navigate to a parent details page and would benefit from seeing all connected child records, with the most recent at the top. This is the simplest approach and often the most useful because it gives full context.

This works well when:

• You already have a details page for the parent
• The full history is meaningful, not just the most recent entry
• Users want to spot trends or patterns, not just one value

See: Display Connected Child Records on a Parent Details Page

How to Choose

Start with the question: do you need the value for logic, or just for display?

If you need it for logic, use Approach A. There is no other way to get the value onto the parent record as usable data.

If you need it for display, ask whether users would benefit from seeing the full history or just the most recent entry. Full history means Approach C. Just the most recent means Approach B.

You can also combine approaches. For example, use Approach A to store the value for email logic and Approach C to display the full history on the details page.

Common Mistakes

• Trying to build a Text Formula or Equation to pull the most recent value. These field types cannot sort or filter connected records.
• Using Approach A when a simple display would work. Mapping fields add maintenance overhead if they are not needed for logic.
• Using Approach B when users would benefit from full history. A single most-recent record hides useful context.

Next Steps

• Store the Most Recent Child Value Using Record Actions and Mapping Fields for logic-driven use cases.
• Display the Most Recent Child Record in a Filtered Modal for display-only use cases.
• Display Connected Child Records on a Parent Details Page when full history is valuable.