Legacy Knowledge Base
Published Jul. 2, 2025

Custom field values are not saving for Document Folder

Written By

Pooja Bhambani

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

  • Steps to reproduce:
    1. Start Liferay DXP 7.2
    2.
    Log in as admin.
    3. Navigate to Custom Fields under configuration.
    4. Select 'Documents Folder'.
    5. Create a new custom field for the document folder.
    6. Click on the "+" icon. Select 'Text Area' and give any name in the field.
    7. Navigate to Document & Media portlet > Click on "+" icon > Add folder > Type any name in Name field > Click Save.
    8. Edit that folder and enter a value into the custom field as created in step 6.
    Expected Behavior: The values must be saved in the custom field.
    Actual Behavior: The values are not saved in the custom field and it is showing as blank.

Environment

  • Liferay DXP 7.2

Resolution

  • The observed behavior is a known issue/bug and it is fixed in Liferay DXP 7.2 fix-pack-17.
  • If the hotfix is required for this issue, please create a support ticket requesting a hotfix by attaching patch details.
  • Installing Fix Packs and Hotfixes on Liferay DXP will guide to installation of the hotfix in the respective environment.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base