Update a saved view

Updates an existing saved view configuration by modifying its name, grid column layout, filter settings, sort preferences, or timeline display options. This endpoint enables users to refine their saved workspace views as their needs evolve, such as adding new filter criteria, adjusting column widths, changing sort orders, or updating the view name. Only the view owner or users with manage permissions can update saved views. Use this endpoint when users need to persist changes to their customized workspace layouts, update filter combinations based on new requirements, or rename views for better organization. The request accepts partial updates allowing modification of specific properties without affecting unchanged settings. For example, call this when a user adjusts column widths in their 'Q4 Tasks' view and clicks save, or when renaming a view from 'My Tasks' to 'High Priority Tasks' without changing its filter configuration. The updated SavedView object is returned reflecting all current settings including both modified and unchanged properties.

Key Features:

  • Supports partial updates of saved view properties (name, grid state, filters, timeline settings)
  • Preserves unchanged properties automatically - only specified fields are modified
  • Updates apply immediately and persist across user sessions
  • Returns complete updated SavedView object for client-side state synchronization

Authorization Logic:

  • Requires manage permissions for the space (seismic.programs.manage)
  • Users can only update views they own or have explicit modification rights to
  • Attempting to update another user's private view returns 403 Forbidden

Usage Example:

When a user modifies their saved view by adding a new status filter and adjusting column order, capture the new gridFilterModel and gridState arrays, then call this endpoint with the updated configurations. The response confirms the changes and provides the complete updated view definition for your UI to reflect immediately.

Path Params
string
required
length between 7 and 22

The unique identifier of the space containing the target entity. This determines the scope of entity queries and ensures proper access control. The space must be accessible to the authenticated user with appropriate permissions. It can be the unique identifier (GUID) of the space or the word "default" to indicate the default programs space. Common values include "default" and "rkr83lapKkyCJuLLWqLqzB".

string
required

Unique identifier for the specific saved view to update. This is a stable string ID in base64url or GUID format (example sv7YtMp2kQxRvN9LmW4HzAg). Use this ID to target the exact saved view you want to modify with new name, grid state, filters, or timeline settings. The view must exist in the specified space and you must have modification permissions (owner or space admin). Required for all update operations on saved views.

Body Params

The saved view data

string

Human-readable display name for the saved view shown in UI dropdowns, menus, and view selectors. Should be concise yet descriptive, typically 2-20 words, helping users quickly identify and distinguish different saved workspace configurations. Use meaningful names that describe the view's purpose or filter criteria, such as 'High Priority Q1 Tasks', 'My Team Programs', or 'Overdue Requests'. When updating, choose names that reflect current filter combinations and column layouts to maintain clarity across team members using shared views. Example updated names 'Critical Priority Tasks - Updated' or 'Active Programs with Budget Over 100K'.

string
enum

Display format type defining how the saved view presents data in the UI. List format shows records in a traditional grid/table layout with columns and rows, enabling filtering, sorting, and column customization. Timeline format displays items on a Gantt-chart-style horizontal timeline based on date ranges, ideal for visualizing program schedules, task durations, and temporal relationships. Choose list for detailed record analysis with multiple attributes, or timeline for date-driven planning and schedule visualization. When updating type from list to timeline or vice versa, ensure gridState and timelineState are configured appropriately for the target display format.

Allowed:
gridState
array of objects | null

Array of grid column state configurations defining column visibility, ordering, widths, and pinning preferences for the saved view. Each GridState object represents one column's configuration including its unique column ID, display width in pixels, pinned position (left/right/none), hide/show state, and sort order within the grid. Use this to update how columns appear in the saved view, such as reordering columns, adjusting widths after user resizes, hiding irrelevant columns, or pinning important columns for visibility. Set to null to remove custom grid state and use default column layout. Example usage includes saving a user's preference to pin the task title column left, hide the description column, and set priority column width to 120 pixels.

gridState
string

Filter model object containing all active filter configurations for the saved view, following ag-Grid filter model structure. This complex object defines which columns have filters applied and their specific filter criteria (equals, contains, date ranges, etc.). The structure varies by filter type - text filters include filterType and filter value, number filters include type (equals/lessThan/greaterThan) and filter value, date filters include dateFrom/dateTo ranges. Use this to update saved filter combinations such as changing priority filter from High to Critical, adding status filters to show only In Progress tasks, or updating date range filters for current quarter. Set to null or empty object to remove all filters. Example shows filtering priority column to Critical value and assignee to specific user ID.

timelineState

Timeline view configuration object containing timeline-specific display settings including date range boundaries, zoom level (day/week/month/quarter), visible date columns, row height, and timeline-specific filters. This state object preserves how the Gantt-chart-style timeline view is configured, enabling consistent recreation of timeline layouts across sessions. Use this to update timeline view preferences such as changing the visible date range to focus on current quarter, adjusting zoom level for broader or more detailed time views, or modifying row heights for better readability. Set to null when updating list-type views that do not use timeline display. Only applicable when saved view type is timeline format. Example includes setting date range from January to March 2025 with week-level zoom and 40px row height.

Responses

Language
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json