# Elastic search using SRS

**URL:** <https://forums.pega.com/t/elastic-search-using-srs/9701>\
**Category:** Pega-as-a-Service\
**Created:** [July 10, 2025, 7:09pm UTC](https://forums.pega.com/t/elastic-search-using-srs/9701 "2025-07-10T19:09:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Balaji\_Srinivasaraghavan](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/balaji_srinivasaraghavan/32/22487_2.png) [@Balaji\_Srinivasaraghavan](https://forums.pega.com/u/Balaji_Srinivasaraghavan)\
**Post date:** [July 10, 2025, 7:09pm UTC](https://forums.pega.com/t/elastic-search-using-srs/9701/1 "2025-07-10T19:09:38Z")

</div>

We are starting to use SRS on Pega cloud. Our existing apps use traditional elastic search. We are experiencing issues with embedded property search in SRS. I will explain further below.

**Behavior:**

We are searching using pxRetrieveSearchData activity by supplying pySearchString. This string is build dynamically like pySearchString = .property: e.g. pySearchString = MemberDetailsPageList.MemberAccessNumber:_00000000000022_

The expectation is that the search look for MemberDetailsPageList page list entries and specifically look for content (value contains) of property named “MemberAccessNumber”. However it fails to do so. This works in the traditional elastic search.

**Question:**

Are there changes to elastic search indexing and retrieval of embedded properties in SRS? Any insights from the product team is appreciated as embedded properties search is very heavily used in many of our applications.

---

<div class="post-metadata">

**Author:** ![NickLoving\_GCS](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/nickloving_gcs/32/6894_2.png) [@NickLoving\_GCS](https://forums.pega.com/u/NickLoving_GCS)\
**Post date:** [July 11, 2025, 7:43pm UTC](https://forums.pega.com/t/elastic-search-using-srs/9701/2 "2025-07-11T19:43:54Z")

</div>

@Balaji Srinivasaraghavan

There are differences in how SRS and embedded search work by default, especially with embedded properties. There are a few settings related to this you can change/create that may be necessary depending on the version of Pega in use (both in the Pega-SearchEngine ruleset):

indexer/srs/includeCSPEmbeddedPropertiesInDataModelindexer/srs/indexAllFieldsForFTS

This is discussed a bit here: [Compatibility of search engines upon migration](https://docs.pega.com/bundle/platform-241/page/platform/search-engine/compatibility-search-engines.html)

Setting indexAllFieldsForFTS to true is probably the easiest way to make the search/indexing more like it was with embedded search, but you will likely be indexing more properties than are needed. After changing either of the settings, you would need to update the data models on the Search Landing Page and then re-index any classes that needed this update.

---

<div class="post-metadata">

**Author:** ![Balaji\_Srinivasaraghavan](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/balaji_srinivasaraghavan/32/22487_2.png) [@Balaji\_Srinivasaraghavan](https://forums.pega.com/u/Balaji_Srinivasaraghavan)\
**Post date:** [September 22, 2025, 1:03pm UTC](https://forums.pega.com/t/elastic-search-using-srs/9701/3 "2025-09-22T13:03:07Z")

</div>

@NickLoving\_GCSThank you for your response. We tried enabling the DSS mentioned. However, the search on specific embedded property seem an outlier that is not working on SRS but works in embedded elastic search. We are raised a Pega issue regarding this - INC-C30134. I believe the indexing is occurring however there is some gap in how SRS search and retrieve embedded property / page list in the indexes.

---

<div class="post-metadata">

**Author:** ![Balaji\_Srinivasaraghavan](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/balaji_srinivasaraghavan/32/22487_2.png) [@Balaji\_Srinivasaraghavan](https://forums.pega.com/u/Balaji_Srinivasaraghavan)\
**Post date:** [September 25, 2026, 12:47pm UTC](https://forums.pega.com/t/elastic-search-using-srs/9701/4 "2026-09-25T12:47:29Z")

</div>

Based on guidance from the SRS product team, scalar and embedded properties must be searched differently in SRS.

**Scalar properties** : Use a standard Elasticsearch query in `pySearchString`.

E.g. set `pySearchString` as `MemberState:"VA"`, Use this when `MemberState` is a property on `pyWorkPage`.

**Embedded properties** : Use the Report Definition **`Filters`** data model instead of `pySearchString`.

`.pyContent.pyFilters.pyFilter(1).pyLogicLabel = "F1"`  
`.pyContent.pyFilters.pyFilter(1).pyFilterName = "MemberPageList.MemberState"`  
`.pyContent.pyFilters.pyFilter(1).pyFilterValue = "VA"`  
`.pyContent.pyFilters.pyFilter(1).pyFilterOperation = "search"`
