DenchClaw Saved Views: The Fastest Way to Filter Your Data

How DenchClaw saved views let you create named filters and instantly switch between different perspectives of your CRM data.

Mark Rachapoom

March 26, 2026·6 min read

DenchClaw Saved Views: The Fastest Way to Filter Your Data

DenchClaw saved views let you define a named filter, sort, and display configuration for any object and return to it instantly. Instead of re-typing "show me leads in New York sorted by last contacted" every time you want that perspective, you save it once as "NYC Leads" and it's always one click away.

Saved views are stored in your .object.yaml file — they're not locked in a database, they're readable YAML on your filesystem. Here's how they work and how to get the most from them.

What a Saved View Contains#

A saved view is a named configuration that specifies:

View type — table, kanban, calendar, timeline, gallery, or list
Filters — which entries to show
Sort order — how entries are sorted
Active columns — which fields are visible in table view
Kanban field — which enum field to use for kanban columns

All of this is stored in the views: section of your .object.yaml:

views:
  - name: NYC Leads
    type: table
    filters:
      - field: City
        operator: equals
        value: New York
      - field: Status
        operator: equals
        value: Lead
    sort:
      field: Last Contacted
      direction: asc
    columns:
      - Full Name
      - Company
      - City
      - Last Contacted
      - Status
 
  - name: Closing This Month
    type: kanban
    filters:
      - field: Close Date
        operator: this_month
    sort:
      field: Close Date
      direction: asc
 
  - name: Pipeline Overview
    type: kanban
    kanbanField: Stage

Creating Saved Views#

Method 1: Ask DenchClaw#

The fastest way to create a view:

"Save a view called 'Hot Leads' that shows all leads with Priority = High, sorted by last contacted date."

DenchClaw writes the view configuration to your .object.yaml and the view appears immediately in your object's view selector.

"Create a calendar view for Deals called 'Closing Calendar' that shows close dates."

"Save the current filter as a view called 'This Week's Follow-ups'."

Method 2: Edit `.object.yaml` Directly#

For power users who prefer direct YAML editing:

Open ~/.openclaw-dench/workspace/crm/OBJECT_NAME/.object.yaml
Add your view definition to the views: array
Save the file — DenchClaw hot-reloads the configuration

Method 3: Use the UI#

In the DenchClaw frontend, apply filters using the filter panel, then click "Save as view" in the view configuration dropdown. Name it and confirm.

Filter Operators#

DenchClaw's filter system supports these operators by field type:

Text and enum fields:

equals / not_equals
contains / not_contains
starts_with
is_empty / is_not_empty

Number fields:

equals / not_equals
greater_than / less_than
greater_than_or_equal / less_than_or_equal
between
is_empty / is_not_empty

Date fields:

equals (specific date)
before / after
between
today / yesterday
this_week / last_week / next_week
this_month / last_month / next_month
this_quarter / last_quarter
this_year
in_the_past (combined with number: in_the_past 30 days)
in_the_future
is_empty / is_not_empty

Tags fields:

contains — entry has this tag
contains_all — entry has all of these tags
contains_any — entry has at least one of these tags
not_contains

Boolean fields:

is_true / is_false

Multi-Condition Filters#

Combine multiple filters with AND/OR logic:

filters:
  operator: AND    # All conditions must match
  conditions:
    - field: Status
      operator: equals
      value: Active
    - field: City
      operator: equals
      value: San Francisco
    - field: Last Contacted
      operator: in_the_past
      value: 30 days

OR logic:

filters:
  operator: OR    # Any condition matches
  conditions:
    - field: Priority
      operator: equals
      value: High
    - field: Close Date
      operator: this_week

Nested logic (AND within OR):

filters:
  operator: OR
  conditions:
    - operator: AND
      conditions:
        - field: Status
          operator: equals
          value: Lead
        - field: Score
          operator: greater_than
          value: 80
    - field: Priority
      operator: equals
      value: Critical

The Default View#

Set the default_view field in your .object.yaml to determine which view loads when you navigate to an object:

default_view: Pipeline Overview

Or ask DenchClaw: "Set the default view for Deals to 'Pipeline Overview'."

View Switching#

Switch between views using the view selector at the top of the object page in the frontend. All saved views appear in the dropdown. The currently active view is highlighted.

When the AI creates or applies a view in response to a natural language query, it sets that view as active automatically. The frontend updates instantly — no page reload.