Overview
Filtering complex objects in report columns requires a different approach than using traditional "contains" queries. For example, in Audit reports, fields like the “Target” column are considered complex objects. These fields cannot be filtered using partial matches or substring searches due to performance considerations. Instead, they require exact matches or searches by token.
Why exact matches are required
Complex fields often store data as objects with unique identifiers or structured information rather than simple text. Filtering these fields efficiently necessitates precise search criteria. Attempting a "contains" search would significantly degrade performance, so only exact and token-based matches are supported.
Examples
Example 1: Filtering by object ID
Suppose you want to filter a complex field such as the target field, which uses a key-value pair (e.g., _id: value). To filter by ID, enter the complete ID value in the search field—partial or substring matches will not return results.
If the ID is 5f09333a-842c-47da-a157-57da27fcbca5, you must enter the entire string to find a match.
Example 2: Filtering by token
The system segments complex identifiers into tokens behind the scenes. For instance, the ID 5f09333a-842c-47da-a157-57da27fcbca5 might be broken into tokens such as 5f09333a, 842c, 47da, etc.
To search by token, enter the complete token in the search field:
If you remove even a single character from the token, the search will fail to find a match, since only exact matches are recognized:
Example 3: Filtering by email address
When searching complex fields such as email addresses, the full email address must be entered.
Partial entries will not yield results; for example, if you omit even the last letter or forget the .com suffix, the filter will not work.
However, because of the token segmentation, entering just the name.surname (so the part of the email before the domain) will still produce search results:
Summary
- Complex report columns require exact matches, not partial or substring searches.
- Use the full identifier or a complete token for successful filtering.
- Partial entries, even by a single character, will not match and return results.
By following these guidelines, you can efficiently filter complex objects in your reports and obtain accurate results.