Answer
If your data source's filter condition references the same custom-LU subquery more than once (for example, repeating an identical correlated subquery inside both an equality check and an IN-list check), try simplifying it to reference that subquery only once — restructuring the condition so the custom-LU lookup happens a single time, with its result reused (or the remaining comparisons built around plain NVL/OR logic instead of repeating the subquery), has resolved this exact class of Aurena-only error even though the root cause of why IEE tolerates the repeated subquery but Aurena's OData-based parser doesn't isn't fully understood. If your Lobby element's filter condition references a custom LU subquery more than once, that repetition is the first thing worth eliminating when it works in IEE but throws a page-parameter error specifically in Aurena.