Mini Widgets
Pagination
arcCustomPagination

With arcCustomPagination
, content can be elegantly displayed page by page – especially with long lists or tables, it is a real game changer in terms of performance and clarity. Instead of loading all records at once, only the currently visible entries are displayed. This saves loading time and makes your interface much smoother.
When should one use pagination?
Pagination is especially recommended when:
a list contains many entries (e.g., messages, projects, clients),
rendering becomes slow due to too many simultaneously loaded elements,
better user guidance through page numbers is desired,
you want to optimize UI/UX, e.g., for mobile devices.
Example of paginated list
Before you paginate your list, you first need to define the Ninox list itself. With this loop, only the corresponding section from the entire list is loaded – depending on the current page number:
Application code for the widget
You insert this application code at the place where you want the pagination to be displayed.
Parameters
Parameter | Type | Description |
---|---|---|
| Text | Unique ID for the pagination element. Required field. |
| Boolean | Allows manual entry of the page number in the input field. |
| Text | ID of the current record to which the update applies. (The action is executed) |
| Text | The field that stores the current page. |
| Text | Layout of the pagination: |
| Text | The currently displayed value in the input field. |
| Number | Current page number – important for navigation and button conditions. |
| Number | Total number of pages (e.g., |
| Text | Small addition before the total number of pages, e.g., |
| Text | Optional string that is placed before the page number on update. |
| Widget | Optional content (text or widget) for the “first page” button. |
| Widget | Optional content (text or widget) for the “back” button. |
| Widget | Optional content (text or widget) for the “next” button. |
| Widget | Optional content (text or widget) for the “last page” button. |
Structure in a Custom Table
Application Code Complex
💡 Pro Tip: If you want to display multiple lists on one page, you can create your own pagination with different uniqueId
values and your own fieldId
fields for each list. This keeps everything independent.
Conclusion
arcCustomPagination
is perfect for elegantly, performantly, and user-friendly presenting large amounts of data. A must for anyone working with long lists – whether in CRM, projects, or support tickets.
Let’s paginate smart. 🚀