Refresh – reading the current record again¶
The command "Refresh" reads the fields of the current record again from the database. This page is for administrators whose actions work on a record that something else may have changed in the meantime.
1. At a glance¶
| Purpose | Get the stored state of the current record |
| Typical use | After a called action, an API call or a background step changed the record |
| Where in the editor | Toolbar menu "Data" → "Refresh" |
| Needs a user interface | No |
| Needs a current record | Yes |
| Related | Discard, Invalidate Relationships, quick action "Refresh" |
2. Settings¶
The command has no settings of its own – only "Display Name", "Description" and "Execution Condition" on the tab "General" (see Actions).
3. Behaviour¶
- Without a current record, the command is skipped.
- A record that was never saved is left as it is.
- Otherwise the fields of the record are read again from the database and replace what the action had in memory.
- The list of files attached to the record is read again the next time it is needed.
Related records are not read again – use Invalidate Relationships for them.
4. Example¶
After an external update. An action calls an external service with HTTP Request, which writes the shipping status back into the order through the REST API. A following Refresh makes the new status visible to the next commands, for example a Switch on "Shipping status".
5. Limitations¶
- Unsaved changes of the current record that the database read replaces are gone. Save first if you need them.