August 2026 Release: Omnitable Resolved Issues

"All" Filter Option Now Available in Omnitable View Configuration

• Feature: Omnitable

• Level of Configuration: None

When creating a new Omnitable or ATS view that used a custom column renderer, users were unable to save the view without specifying filter criteria — there was no option to display all records. The view configuration in both Omnitable and ATS has been updated to allow saving a view without filter criteria, so all records are displayed by default regardless of the column renderer in use.

 

Omnitable Filter Crashes when Filtering on Created By ID

• Feature: Omnitable

• Level of Configuration: None

Applying a filter on the Created By ID field in an Omnitable caused a component error that prevented the table from loading filtered results. The Omnitable filter has been updated to correctly handle Lookup(User) fields. The filter now saves and applies successfully, and the current logged-in user is automatically presented as a value option when filtering on a User lookup field.

 

Columns and Filters Not Saved When Creating a New Omnitable View

• Feature: Omnitable

• Level of Configuration: None

Columns and filters configured during the initial save of a new Omnitable Named View were not persisted. The view fell back to the default fieldset, and the correct configuration only appeared after saving a second time. Column width preferences were also lost on first save. Columns, filters, and column widths are now correctly persisted the first time a new view is saved, and all users with access to the view see the correct configuration immediately.