Refresh Queries
Overview
A dynamic component reads its data when it loads. If an interaction then changes a record, the component still shows what it read before, so the change only appears once the page is reloaded.
The refresh interactions exist for that moment. Add one after the action that writes, and the component re-reads its data in place.
There are two of them:
Refresh All Queries, when everything on the page (or the whole current component) should re-read.
Refresh Query, when you want to name the components that should re-read.
Both act on components that run a query. See What a refresh does not do for what falls outside that.
When to use them
Add a refresh after any interaction that creates, updates or deletes data, including a Flow you run from the component with Execute Flow. A common shape is two actions on the same trigger: Update Record, then Refresh All Queries.
This also covers the case where a Salesforce automation reacts to your write. If a record-triggered flow fills in other fields after the update, those fields are on the record but not yet in the component. For components that run a query, the refresh is what brings them in.
Refresh All Queries
Re-runs the data queries of dynamic components so they show current information.
Scope to the current component
Refreshes only the queries inside the dynamic component that triggered the action. Leave it off and every dynamic component on the page refreshes. Turn it on when a single component is affected and you want to keep the page light.
Exclude self
Skips the triggering component's own query. Use it when that component has already updated what it displays and does not need to fetch its data again.
Refresh Query
Refreshes the query of the components you name, and nothing else.
Components
The components that should refresh. Leave it empty to refresh the current component only.
Use this one when a page holds several components and only some of them display the data you just changed.
What a refresh does not do
A refresh re-runs the queries of Avonni components. Two things sit outside that.
Components that do not run a query
A refresh interaction only reaches components that run a query, such as Data Tables, Lists, Kanbans, metrics and charts. A component bound directly to a field on the record, such as a Record Picker, does not run a query, so a refresh has nothing to re-run on it.
Those components pick up the new value another way: Update Record refreshes the page record fields and pushes them in on its own. Get Record does the same for a record variable. So a picker that reflects a change after Update Record is not doing so because of the refresh, and adding Refresh All Queries next to it changes nothing for that component.
Standard Salesforce sections
A refresh does not re-render standard Salesforce sections on the same record page, such as the highlights panel or a standard field section.
If a standard part of the page also has to show the new value straight away, a refresh is not enough on its own. A Navigate interaction back to the record reloads everything, at the cost of a full page load.
Related
Navigate
Execute Flow
Was this helpful?