Skip to main content

Saved grid views

Any data grid — a screen's table or an ad-hoc Table View — can remember how you set it up. A view captures the grid's full presentation and lets you switch back to it in one click:

  • which columns are visible, and their order;
  • the sort;
  • the per-column filters;
  • the grouping;
  • the page size.

At a glance​

CustomersTableChartSummaryViews ▾Columns ▾Export ▾+ AddSHAREDStandarddefaultMonth-endMY VIEWSMy French customers🗑Save as…SaveResetNAMECOUNTRYSTATUSUPDATEDACME IndustriesFRActive27/10/2026Beta SARLFRActive25/10/2026Gamma SABEProspect12/10/2026Views menushared and personalPersonal viewsfollow the user everywhereSummarycounts per group, server-sideThe gridcolumns, sort, filters saved

Your views vs shared views​

The Views menu on the grid toolbar lists two groups:

  • Shared — published, read-only views available to everyone on that screen. An admin authors them in the Screen Designer's Views tab, and may mark one as the default — the layout the grid opens with.
  • My views — the views you save yourself. They are stored per user on the server, so they follow you across devices and sessions. You can have as many as you like per grid.

A regular user reads shared views and manages their own; publishing a view for everyone is an admin action in the Designer.

Working with views​

ActionWhat it does
Save as…Names the current columns, sort, filters and grouping as a new personal view. Reusing a name overwrites that view.
SaveOverwrites the active personal view in place (shown only when the active view is one of yours).
Select a viewApplies a shared or personal view.
Delete viewRemoves one of your own views (the trash icon).
Reset to shippedIn the Views menu: back to the layout the screen ships with — its default shared view, else its base layout.
ResetReverts to the screen's default shared view, or to its base column layout if there is none. Handy when an older saved state conflicts with a column that is now conditionally hidden. Reset lives in the Columns menu.

The grid also remembers, per device, the last view you opened on each table — so you land back where you left off — while the views themselves live on the server.

Summary view​

The Summary view is set on the screen, not saved by the user: when the screen editor's Summary tab lists grouping columns, the grid gains a Summary button next to Table and Chart.

In that mode the grid shows one parent row per combination of the grouping columns, with the number of rows behind it (the count column's header is set in the same tab). The count is computed by the database over the whole result, so it stays exact even when the grid caps the rows it loads. A chevron on each parent row loads its detail rows — the screen's own query, narrowed to that group — only when it is opened.

A date or timestamp grouping column can be bucketed by day, month or year: the parent row then shows the period, and the detail rows are the records that fall into it.

Day-grain filter on timestamp columns​

Filtering a timestamp column doesn't force you to type a full YYYY-MM-DD HH:MM:SS bound. The column-header filter lets you pick a day and matches every row whose timestamp falls on that day (server-side lower / upper bound).

Tips & best practices​

  • Save the layouts you reuse. A "month-end" view with the right columns, filter and sort is one click away every time.
  • Publish the team's standard as a shared default. Author it once in the Designer's Views tab and mark it default, so everyone opens the grid on the agreed layout.
  • Reach for Reset when a grid looks wrong after an upgrade. If a column became conditionally hidden, an old saved state can fight the new rule — Reset clears it back to the screen's default.