A Lobby Data Source built on a SQL/IAL view successfully previews data with no columns added, but adding the actual columns you need makes the preview hang and eventually time out, even though the underlying SQL statement (checked via debug) looks correct.

All FAQ questions / Data migration

Answer

Check whether each column's declared data type in the Lobby Data Source matches the underlying database column's real type — for example, a column that's actually NUMBER in the source table but was defined as Text in the Lobby Data Source can cause exactly this kind of query-never-returns behavior once that column is included. Correcting the column type to match the real underlying type (and removing unnecessary column aliases, which can also interfere) resolves it.

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

← Browse Data migration questions