A Lobby Data Source column uses a CASE expression to display a custom, business-meaningful sort order for a status value (like Blocked, Planned, Released, in a specific sequence rather than alphabetically), and an equivalent Quick Report sorts correctly this way, but the same CASE-derived alias in a Lobby Data Source just sorts alphabetically instead.

All FAQ questions / Platform, Aurena, and customization

Answer

A Lobby Data Source's ORDER BY can't sort by a CASE-derived display alias the same way a Quick Report's SQL can. Keep the CASE expression for producing the display label itself, but drive the actual sort order using a separate DECODE(<original_column>, 'Value1', 1, 'Value2', 2, ..., 'ValueN', N) expression directly in the ORDER BY clause, mapping each of the original underlying status values to its desired numeric sort position, rather than trying to order by the same CASE-derived alias used for display.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Platform, Aurena, and customization questions