About the Recordset Query Limitation and Page Size

When Recordset Query Limitation is enabled for an entity, the system appends an additional command to a view's SQL query before sending it to the database server. This command limits the maximum number of records returned by the server based on the user's Recordset Query Limit. If the number of records returned matches the user's Recordset Query Limit, a message is displayed to the user informing them that the limit was reached.

List views also support paging. This functionality breaks up a view's results into one or more pages of a specified maximum size. Paging appends the same command to a view's SQL query as Recordset Query Limitation (although in this case, the record limit is the size of the page). However, when using paging, a user can navigate the other pages to review all of the data returned by view.

If you intend to use Paging in conjunction with Recordset Query Limitation, keep in mind the following conditions:

• The Recordset Query Limit is not imposed if the view's Page Size is less than the Recordset Query Limit. However, the Recordset Query Limit continues to apply if the view's Page Size is greater than the Recordset Query Limit.
• Paging and a view's Page Size is controlled on a view-by-view basis, and users can modify these settings as necessary. Recordset Query Limitation is configured on an entity-by-entity basis by an administrator to prevent a user from executing a query that returns an excessive number of rows.