You are here:
Considerations for Using Criteria-Based Search and Filter
Review these considerations before you implement and use Criteria-Based Search and Filter.
Required Editions
| Available in: Lightning Experience |
| Available in: Automotive Cloud, Consumer Goods, Health Cloud, Manufacturing Cloud, Nonprofit Cloud, Nonprofit Cloud for Grantmaking, and Public Sector Solutions. View edition availability. View edition availability. |
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.
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 MapsTM 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
| Configuration | Supported Field Types |
|---|---|
| Search Criteria |
|
| Search Results Display | For a list view:
For a card view: Field types supported by OmniStudio FlexCards |
| Search Results Grouping and Aggregation |
|
| Search Results Filter Fields |
|
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.
この記事で問題は解決されましたか?
ご意見をお待ちしております。

