MAXRECORDS node
The node of the Hansen8 configuration defines the maximum number of records Infor Public Sector will return in lookups and collections. This node can have these attributes:
| Attribute | Description |
|---|---|
| Batch Update Limit | Maximum number of criteria to use in a batch update statement (typically an "IN" statement). The number should not exceed what is allowed by the provider for processes that support batch updates. |
| Record Load Limit | Maximum number of records to retrieve from the database at one time when a
collection is loaded. The default is 100. For example, suppose a user
searches for all work orders in the system. If this number is set to the
default, Infor Public Sector will return 100
work orders and show them in the grid. If the user keeps clicking
on
the grid, Infor Public Sector will return the
next 100 records after the user reaches the 100th record in the grid. The Record Load Limit should be equal to the product of the Grid Page Size and the Grid Page Count attributes on the node. Performance degradation will result if otherwise. This number determines the balance of memory to performance. Higher numbers of records will consume more memory, and lower numbers will give better performance (with a few exceptions). 100 was chosen as a good balance between the two and should rarely be changed. |
| Serialization Limit | Maximum number of records to send back to a web service at one time when
a user requests loading of a collection. For example, the user in a web
service might want to load all service requests. The Record Load Limit attribute is used initially to load the records. The Serialization Limit attribute then determines how many of those records to send back to the web service. Therefore, the Record Load Limit and Serialization Limit numbers should match to avoid additional database requests, or the Serialization Limit should be less than the Record Load Limit. |
| Unpaged Load Limit | Maximum number of records to return before paging is forced. |