Data Pagination
Description
Data pagination means breaking data up into pages. The properties here specify how users move through and view large blocks of data. For example, when viewing a data set with 100 rows or more of data, a user might only be able to view a given number of rows at a time. In this section you can choose how big the page should be, what controls should be used to navigate the pages, what these controls should look like, a what they should say.
- Name
- Description
- Paginate data
Specify if the list will show all of the data in the query initially, or will only display a page of data. The user can then request additional pages of data. Checking this property opens up a host of additional pagination properties.
- Page size
Specify how many rows of data to show in a 'page' of data.
- Pagination method
Specify if pagination will be done using buttons for First, Previous, Next, and Last, a 'Fetch More' button willl appear in the List Data Footer, or 'AutoFetchMore' which is similar to 'Fetch More' except that no 'Fetch More' button is displayed. Instead, more records are automatically fetched as you scroll toward the end of the records that are currently loaded into the List.
- 'Fetch More' control text
Specify the text to show on the 'Fetch More' button.
- 'Fetch More' control type
Specify if the 'Fetch More' button should be shown using a Button control, or a DIV.
- 'Fetch More' control style
Specify the in-line style for the button or div tag for the 'Fetch More' control.
- 'Fetch More' container style
Specify the in-line style for the container row that contains the 'Fetch More' control. For example, to center the 'Fetch More' button, enter: text-align: center;
- Has Navigation Bar
Enables or disables the built-in List Control Navigation Bar. Available in a paginated List control using the "NavigationButtons" Pagination method.
- Navigation Bar settings
If enabled, the Navigation Bar settings are used to configure the List Control's Navigation Bar. The Navigation Bar can be shown either in the List's header, footer, or in a DIV in the UX Component.
- Server-side sorting
Enables server-side sorting for all List Columns.
There is a difference between Client-side and Server-side pagination. The data pagination done in the List Builder's Data Source tab is all server-side. Because you are connected to a server in order to obtain data; which will necessarily limit the number of records downloaded to the device at a given time. Thisalso means that you have to have an active connection in order to fetch the next batch of records. This makes it impossible to use server side pagination in a disconnected context. With the client-side equivalent of "pagination", i.e. "list virtualization", you basically download the entire data set but only render a small portion of it. The most expensive part of the list data is displaying it, not storing it, so using client side list virtualization actually allows you to have a huge number of records. However, you can just render a small portion of these records at a time of them. List virtualization for controls is defined on the List Properties tab in the List Builder.