FSM Search Retrieval Limits
This reference is intended for administrators and developers who need search retrieval limits and supported retrieval options.
Standard FSM search retrieval returns the first 1,000 search rows. In supported locations, all: true retrieves further batches of up to 1,000 rows until the search results are exhausted. It doesn't remove NetSuite execution or governance limits.
|
Search Location |
|
|---|---|
|
Resolved element |
Passed to standard search retrieval. |
|
Resolved nested search. |
Passed for that individual search. |
|
Resolved report or email data search within a notification definition. |
Passed for that individual search. |
|
An individual named search within a standard article definition with multiple sources. |
Passed with that search's options. |
|
A search defined directly on an article with its own |
The standard single-source article retrieval doesn't pass this property to the search. |
For example, in the CRM Task options search in Defining a Search, all is alongside record, filters, and map. It is not a route-wide setting. In a collection of nested or named searches, set it separately on every supported search that needs more results.
Here, single-source means an article with a direct record property. It can display multiple records of that type. This definition doesn't mean that the resource displays only one record.
Search-row counts can differ from the number of final mapped objects. Joined rows can be merged, and summary searches return groups. Don't infer that all underlying data was retrieved solely from the number of visible records.
Retrieve only the records and columns needed for the behavior. Larger searches can increase load time, response size, and processing usage. If a direct article search needs to exceed the standard retrieval limit, resolve that design before relying on all in that location.
For guidance on measuring the effect of larger searches on loading time and response size, see Capturing FSM Performance Data.