Saved-search validation guide
Make the saved-search definition reviewable before it powers a scoreboard.
A familiar saved search can still contain assumptions that disappear when the result is summarized. Document the source logic and reconcile representative values before the number goes on a shared screen.
Guide in brief
- Name the owner and recurring question for every source search.
- Document criteria, formulas, dates, scope, permissions, and exclusions.
- Reconcile the scoreboard with NetSuite before launch and after material source changes.
Definition record
Capture what the search includes and excludes
- Record type, result columns, summary behavior, grouping, and formulas.
- Statuses, date basis, locations, subsidiaries, roles, and permissions.
- Exclusions, null handling, duplicate risks, and local business rules.
- Search owner, scoreboard owner, and approval responsibilities.
One or several searches
Combine searches only when their definitions can be reconciled
One summary search
Use one search when it reliably returns the required total, grouping, queue, or exception result.
Several approved searches
Use several searches when totals, comparisons, locations, or queues require distinct reliable logic.
New or revised search
Create or change a search when the agreed scoreboard question is not answered reliably by the current source.
Reconciliation
Test normal, boundary, and exception cases
- Compare totals for representative dates, periods, and locations.
- Inspect records near date, status, age, and formula boundaries.
- Verify role and permission effects with the approved audience.
- Document acceptable timing differences while an update is completing.
- Repeat validation after material saved-search or workflow changes.
Change ownership
Treat source changes as scoreboard changes
A changed formula, filter, location, role, or status definition can change the meaning of a displayed value. Assign ownership for notifying, reviewing, testing, and accepting source changes.
Keep the displayed label aligned with the approved definition. A short scoreboard label should not imply broader coverage than the saved search actually provides.
Frequently asked questions
Can Xillix create a saved search?
Yes, saved-search creation or revision may be included within the agreed scoreboard scope.
Can several saved searches power one page?
Yes, when each result has an approved definition and the combined view can be reconciled responsibly.
When should validation be repeated?
Repeat it after material changes to search criteria, formulas, roles, fields, locations, workflow definitions, or scoreboard logic.
Continue exploring
Related Xillix resources
Use these guides and Scoreboard pages to plan the next practical step.
Saved search scoreboards
Review the implementation offering built around one or more approved searches.
Explore saved search scoreboardsSaved-search examples
Review totals, queues, comparisons, and exception patterns.
Read the examples guideHow projects work
See where source confirmation and reconciliation fit in the project.
Read the project processBring one saved search and the question it is meant to answer.
Xillix can review the source definition, scoreboard audience, reconciliation path, and first implementation scope.
Request a Scoreboard Review