Legacy Knowledge Base
Published Jul. 2, 2025

Multiple rich text fields assign the same default value

Written By

Kanchan Bisht

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • If several 'Rich Text' components are included in a form and assigning a different default value to each of them, then while saving, it assigns the same value to all the fields.
  • Steps to reproduce:
    • Start a new DXP 7.3 bundle
    • Create a new form
    • Add a Rich Text field and add a predefined value (under Advanced), e.g. 'Value 1'
    • Add another Rich Text field and add a predefined value (under Advanced), e.g. 'Value 2'
    • Click save   
      Expected result: Rich Text fields have the respective text e.g. 'Value 1' and 'Value 2'
      Actual result: Rich Text fields have the same value and an error message on portal UI.Screenshot__29_.png

Environment

  • Liferay DXP 7.3

Resolution

  • It's a known issue and will be fixed in the upcoming fix pack.
  • If the hotfix is required for this issue, please create a support ticket requesting hotfix by attaching patch details.
  • Installing Fix Packs and Hotfixes on Liferay DXP will guide to install this hotfix in the respective environment.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base