We are experiencing an issue with the Search and Select functionality in Pega Constellation (25.1.3.)
We use a single-select Data Reference to search for users in an external system via a Data Page, configured to reload once per interaction.
Steps to reproduce:
Search for users → works.
Select a result → triggers a form refresh that copies the selected value to another property. (Issue persists with or without the form refresh)
Search again → works.
Search a third time with or without selecting a result in step 3 → nothing happens.
Observed behavior:
The third search produces no visible UI response, no network request in the browser, and no activity in Pega Tracer or the Logs. Visual Hover and Click effects for the “Search” button remain active but no event is triggered.
Has anyone encountered this behavior or knows of a related Constellation issue or limitation?
The Search and ListView components seems to have gotten out of sync once we’ve selected a value. We noted that the Search button was still publishing the search events but nothing was listening on them anymore. We further noted that the publish scubscribe key matching in hook.js of the ListView component was mismatching keys all of a sudden, so nothing was triggering a server call and refresh of the result list.
We identified the root cause to be the following:
The Data Page we use for the search and select has no parameters defined but is automatically added with a parameter called “pyImplicitParameter” in the DX API JSON. We assume that this includes a dependency on the UI rendering. So after selecting a value, there is some rerendering/remounting of the component.
When using a new DataPage (that has also no parameters and looks absolutely identical) the UI builder stopped adding “pyImplicitParameters” and the search was working fine.
In our case, we are using the D_Entity_Search Data Page for the Search and Select functionality V25.1.4, which has two parameters defined: Profile and searchCriteria.
However, we are not seeing the pyImplicitParameter parameter in the DX API JSON.
Could you please confirm whether this issue could also occur with a parameterized Data Page? Also, is there anything else we should verify to identify the root cause before making any changes?