A Lobby Data Source built on an IAL that joins two otherwise-unrelated views (using REGEXP_SUBSTR to relate them, since there's no real foreign-key relationship) throws an error and shows no data when a specific parameter (like MANAGER) is used in the lobby element's condition — how do you actually diagnose this kind of Lobby-parameter failure?

All FAQ questions / Platform, Aurena, and customization

Answer

Use the Preview button in the SQL Data Source section of Data Source Designer as your first diagnostic step — when previewing a data source whose condition references a parameter (like company = '$COMPANY$'), it should prompt you to supply a test value for that parameter. If it doesn't prompt you at all, that points to a syntax issue in how the condition references the parameter. If it does prompt you, check whether supplying a value returns real results or an error — that narrows down whether the problem is in the parameter binding itself or in the underlying query logic. Also confirm the underlying view or IAL your data source is built on genuinely includes a column literally named to match the parameter (for example, a real MANAGER column) — a lobby condition parameter can't bind to a value that isn't actually present as a queryable column in the data source's own result set.

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