Table component
Add a Table component to a page to show records in rows and columns.
Use a Table component to show records in rows and columns on a page when users need to scan several records at once.
Before you add a Table component, make sure your table has:
Clear field labels so columns are easy to scan
The fields users need for quick decisions
Fields to filter the records if the page should show only relevant ones
Add a Table component to a page
Open the Add tab
In the Settings panel, open Add.
Add Table
Under Views, drag Table onto the page.
Label the component
Ninox generates the Label and Internal name automatically. You can update both values if needed.
Configure the Table component manually
Under Behavior:
Keep Constant selected as the data point option.
Choose the source Table.
Select the fields to show using hidden columns.
Filter or Group if you want to show only a selection of rows.
Review the result
Check whether the expected records and columns appear. Then drag the component to move it on the page. Use the resize handles to adjust its size.
Table component settings
In On the form, you can define the basic component details:
Label for the title shown on the component
Internal name is filled automatically. Change it only if needed and carefully. When you script, you use Internal name, not Label.
Under Behavior, configure how the table works on the page:
Data point to set up data retrieval. Use Constant to configure it with controls, or Logic to use Ninox Script. If Data point is set to Constant:
Table to choose the source table
Filter to limit which records users can see with one or more conditions
hidden columns to control which fields Ninox shows, search for fields, and use Hide all or Show all
Group to group records by one displayed text, date, status, linked-record, or location field
Show title to show or hide the component Label.
Show search field to show a search field at the top of the table
Show add record button to show a button that lets users add new records
Quick add at the bottom to show a blank row at the bottom of the table for quick entry
Multi-select and bulk actions to let users select multiple records and perform bulk actions
Inline editing to let users edit records directly in the table If Data point is set to Logic:
Logic to add the Ninox Script that retrieves the data. In this case, Ninox expects the values and optional layout setting as a JSON-like object with key-value pairs in curly braces {...}. Required identifiers in
dataare:idof the record to displaytableIdbuilt withtableId(...)cellscontaining key-value pairs, such as{name: "Kim"}
Required
settingsidentifier:columnsfor explicit column order as plain strings.
Without
settings.columns, order falls back to the first-seencellskeys across all rows.See the example below.
Under Visibility, choose how the component is shown on the page:
Visible: shows the component on the page.
Hidden: hides the component on the page.
Conditional: defines a Visibility condition that controls when the component is shown or hidden.
Use Conditional when the component should appear only in specific cases.
Build the condition based on user roles, Tables, or Fields.
This only affects what is shown on the page. It does not change records or permissions.
Let's take a look at an Example
When you use Logic data retrieval, structure the script like this:
Use this prompt to create the script with Ninox AI: "Create a script for the Table component that displays records from the Employees table. Show these columns: Name, Project, Initials, and Has Photo."
Last updated
Was this helpful?