Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Using Elastic search

Updated on September 18, 2020

To use Elastic search, call the D_<ObjectType > Results data page as your data source for either an auto-complete control or elsewhere in any other search field.

The above data page takes the below parameter:

  • SearchString – The data string to search for

For all classes, you can perform the search for fields specified in the tool tips on the Search screens. It is defined through a search model that is configured through the pySearch rule of the Custom Search Properties type created in each of the classes, which instructs the Elastic code which fields to enable for search.

Note: Although not advisable, if more fields for search are required, they can be added to the pySearch and adequate data indexing is done. Note that adding too much data may significantly increase the Elastic index file, causing potentially poor performance.

The data source for the data page is the Activity as GetSampleDataResults, which prepares the query to be passed and calls the report definition. This Activity sets the properties based on the parameter that is passed and then calls the report definition rule by passing the query string to fetch the records for the specified object type.

  • Previous topic Step 11: Implementing Elastic search on sample data objects
  • Next topic Step 12: Managing member PII data masking

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us