Data freshness guide

Tell viewers when the NetSuite snapshot changed and when only the page changed.

A moving scoreboard can look live even when the data has not changed. Clear timing language and a visible data-as-of value help the team interpret the current snapshot correctly.

Start a ScoreboardTechnical Overview

Guide in brief

  • Describe standard NetSuite updates as approximately every 15-20 minutes, not real-time.
  • Keep page rotation on its own configured timer.
  • Show a visible data-as-of value and define what it represents.

Data refresh

Use precise standard timing

Standard scoreboard configurations are designed to receive updated NetSuite results approximately every 15-20 minutes. Exact completion may vary slightly because of NetSuite processing, reporting complexity, and the agreed implementation.

Do not call the scoreboard real-time. A viewer should understand that the page displays the latest available NetSuite snapshot.

Page rotation

Changing the page does not collect NetSuite data again

Scoreboard pages may rotate every 20-60 seconds or at another configured interval. That timer controls what the browser shows, not when NetSuite results are updated.

Every page in the rotation may use the same latest available snapshot until the next scheduled data update completes.

Data-as-of design

Make freshness visible without dominating the screen

  • Use a plain label such as Data as of with an unambiguous date and time.
  • Keep timezone and location context clear when viewers span regions.
  • Define whether the timestamp means collection started, results completed, or the scoreboard snapshot was published.
  • Place the timestamp consistently across rotating pages.
  • Do not imply that page motion proves fresh data.

Historical boundary

Current reporting results do not automatically create history

Period comparisons may require separate searches or historical snapshots. Historical point-in-time retention exists only when technically available and included in the written implementation.

A current search can change as records change. Decide whether a comparison needs current-period logic, separate prior-period logic, or retained snapshots before promising a trend view.

Frequently asked questions

Is a Xillix Scoreboard real-time?

No. Standard configurations are designed for updated NetSuite results approximately every 15-20 minutes.

Does every page have a different refresh time?

Pages may share the latest available snapshot. Page rotation is independent and does not trigger a new NetSuite collection.

Does a saved search provide historical snapshots?

Not automatically. Historical retention must be available and specifically included in the implementation.

Continue exploring

Related Xillix resources

Use these guides and Scoreboard pages to plan the next practical step.

Define what fresh enough means for the recurring decision.

Xillix can review the NetSuite reporting, standard update schedule, page rotation, and data-as-of communication for a focused scoreboard.

Start a Scoreboard