NetSuite data refresh
Standard configurations are designed to receive updated NetSuite results approximately every 15-20 minutes. Exact completion may vary slightly with processing and search complexity.
Technical overview
A clear conceptual path from approved NetSuite information to the browser screen.
The exact collection and hosting method is confirmed for each implementation. This page explains the boundaries Xillix uses when scoping a standard NetSuite Scoreboard.
Core boundary
The required information must be reliably returned through customer-approved NetSuite reporting. Saved searches may be one approved source.
Conceptual data path
From approved search to visible scoreboard.
This sequence describes a reasonable implementation model, not a promise that every customer will use the same transfer, hosting, or access design.
Customer-approved NetSuite saved searches
One or more searches return the fields, formulas, filters, locations, and scope approved for the scoreboard.
Scheduled result collection
The agreed implementation retrieves or receives approved NetSuite reporting results on the standard schedule.
Secure transfer or retrieval
The customer-specific method and access boundary are confirmed during technical discovery.
Customer-specific scoreboard data
Results are mapped to the agreed measures, queues, pages, and data-as-of value.
Browser-based rendering
Compatible televisions, monitors, tablets, workstations, or meeting-room displays render the scoreboard pages.
Separate page rotation
The browser may rotate pages every 20-60 seconds or another configured interval without collecting NetSuite data again.
Visible data-as-of timestamp
Viewers can see when the current NetSuite snapshot was received or completed.
Agreed monitoring and maintenance
Only the checks, change process, and support responsibilities included in the implementation are represented as active.
Four distinct concepts
Do not treat every timer or stored value as the same thing.
Browser content checks
A browser or hosting check may confirm that content can be served, but it does not prove that the underlying NetSuite data changed or that every display is healthy.
Page rotation
The browser can rotate between pages on a separate interval, often 20-60 seconds, while using the latest available NetSuite snapshot.
Historical retention
A current reporting result does not automatically create point-in-time history. Historical snapshots exist only when available and included in the agreed implementation.
Reporting contract
Every displayed value needs a reviewable source definition.
SourceSearch owner, record type, fields, formulas, grouping, and criteria.
ScopeDates, locations, subsidiaries, statuses, roles, and exclusions.
AcceptanceRepresentative values reconciled against NetSuite before launch.
Display boundary
The screen configuration is part of the implementation.
Compatible browser display
Hardware, browser support, orientation, resolution, network access, and sign-in behavior are confirmed for the agreed display group.
Audience-specific content
A public-floor TV and a management workstation may require different fields, masking, density, and access.
Data-as-of communication
The display should make the latest available NetSuite snapshot time clear to the viewer.
Review the NetSuite data and display path before implementation.
Share the NetSuite question, intended audience, current reporting, and proposed screens so Xillix can identify the technical decisions that need confirmation.
Request a Technical Review