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

PromptSelect control is displaying as Input Text field



Developer reported that if they use PromptSelect control inside a section present in another class using some page, eg: Page.PropertyName, then at runtime, this field is appearing as normal input text field.

However if they use same property inside a section which is present in the same class, (without using any page reference) then promptselect control is displaying as dropdown properly.

Error Messages

No error message.
Instead of displaying as dropdown, PromptSelect control is displaying as normal input text field.

Steps to Reproduce

1. Create a property with PromptSelect control and TableType as PromptList.
2. Include this property in some section present in another class by using some Page reference. (Refer the page name in Pages & Classes tab of section)
3. Now preview the section and observe the field.
This promptselect field is appears as input text field.

Root Cause

The root cause of this problem is a defect in customer application code/rules.
Developer has not given the proper page reference in pre-activity of flow action. Due to this PRPC is looking for the property reference in wrong class and it is not able to find it.


This issue is resolved through the following local change:
After giving proper page reference in Pre-Activity pages & classes tab, PromptSelect control is displaying dropdown properly at runtime.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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.

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