DynamicGroups

A DynamicGroup is a reusable table or form with its own row source, displayed bindings, and per-UserType access. Choose an ObjectType directly; a query is optional. Optional record contexts let the same group show all permitted rows or narrow to a selected record. See Context, bindings, and views for the current builder.

Default row sorting

Configure Groups → Main → Default row sorting offers:

• Record ID (default): ascending ID order, preserving existing behavior. This generally follows creation time, but records created within the same second may not follow exact ingestion order.
• Specific column: ascending or descending by a displayed scalar column.
• Last updated (newest first): the primary record’s existing updatedAt timestamp, falling back to creation time for older records.

The setting applies across pages in Owner previews and Views, including Sheets and forms. It changes row order only; column positions and headers stay fixed. Ties use Record ID. Empty column values appear first ascending and last descending. If a role or View cannot read the chosen column, its rows fall back to Record ID order. Viewing a record does not update its timestamp, and editing a related record does not update the primary record’s timestamp.

Direct record columns and timestamps sort in the database. Related and calculated columns resolve authorized values before sorting, with a maximum of 1,000 source records and the existing relationship/time budgets. Exceeding a bound returns an error without partial results. Aggregate summaries retain their existing ordering.

Changing the Group definition invalidates existing page cursors; refresh before continuing.

Configure and open a Group

Owners open Admin Panel → Views, Groups & Sheets and configure a Group. Choose an ObjectType or saved query, displayed bindings, contexts, relationship paths, record operations and per-UserType permissions. Select Table, Form or Spreadsheet. See context and bindings for mixed-record configuration and Dynamic Sheets for spreadsheet behavior.

Group and View configuration is Owner-only. Owners can open standalone previews. Members open Groups through authorized DynamicView placements; legacy query-only Groups remain Owner previews until upgraded to contextual bindings and placed in a View. Empty UserType visibility leaves a Group Owner-only. Group permissions and View restrictions never expand underlying data grants.

Edit records

Table Groups use DataTables Editor inputs and one trailing Actions column. Choose Edit, then Save or Cancel. The trash control changes to Confirm Delete / Cancel. Creation uses an inline draft with schema defaults and validation. Controls appear only for permitted operations; read-only summaries and drill-downs remain read-only. Forms retain their record selector and form workflow. Sheets edit individual cells and autosave.

Owner previews and View placements use the same permission-aware renderer. Creation must satisfy the source/query constraints and required fields. Contextual creation writes one anchor record and requires explicit creation bindings; it does not create a graph of related records. Editing may remove a record from the saved query's results. Query-backed select/multiselect fields remain read-only pending live option validation.

Writes enforce schema, per-cell access, context/query restrictions and revisions. Reload after concurrent changes. Multi-binding saves may partially succeed; errors identify earlier saved changes. Removing role access takes effect on subsequent requests.

Search and column filters

Record search runs across the authorized dataset before pagination. Configure an optional Search placeholder; blank uses “Search all available records”. Allow column filtering adds funnel controls to readable columns in table and Sheet displays.

Each column supports up to three type-aware conditions joined by All (AND) or Any (OR). Different columns combine with AND and intersect search text. Apply saves the filter, Clear removes it and Cancel preserves the previous filter. Active filters use a filled funnel icon. Empty conditions match missing values; other comparisons exclude them.

Views inherit filtering or disable it; they cannot enable what the Group prohibits. Related/calculated fields retain their read permissions and execution limits. Summary results do not support search or column filters, including via direct API requests. Separate page-local filtering, where offered, only filters loaded rows.

Custom buttons and actions

Custom Group buttons provide navigation, DynamicActions and browser redirects. Views inherit buttons and may hide, narrow or reposition them. Owners configure reusable actions at Admin Panel → Dynamic Actions. Actions create one record with up to four connections or update one existing record; conditions, duplicate checks, explicit grants, revisions and idempotency remain enforced.

Boundaries

Groups support bounded relationship access and calculated display values, not arbitrary code or unrestricted traversal. Bulk/multi-record creation, automatic action triggers and external API execution remain planned. Referenced queries, fields and destinations are protected from incompatible changes.