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

Value is not saved when same property is used twice

SA-79818

Summary



When a property is being used twice in a section in two dynamic layouts, the input value of the property in first dynamic layout is overwritten by the second one. The property value is not saved if changed from the first dynamic layout and the user clicks Save. 


Error Messages



Not Applicable.


Steps to Reproduce

  1. Create a case type
  2. In the section of an assignment, use two dynamic layouts and set two UI control. For example, Text Input in each dynamic layout and reference the same property
  3. Use the 'Run visibility condition on client' option to show or hide each dynamic layout and use a Dropdown control to set the visibility value 
  4. Run the case and attempt to save the property value by providing an input to the Text Input field in the second dynamic layout


Root Cause



An issue in the custom application code or rules. On setting the same property in different layouts in a section and selecting 'Run visibility condition on client" as checked, then it always passes the value present at the bottom of the Document Object Model (DOM).

Resolution



Perform the following local-change:
  1. Uncheck the 'Run visibility condition on client' option
  2. Add a refresh section action in the dropdown so that whenever the value of the dropdown changes, the complete section is refreshed 

 

Published August 19, 2019 - Updated December 2, 2021

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