Overview
The View Editor is used to create and configure the views that display application records. Shared settings control how a view opens, how users search and filter its records, which export methods are available, who can see the view, and what happens when a record row is selected.
The editor contains Settings and Filters tabs, a view-specific middle tab, and—when enabled by a platform administrator—an Anonymous tab. Current view types include Table, Cards, Calendar, and Kanban. The middle tab changes according to the selected view type.
For the purpose and structure of each view type, see Views Overview.
Shared and View-Specific Tabs
| Field or option | Description |
|---|---|
| Settings | Shared view name, record-opening, preview, editing, pagination, formatting, defaults, and Record Linking controls. Available options vary by view type. |
| View-specific middle tab | Table Columns, Card configuration, Calendar configuration, or Kanban configuration. |
| Filters | Sorting, grouping, Search Fields, Dynamic Table Search Fields, filtering, exports, and view security. Calendar Views do not use the same default sorting and grouping controls as Table and Kanban Views. |
| Anonymous | Anonymous-view settings. This tab appears only when Anonymous Access has been enabled by a platform administrator. |

Settings Tab
The Settings tab contains general controls for the view. Not every control appears for every view type; configure and test the options that are present in the selected view.
View Name and Description
| Field or option | Description |
|---|---|
| View Name | The name shown at the top of the view and in application navigation. Keep it descriptive and reasonably short. |
| Description | An optional internal description that explains the view’s purpose to designers. |
Preview Pane
Preview Pane opens a selected record beside the view instead of replacing the view. Designers choose the pane width and whether the record initially opens in View or Edit mode.
| Field or option | Description |
|---|---|
| Preview Pane | Enables or disables the pane. |
| Width | Sets the portion of the available view area used by the pane, such as 75%, 50%, or 25%. |
| Hide Status | Hides the record’s displayed workflow status at the top of the preview pane. |
| Enable Create | Allows the New control to open record creation in the Preview Pane. |
| Mode | Sets whether existing records initially open in View or Edit mode inside the pane. |

Editable Cells
Edit Cells in Table allows supported displayed fields to be edited directly from a Table View. Fields that are not displayed, unsupported field types, or protected fields still require the record form.
Permissions: Direct editing respects form, workflow-stage, field, and role permissions. Enabling the view control does not override those security rules.
Action Column
Show Action Column displays the workflow actions available for each record at the right side of a supported view. The visible actions depend on the record’s current stage and the user’s permissions.
Record Copy
Hide Record Copy removes the view-level Copy Record option. This is separate from the form-level control that removes copying while viewing or editing the record itself.

For the form-level setting, see Form Editor: Settings Tab.
Pagination
| Field or option | Description |
|---|---|
| Infinite Scrolling | Uses a Load More pattern instead of standard pages. Grouped views may use this behavior by default. |
| Default Page Size | Sets how many records are shown when the view opens. Users can change the current page size when paging controls are available. |

Formatting
| Field or option | Description |
|---|---|
| Display Density | Controls row spacing and, for Compact mode, the amount of information that fits on screen. |
| Header Color | Sets the view header color. |
| Footer Color | Sets the view footer color where applicable. |
| Alternating Row Colors | Uses two alternating colors to make Table View rows easier to follow. |

Override Form Defaults
Override Form Defaults supplies view-specific initial values when users create records from the view. Each field map identifies a Target Field and the default rule to apply. For example, supported date fields, Relative options can use Days, Months, and Years offsets. Records created directly from the form continue to use the form’s normal defaults.

Record Linking
Record Linking is the permanent row-navigation configuration for supported record views. It determines whether selecting a record row opens the record, where it opens, and whether the record initially uses View or Edit mode.
| Field or option | Description |
|---|---|
| Open record on Row click | When enabled, selecting a record row starts the configured record-opening behavior. |
| Action — Open record | Opens the record in the current view context. If Preview Pane is enabled, test the combined behavior to confirm where the record is presented. |
| Action — Open record in another tab | Opens the selected record in a separate browser tab when that option is available. |
| Mode — View | Opens the record in view mode. |
| Mode — Edit | Requests edit mode. The user must still have permission to edit the record and fields. |
The current Pagination and Record Linking controls are shown together in Figure 3.
Configure Record Linking
- Open the required view in the View Editor and select Settings.
- Locate Record Linking.
- Enable Open record on Row click when the full record should open after a row is selected.
- Select Open record or Open record in another tab from Action, according to the navigation required for the view.
- Select View or Edit under Mode.
- Save the view.
- Launch the application and test a normal row, a workflow-action control, and any editable cell or Preview Pane behavior used by the view.
- Repeat the test with a user who has view-only access and a user who has edit access.
Supported interaction: Row linking controls record navigation; they do not bypass record, workflow, form, or field permissions. In views with editable cells, action buttons, selection checkboxes, or a Preview Pane, test each interactive area so users do not trigger an unintended row-navigation action.
Filters Tab
The Filters tab controls the default record order and grouping where supported, the fields searched by the launched search box, fixed and user-editable filters, export availability, and view visibility.
Default Sorting and Grouping
| Field or option | Description |
|---|---|
| Default View Sorting | Sets the initial record order using one or more fields and ascending or descending direction. |
| Default View Grouping | Groups records by selected fields and can control sort order, highlight color, labels, counts, and whether the grouped field remains visible as a regular column. |
| View-type availability | Table and Kanban Views support the documented defaults. Calendar Views use Calendar-specific ordering and do not present the same sorting and grouping sections. |
Search Fields
Search Fields controls which ordinary form fields the launched view search evaluates. Leaving the list empty uses the view’s default searchable record fields. Adding fields limits searching to the configured set and provides field-specific comparison behavior where available.
| Field or option | Description |
|---|---|
| Exact Match | The field value must equal the search input. |
| Starts With | The field value must begin with the search input. |
| Ends With | The field value must end with the search input. |
| Contains | The search input can appear within the field value. |

