Dynamic Filter

Apply Dynamic Filter for Wave Embedded

Dynamic Filters allow you to filter grid data at runtime using values passed from the surrounding context such as a Flow, component, or configuration instead of fixed (static) filter values.

They are especially useful when the filter value needs to change based on:

  • The current record

  • User input

  • Flow variables or component parameters

Availability Dynamic Filters are supported only in Wave Embedded.


How Dynamic Filter Work

Unlike standard filters where you manually enter values, Dynamic Filters:

  • Receive values dynamically at runtime

  • Apply those values directly to the Salesforce query

  • Do not behave like standard Salesforce UI filters

Because of this, some UI behaviors differ from regular filters.


Supported Input and Format Rules

Dynamic Filters work only with supported formats and syntax. Using unsupported formats may cause the filter to fail or behave unexpectedly.

Date Fields

  • Date values must be provided in UTC format

  • Supported format: YYYY-MM-DD

❌ Other date formats are not supported.


Runtime UI Behavior (What You’ll See)

Dynamic Filters do not render like standard Salesforce filters.

UI Differences to Note

  • IN operator

    • Values are applied, but value “chips” are not displayed

  • Date fields

    • No date picker is shown

  • Displayed values

    • The grid shows the actual values used in the Salesforce query, not a formatted or user-friendly version

This is expected behavior and does not affect the results.


DateTime Fields

  • Users can provide DateTime values in their local timezone

  • At runtime:

    • The value is converted and stored in UTC

    • The displayed value also appears in UTC DateTime format


Case Sensitivity (Very Important)

Dynamic Filter variable names are case-sensitive.

When passing values from:

  • Flows

  • Components

  • Configurations

✔ The variable name must match exactly (including uppercase and lowercase letters). ❌ Any mismatch will cause the filter to fail.


Reference and Lookup Field Behavior

Filters on Reference Lookup Fields

  • Only record IDs are supported as input values

Filters on Lookup Name Fields

You may provide:

  • All record IDs or

  • All lookup names

triangle-exclamation

App Page Limitations

Dynamic Filters on App Pages do not support the $record. syntax.

This means:

  • Record-specific values cannot be resolved dynamically on App Pages

  • $record.FieldName works in supported contexts (such as Embedded scenarios), but not on App Pages


Using Dynamic Filters in Flows

When configuring Dynamic Filters in a Flow:

  • Follow the supported syntax exactly

  • Avoid extra spaces or unsupported characters

Incorrect formatting may cause:

  • Filters not to apply

  • Incorrect or empty results


Filter Syntax Rules

Basic Format

Each filter condition must follow this structure:

Multiple Conditions

  • Use a semicolon (;) to separate filter conditions

  • Use a comma (,) to separate multiple values within one condition

Spacing Rules

  • Spaces are not supported

  • Avoid leading or trailing spaces in values or separators


Example

What This Does

  • Name filter Shows records where the Name is Maria, Bella, or Andy

  • Stage filter Shows records where the Stage is Closed Won or Closed Lost

  • The semicolon (;) separates each filter condition


App Page Dynamic Filter Configuration Examples

Dynamic Value Assignment

Use values from the current record:

Static Value Assignment

Use fixed values:


Key Things to Remember

  • Dynamic Filters are evaluated at runtime

  • Date and DateTime values must use UTC

  • Variable names are case-sensitive

  • Do not mix record IDs and lookup names in the same filter

  • UI behavior may differ from standard Salesforce filters

  • App Pages have limited Dynamic Filter support

Last updated

Was this helpful?