Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

DynamicSelect return messages that cannot be localized

SA-8513

Summary



Requirement to display the localized text for the DynamicSelect control results.
If the result set is empty, then Dynamicselect control displays message as ‘No results were found’.  Developer is not able to localize DynamicSelect control message.



Error Messages



Not able to localize the message ‘No results were found’ in Dynamicselect control.
 

Steps to Reproduce



1. Configure a Dynamicselect control in a section and use the source as ReportDefinition or Activity.
2. Ensure that there are no values present for that field which is used as a source for this Dynamicselect control.
3. Create a field value rule for ‘No results were found’ with fieldname pyMessageLabel.
4. Run the flow and observe the error message displayed is in English or in localized text.


Root Cause



The root cause of this problem is defect/misconfiguration in the operating environment.
Field value rule created in the localized rule set is correct. However PRPC is not able to pick the field value at runtime.


Resolution



This issue is resolved through the following local-change:
After creating the field value rule, Re-saving the section that contains the Dynamicselect control results in displaying localized text at runtime.

 
Suggest Edit

Published June 12, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us