Legacy Knowledge Base
Published Jun. 30, 2025

Problem with Web content structure field reference

Written By

Viktória Gyömbér

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

Reproduction steps:
1. Create a structure "test-structure" -> add single selection field.
2. Edit the field options and corresponding field references -> Option1 (field reference: "true") and option2 (field reference: false).
3. save.
4. create a web content with "test-structure". select option1 ("true") and publish.
5. edit the web content and view source from top right corner (xml).

xml:
<?xml version="1.0"?> <root available-locales="en_US" default-locale="en_US" version="1.0"> <dynamic-element field-reference="SingleSelection45078601" index-type="keyword" instance-id="YR7rdaOf" name="SingleSelection45078601" type="radio"> <dynamic-content language-id="en_US"><![CDATA[Option55022596]]></dynamic-content> </dynamic-element> </root>
<dynamic-content language-id="en_US"><![CDATA[Option55022596]]>

CDATA for option1 suppose to be "true". But it is taking some random value("Option55022596").

Actual result: There is a random value
Expected result: It should be 'true'

Environment

  • Liferay DXP 7.4

Resolution

  • The field references are mostly used to refer to the field easier for workflow editors or template editors. The database will still reference the fields by their value/name instead of the reference id. The only function of the reference id is to make the editor job more easer in templates/workflow definitions. Based on the current expected behaviour this is not available in the out-of-the-box product.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base