We are using the OOTB Search and Select component, and in the Data Page response, we are setting a Page‑Set message to display the error. Once an error message is displayed, we face the following issues:
-
An additional system‑generated message from Pega appears along with our custom error message. (we found an article this is a product issue and will be release with 26.1 version Unexpected error message displayed alongside custom data view DX API errors | Support Center)
-
The error message does not clear automatically after a subsequent successful API call when the transaction data loads. Even if the message is cleared, it still remains visible in the UI.
-
When a subsequent API call fails, the previously loaded transactions remain visible in the table instead of being cleared. The table continues to display the earlier loaded transaction data.
As confirmed by the Pega Support team, the above issues will be addressed in the 25.1.3 and 26.1 upgrades.
Given that an upgrade may not be immediately feasible, we would like to understand whether there is any interim workaround or recommended design approach to display user‑friendly error messages when a Data Page used by the Search and Select (Constellation) Data View fails.