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

Error with two section includes of the same section



There are two different section in a single layout. Both section shares the same property. The first section uses it to get input from user and second section uses it to show the value entered. If first section field is a required field and no value has been entered then while submitting the error is getting displayed in the second field.

Error Messages

"Value cannot be blank"

Steps to Reproduce

1. Create a single page property in a class (class #1) whose page definition routes to a separate class (class #2).
2. Inside the separate class create a new single page property whose page definition routes to the class it is in (class #2).
3. Create a new section with a required property in class #2.
4. Create a new section in class #1 and do two section includes in separate dynamic layouts, one using the first single page property, and one using the second single page property.
5. Run the section that includes the two section includes and prompt the "Value cannot be blank" error on the second single page property section include and witness the red error text on the first single page properties section include (the label for the field).

Root Cause

As same section has been used twice in a different way under the same layout, when one section is getting error, the other one is getting affected by showing error message of former section.


Apply HFix-27076 and HFix-26544 to resolve the issue.
Both the hotfixes have changes related to Repeat Dynamic Layout validation in Pega-UIEngine - RULE-FILE-TEXT WEBWB PEGA_VALIDATORS.JS.

Published September 23, 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