Table (Grid View)

Turn a nestable data table into an interactive Grid.js view with optional search, sortable columns, resizable columns, and client-side pagination. The input table is still authored in Bricks.

Setup and First Use


Before starting, enable the relevant element or feature family under Bricks → BricksUltimate → General Elements, save, and reopen the Bricks editor. Integrations also require their corresponding plugin to be active.

  1. Add (BU)Table (Grid View) and inspect its generated header and body structure.
  2. Use Show raw table in the editor while editing the source cells and rows. Keep the same number of cells in each row.
  3. Replace sample values with your data, or configure a limited body-row query where appropriate.
  4. Enable Sortable columns and Resizable columns if the data benefits from them.
  5. Enable search and/or pagination and configure labels, row count, and buttons.
  6. Disable raw editing preview when you want to inspect the enhanced view, then test the real frontend.

Controls and Settings


ControlPurpose and usage
Show raw table in the editorAn editing aid for the underlying table. It is not a separate public data source.
Hide the bottom buttonsHides builder-only editing controls, not the frontend pagination feature.
Disable text wrapCan make dense tables wider. Use carefully and test horizontal scrolling on mobile.
Fixed headerThe control description requires a height under Style → Layout. Use this only for a deliberately constrained scrollable table.
Sortable / Resizable columnsEnable the respective Grid.js interactions and style hover/focus header states.
PaginationSet Rows per page, previous/next controls, summary visibility, button count, labels, and state styling.
Search Form / l10NSet search appearance and placeholder, no-record/error messages, and localized pagination text.

Client-side Pagination Is Not Database Pagination


Grid.js enhances the table rendered into the page. Search, sort, and page controls operate on those available rows; they do not automatically search an entire database or fetch private records securely. Keep datasets modest and do not mistake five visible rows for a five-row server query.

Dynamic Content and Column Meaning


Use consistent column values and test sorting numbers, dates, formatted currency, and HTML rather than assuming every display format sorts as its underlying value. If a query returns only one server page, the client-side search covers only that rendered subset. Avoid combining two pagination systems without an intentional design.

Practical Example


Create a staff directory with Name, Department, and Office columns. Render a modest public dataset, enable search and sorting, and paginate at ten rows per page. Test no matches and the final page.

Troubleshooting


  • Search misses a known record: confirm that record was actually rendered into the source table.
  • Header/cells mismatch: correct the raw table structure.
  • Fixed header fails: set a suitable scrollable layout height as instructed by the control.
  • AJAX popup displays raw content: verify Grid.js initialization after content injection.

Related Documentation