Advanced search

Advanced search is used to run a full-text search in the database. Properties to be included in the search must be enabled for advanced search in the data model.

Tier requirement

Access to advanced search is dependent on your solution's subscription tier.

Usage

This action node can be used when large amounts of data in the database should be searchable by the user, but only need to be retrieved on demand. This approach reduces the need for reading data to the client, which can improve the application's performance. An example can be a library of articles or case files that the user only needs access to on demand.

See How to configure advanced search for a step-by-step guide on how to set up advanced search in an app.

Properties

Property	Description
Data Source	Select the data source you want to populate with the search results. Must be a runtime-only data source.
Search Score	Every object returned by Advanced Search is assigned a score based on relevance. Select a property on the selected Data Source to store this score. Must be of type float. Many factors can influence an object's score, including: - The position of the search term in the object - The frequency of occurrence of the search term in the object - The type of operator the query uses - The type of analyzer the query uses
Filter	Define the filter to apply to the results.
Search Type	Text: perform textual analyzed search. Corresponds to the contains any string operator. Autocomplete: perform a search-as-you-type query from an incomplete input string. Equals: search for an exact match. This works for string, integer or float properties.
Search in Properties	Choose which object class properties to search in. Only properties enabled for advanced search in the data model will be listed.
Sorting	Add sorting rules. The objects will be sorted before they are read into the data source.
Search Term	Define the term to search for in the database. This will typically be an App Variable containing the search string.
Limit Result	Limit the maximum number of objects returned in the search.
Match Criteria	Available when for Search Type Text only. Select criteria to use to match the search term. The criteria can be one of the following: - any: return entries that match any of the words in the search term. - all: return entries that contain all of the words in the search term.
Fuzzy Match	Enable to find matches even when the search term does not exactly match the result. Useful when typos can occur in the search term.
Fuzzy Max Edits	Available when Fuzzy Match is enabled. Maximum number of single-character edits required to match the specified search term. Value can be 1 or 2. Default is 2. A single-character edit can be an insertion, deletion, or substitution of a character, or a transposition of two adjacent characters. Example, if your search term is 'cat': - With fuzzyMaxEdits: 1, possible matches could include 'bat' (substitution), 'cats' (insertion), or 'at' (deletion) - With fuzzyMaxEdits: 2, it would allow for edits like 'cart' (substitution and insertion), 'scat' (insertion and substitution), or 'tac' (transposition).
Fuzzy Prefix Length	Available when Fuzzy Match is enabled. Number of characters at the beginning of each term in the result that must exactly match. The default value is 0.
Fuzzy Max Expansions	Available when Fuzzy Match is enabled. Controls how many possible variations the search considers when finding similar terms to your query. Adjusting this can change both the number of results and how quickly you get them. The default value is 50. - Low Number (e.g., 50): - Effect: The search checks up to 50 variations. - It is faster but might miss some matches. - Suitable for: Fast searches when precision is not as critical. - High Number (e.g., 500): - Effect: The search considers up to 500 variations. - You get more matches, but it might take longer. - Suitable for: Thorough searches where finding more potential matches is important, even with typos.',