Considerations for Using Criteria-Based Search and Filter

General Considerations

• When you create criteria field mappings and result field mappings for a searchable object configuration, the mappings are applied to all configurations that use the same searchable object. If you delete the mappings for one configuration record, the mappings are deleted for all other searchable object configurations using the same object.
• The search results panel shows up to 2,000 records. If a search generates more results, only 2,000 records are shown. If you apply aggregation or filter criteria, only the 2,000 records in the results panel are filtered to match the criteria.
• In search criteria configurations that use grouping and aggregation, you can view up to 20 groups in the search results.
• Deleting records in a source object can affect the searchable object. If a record is missing in the source object, the searchable object record is either deleted or the impacted field is set to empty during the next sync job.
• To make custom objects searchable, select the Allow Search option in the Search Status section when you create a custom object in Setup.
• When using the Criteria-Based Search and Filter Intake component in Screen Flows:
  • The Selected Record IDs output is a JSON-encoded string containing an array of record IDs. Store it in a Text flow variable, then parse it (for example, via an Apex action) into a collection for downstream use.
  • The Maximum Selection property warns users when selections exceed the cap but doesn't prevent selection until they attempt to advance to the next screen.
  • The Search Context JSON must use exact field API names from your Search Configuration. Mismatched field names will be ignored.
  • Read-only fields defined in Search Context prevent users from modifying those filter values during the flow screen interaction.

Bulk Selection Considerations

• The Select All feature allows you to select up to 2,000 records at once for bulk actions. If your search returns more than 2,000 records, only the first 2,000 are included in the selection.
• When Maximum Selection is configured in a Screen Flow context, the "Select all across pages" functionality is automatically disabled. Users can only select up to the configured maximum.
• Selection state persists across pagination. When you load additional pages after selecting all records, newly loaded records are automatically included in the selection.
• The results header, next to the search results count, shows a live count of selected records (for example, "2000 selected"). This count updates immediately when you manually deselect individual records after using Select All.
• When a flow or OmniScript action opens in a new browser tab, selected record IDs are passed using session storage instead of the URL, regardless of selection size.

Location-Based Considerations

• Manually edit the field-level security for the Location object for the System Administrator and the Analytics Integration user profiles, and enable Read access on the fields Location and Parent Location.
• The Relative Location field shows a city name, but you can also search by street name, state or province, or any other address attribute that Google Maps^TM can use to extract information.
• Location fields can result in a numeric overflow during recipe ingestion and in computations when you run a Data Processing Engine definition to transform data in the searchable object. To resolve the issue, you must adjust the numeric field’s precision or scale to accommodate the numeric value. Reduce the Scale value for all location-based measures in source objects and in the searchable object in Data Manager for the connection you’re using.

Supported Fields and Field Types

When selecting a search criteria field, select text-indexed fields that can yield only up to 4,000 records when used in a combination.

Composite, formula, and encrypted fields aren’t supported for search.