Refresh Field Data
Audience:
Low-code EngineersSkill Prerequisites:
Actions,Forms 2.0,Tokens
Changes the value of the Forms 2.0 fields you list, without reloading the page. The browser shows the new values right away. Only the fields you list change.
This action is only available in Forms 2.0, in button actions and other events that run after the form has loaded.
Typical Use Cases
- Fill in a customer's address after the user enters a customer number and clicks Look up
- Show a value calculated on the server, such as a generated order number or a price from a database
- Clear some fields after a button's actions, without resetting the whole form
Don't use it to
- Calculate a value that only depends on other fields. A field's Value automation updates it in the browser without calling the server. See Field Automations.
- Set a Repeater's entries or the fields inside a Repeater. Use Refresh Form Data from JSON instead.
- Set field values while the form loads, in On Preinit, On Page Load or After Fields Initialization. It's not available there. Set the field's Initial Value, or create a token with the field's name in On Preinit.
Related Actions
| Action Name | Description |
|---|---|
| Refresh Form Data from JSON | Sets many fields at once from a JSON object, including Sections and Repeaters. |
| Refresh Form Data from Context | Refreshes every field from the tokens with the same name, then ends the actions. |
| Run SQL Query | Reads values into tokens that you can use in the Value column. |
Input Parameter Reference
| Parameter | Description | Supports Tokens | Default | Required |
|---|---|---|---|---|
| Fields to Refresh | One row per field to change. Click Add Field to add a row. | Yes | empty | Yes |
| Fields to Refresh > Field | The field to change. Pick it from the list, or switch to an expression to type its name, for example a token. Fields inside a Section use their full name, for example Billing:City. | Yes | empty | Yes |
| Fields to Refresh > Value | The new value. Leave it empty to clear the field. | Yes | empty | No |
| Continue Execution | When checked, the actions after this one run. When unchecked, this action ends the action list. | No | True | No |
How it works
- The rows are handled one at a time, from top to bottom. Each row's Value is resolved just before it's set, so a later row can use the value an earlier row set, for example
[City]. - Each value is set on the field on the server, so the field's token has the new value for the actions that follow.
- The changed fields are sent to the browser, which shows the new values. A validation error shown on a changed field is cleared.
Considerations
- Put it after the actions that load the values. The Value is resolved when this action runs.
- Unknown names become tokens. If Field doesn't match a field on the form, nothing on screen changes, but a token with that name is set for the next actions.
- Repeaters aren't supported. A Repeater, or a field inside one, can't be changed here. Use Refresh Form Data from JSON.
- Inactive fields aren't shown. A field that isn't active isn't on the page, so it isn't refreshed in the browser.
- Conditions. To refresh only in some cases, give it a condition. See Common Parameters.
Examples
tip
To understand how to use the below examples, please see Running Examples.
1. Fill in an address from a customer number
Add this action to a Look up button, after a Run SQL Query that loads the customer into the Customer token. The Street and City fields show the customer's address. The Notes field is cleared.
{
"Title": "Refresh Field Data",
"ActionType": "RefreshFieldData.Csp",
"Description": "Show the customer's address",
"Parameters": {
"Fields": [
{
"Field": "Street",
"Value": "[Customer:Street]"
},
{
"Field": "City",
"Value": "[Customer:City]"
},
{
"Field": "Notes",
"Value": ""
}
],
"ContinueExecution": true
}
}
Revised 11/18/2026