Managing the Recordset Query Limitation

Recordset Query Limitation lets an organization limit the number of records that are available to a user within a list view. This is particularly useful for entities that have a large number of records, such as Persons. If a user opens an "all" view of such an the Persons entity, it can require a large amount of time and system memory to run a query that retrieves all records.

This situation is further exacerbated if the user is connecting to Aptify from a shared server using a terminal client, such as with Windows Terminal Server software. In this case, the view query reduces system response time for not only the user who opened the view but also for other concurrent users.

Limiting the number of records in a view prevents users from inadvertently slowing down the system. It also encourages users to create and use targeted views rather than spend time scrolling through all available records.

Note that Recordset Query Limitation does not prevent a user from accessing any particular record; all records are still available to the user. This feature only limits the number of records that can be displayed within a single page of a view.

Recordset Query Limitation applies only to List views; it does not apply to Pivot Table, Pivot Grid, Calendar, or Chart views.

This topic contains the following sub-topics:

• Enabling Recordset Query Limitation
• Disabling Recordset Query Limitation
• About the Recordset Query Limitation Effects
• About the Recordset Query Limitation and Page Size