How It Works
When configuring an action that needs to locate a record, you’ll use the Record Matching Conditions panel.
To set up a match:
Select a Field — Choose a column from your connected data source (e.g.
Status,Email,ID).Choose an Operator — Use logic like
Equals,Contains,Greater Than, etc.Define the Value — Enter a static value (e.g.
Completed) or a dynamic variable (e.g.{{ user.email }},{{ record.frontly_id }}).
You can also add multiple conditions for more advanced matching logic. The condition system is identical to what’s used throughout Frontly — in visibility rules, filters, and action logic — so it should feel familiar.
Where Record Matching Conditions Are Used
You’ll encounter Record Matching Conditions in places where Frontly needs to act on or pull data for a specific record, including:
Edit Forms
Used to bind a single record to the form for editing. The record matching conditions determine which row should be pre-filled and updated.Get Data Source Request (Action)
When using a "Get" request to pull one row of data into your app, the matching conditions determine which record to fetch from the data source.
More areas may adopt this system in the future as Frontly continues unifying its logic across blocks and actions.
Example
Want to edit a record where the user’s email matches the logged-in user?
Set your matching condition as:
Field:
EmailOperator:
EqualsValue:
{{ user.email }}
This ensures the form or Get action targets the correct row for that specific user.
Why This Matters
Using Record Matching Conditions allows you to:
Precisely locate a single row of data
Drive logic dynamically with session, form, or user-based inputs
Reduce reliance on static values or brittle row references
It replaces older methods like hardcoded row_id, offering a more flexible and scalable approach to record control.
Let me know if you'd like a visual walkthrough block next — could be helpful to show this in the context of a form!
You said:
Sorry it's not just the 'Get' Data Source Request action, but the 'edit' and 'delete' data source request action as well.
ChatGPT said:
No problem at all — here's the revised section with that added detail:
Where Record Matching Is Used
You’ll encounter Record Matching Conditions in any area where Frontly needs to act on or retrieve a specific record from your data source. This includes:
Edit Forms
Used to bind a single record to the form for editing. The matching condition determines which row gets pre-filled and updated.Get Data Source Request (Action)
When retrieving a specific row of data using the "Get" request action. Matching conditions define which record to fetch.Edit Data Source Request (Action)
Used when updating a record directly through an action. The condition ensures the correct row is modified.Delete Data Source Request (Action)
Ensures that only the targeted record is removed, based on the specified condition(s).
This consistent matching system makes it easy to work with individual records — no matter where you’re editing, retrieving, or removing data in your app.
Let me know if you want these broken into bullets with icons or made into a quick reference table!