Preserve selection order in API for "Select from List" fieldPreserve selection order in API for "Select from List" fieldhttps://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&threadId=1235064352026-04-04T21:35:49Z2026-04-04T21:35:49ZPreserve selection order in API for "Select from List" fieldCristiano Nicolòhttps://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=1235064342025-07-24T16:11:04Z2025-07-24T13:03:49Z<p>In Web Content Structures, when using a "Select from List"
field with multiple selection enabled, the UI allows users to visually
reorder selected items. However, the current behavior does not
preserve this order when retrieving the values via API.</p>
<p>This is particularly problematic when editors rely on the selection
order to define the display or processing logic downstream. For
example, in our case, the selection order (e.g., priority_per_price,
date_rt, product_name, priority, price_desc, price_asc) was meaningful
and used in production systems to drive sorting behavior.</p>
<p>We have confirmed that in Liferay 7.4 q1.0 2025, the order is not
preserved and appears to be stored arbitrarily, which breaks the
expected functionality after recent upgrades. The visual reordering in
the UI is not reflected in the actual stored data or API response.</p>
<p>This behavior causes confusion and breaks backward compatibility in
environments where selection order has functional implications.</p>
<p>We suggest either:<br> - Persisting the selection order as defined by
the user in the API.<br> - Or, at least, allowing the configuration of
this behavior per field or structure.</p>
<p>This feature would improve consistency and data reliability for use
cases where selection order matters.</p>Cristiano Nicolò2025-07-24T13:03:49Z