Answer
This is commonly a permissions issue specific to how Aurena evaluates access, rather than a problem with the SQL data source itself or the lobby element's configuration — the logged-in user's role/permission set may be missing a grant that IEE doesn't strictly enforce for the same view but that Aurena does check. Review and correct the permission set(s) assigned to the affected users so they include whatever access the lobby element's underlying SQL data source actually requires; granting the missing permission resolves the blank-data symptom without needing any change to the lobby element or data source definition itself.