[object Object]

A sales rep updates the Account credit limit, opens an Opportunity for that account, and the Quick View still shows the old number. You restart the browser, it updates. This is not a bug, it is how Quick View Forms behave by default, and understanding the refresh rules saves you a week of support tickets.

How Quick View Actually Loads

Quick View Forms render a snapshot of the parent record taken at the moment the host record loads. The control reads from the lookup attribute, then issues a single retrieve against the referenced record. Once rendered, it does not poll. If the parent changes after the host form opens, the user sees yesterday’s data until they reload.

The control also respects the user’s security role on the referenced table. A user with no read access to Account will see an empty Quick View on the Opportunity, with no error and no warning.

The Refresh Trigger Map

There are exactly three events that refresh a Quick View:

1. The host form is fully reloaded (F5 or navigate away and back).
2. The lookup that drives the Quick View is changed to a different record.
3. A script calls the refresh method on the control.

Saving the host record does not refresh it. Switching tabs does not refresh it. Editing the parent in another window absolutely does not refresh it.

Forcing a Refresh from Script

When you need fresh values, target the Quick View control by name and call refresh. The control name is set in the form designer and is case sensitive.

function refreshAccountSnapshot(executionContext) {
  const formContext = executionContext.getFormContext();
  const qv = formContext.ui.quickForms.get("AccountQuickView");
  if (qv) {
    qv.refresh();
  }
}

Wire this to the OnSave of the parent if you have a plugin updating the Account, or to a custom button that the user can press after they know a teammate edited the related record.

Performance Costs You Underestimate

Each Quick View on a form is a separate retrieve. Three Quick Views on a Contact form means four database round trips before the form is interactive. On slow networks this is the difference between a 1.2 second form load and a 3.8 second one. Audit your forms in the Performance tab of Edge DevTools and remove Quick Views that duplicate data already shown by lookup tooltips.

What to Put on a Quick View, and What to Skip

Good Quick View content is reference data that rarely changes during a session: the account industry, the primary contact phone, the parent case category. Bad Quick View content is anything the user will edit in the next minute, anything that depends on rollups, and anything calculated from a related table further down the chain. For volatile data, replace the Quick View with a tightly scoped sub-grid filtered by a saved view.

The Caching Trap with Rollup Fields

If your Quick View shows a rollup field, you are looking at a value that the platform job recalculates on a schedule, by default once an hour. Even a manual refresh of the Quick View will not trigger a recalculation. Users will swear the system is broken when the Estimated Revenue rollup lags behind reality. Either move to a calculated field, or add a button that calls the CalculateRollupField action and then refreshes the control.

What to do this week

Open your top three most-used forms, count the Quick View controls, and remove any that show rollups or volatile data. Add a refresh call to the OnSave of the parent lookup, and document the freshness contract on the form description so the next developer does not chase the same ghost.

[object Object]
Share