Dynamic Table Search Fields
By default, the launched view search ignores values stored inside Dynamic Table fields. Dynamic Table Search Fields lets the designer select the table fields whose contents should participate in view search.
- Open the view’s Filters tab.
- Locate Dynamic Table Search Fields.
- Search for and select each Dynamic Table field that users need to search.
- Remove fields that should no longer participate in search.
- Save the view and launch it.
- Search for a value that exists only inside a selected Dynamic Table and confirm that the parent record is returned.
- Search for a value inside a non-selected Dynamic Table and confirm that the default exclusion remains in effect.

| Field or option | Description |
|---|---|
| No Dynamic Table fields selected | Search ignores data stored in Dynamic Tables. |
| One or more fields selected | Values in the selected Dynamic Table fields are added to the view’s searchable scope. |
| Record result | A matching Dynamic Table value returns the parent record in the view, subject to the view’s filters and the user’s access. |
| Interaction with ordinary Search Fields | Ordinary fields and Dynamic Table fields are configured in separate sections. Test representative queries when both are used. |
Dynamic Table Search Performance
- Select only the Dynamic Table fields users genuinely need to search.
- Expect broader search scope to require more work than searching only ordinary record fields, especially when records contain many Dynamic Table rows.
- Test with representative record counts, Dynamic Table row counts, and typical search terms before publishing the view.
- Use view filters to keep the result set appropriate for the user’s task, but do not treat filtering as a replacement for permissions.
- Review performance again after large data imports or substantial growth in the number of records or Dynamic Table rows.
- Avoid documenting fixed performance limits unless Product or Engineering has supplied and validated them for the current release.
Filtering
| Field or option | Description |
|---|---|
| Add a new Filter | Adds an AND condition. Records must satisfy the required AND conditions to remain visible. |
| Add OR Filter | Adds a grouped OR condition. A record can satisfy any condition within the OR group. |
| Field | The field evaluated by the condition. Available fields depend on the field type and feature support. |
| Operator | The comparison used for the selected field. Operators are context-sensitive to the field type. |
| Value | The fixed value, relative date, selected stage, or other comparison input required by the chosen operator. |
| Uneditable | Prevents application users from removing the designer’s filter. Users can still apply additional filters when the interface and permissions allow. |
Exports
The designer controls which export methods are available from the view. Users see only the export methods enabled for that view and must still have access to the records and fields included in the export.

See Export Records to CSV or Google Sheets for spreadsheet exports and optional View and Edit record links, and Export Records from a View to PDF for PDF output.
Security
| Field or option | Description |
|---|---|
| Everyone in the App | Makes the view available to application users who otherwise have access to the application and its records. |
| Custom Roles | Limits view visibility to selected application roles. If no role is selected, users will not have role-based access to the view. |

Current In-View Controls
After the application is launched, the visible controls depend on the view type, the view design, and the user’s permissions. Current view experiences can include:
| Field or option | Description |
|---|---|
| Search | Searches the ordinary and Dynamic Table fields configured in the View Editor. |
| View Filters | Opens user filters together with available AND/OR conditions. Current interfaces can include Clear All, Column Sorting, and Column Grouping. |
| Export to | Opens the export methods enabled for the view. |
| Settings | Opens supported view settings in a side panel for authorized users. |
| Edit View | Opens the current view in the View Editor for an authorized designer. |
| Edit Form | Opens the source form in the Form Editor for an authorized designer. |
| Save | Saves permitted in-view design changes to the current view. |
| Save View as | Creates another view from the current configured state when the user is authorized to create views. |
| Record row | Uses the configured Record Linking, Preview Pane, or other supported record-opening behavior. |
Security: Filters limit what a view displays; they do not grant or replace record-level, workflow-stage, field, or role permissions.

Permissions and Supported Behavior
- Seeing a view does not automatically grant access to every record or field referenced by the view.
- View mode requires permission to open the record; Edit mode also requires permission to edit the record and relevant fields at its current workflow stage.
- Edit Cells in Table, the Action Column, and row-click navigation continue to respect form, role, workflow-stage, field, and record security.
- Edit View, Edit Form, Save, and Save View as should be available only to users with the corresponding design or administration authority.
- Exports include only the data available through the enabled method and the caller’s effective access. Review exported files before sharing them outside the authorized audience.
- Dynamic Table Search Fields changes what search evaluates; it does not make restricted records or fields visible.
- Anonymous View behavior is controlled separately and must be security-reviewed before public use.
Troubleshooting
| Field or option | Description |
|---|---|
| Dynamic Table data is not found | Confirm the correct Dynamic Table field is selected, save the view, and test a value stored in that field. |
| Search becomes slow | Reduce unnecessary searchable Dynamic Table fields, test with representative data volume, and review broad filters or unusually large Dynamic Tables. |
| A row does not open | Confirm Open record on Row click, Action, Mode, record access, and any interaction with Preview Pane or editable cells. |
| Edit mode opens as view-only | The user may not have permission to edit the record or fields at the current workflow stage. |
| Record opens in the wrong place | Review Record Linking Action together with Preview Pane configuration, save, and test again. |
| Designer controls are missing | Confirm the user is an App Designer or has the authority required to edit the view or source form. |
| An export option is missing | Confirm the method is enabled for the view and use the dedicated export article for its prerequisites. |
| A user cannot see the view | Review Everyone in the App, Custom Roles, application access, and—if relevant—Anonymous Access. |
Continue with View Editor: Table Views, View Editor: Calendar Views, or View Editor: Kanban Views for settings unique to those view types. Link the Card Views article here after it is published.