A Lobby element built using the Query Builder tool (rather than raw SQL) for its data source works fine in Enterprise Explorer but returns no data — or in some cases breaks the entire Lobby page — when viewed in Aurena, even though it's based on the exact same underlying view.

All FAQ questions / Platform, Aurena, and customization

Answer

This has been confirmed as an Aurena-specific bug in how it handles Query-Builder-generated data sources, as opposed to SQL-based ones built on the identical underlying view. The practical workaround is to rebuild the affected Lobby element's data source using SQL directly instead of the Query Builder tool — a SQL-based data source against the same view works correctly in both Enterprise Explorer and Aurena, where the Query-Builder-based equivalent doesn't. If you hit this, also raise a support case with IFS, since it's a genuine platform bug rather than something fixable purely through Lobby configuration.

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