Skip to content

A Lobby element's filter is built to accept a comma-separated list of Site codes from a parameter (so a user can filter to several sites at once instead of just one), but the resulting SQL only ever matches a single value — the whole comma-separated list gets treated as one literal string inside the IN(...) clause.

Answer

This happens when the filter expression wraps the parameter in its own quotes (like IN ('$SITE$')) — that resolves to a single quoted string containing commas, not multiple separate values, so it only ever matches one row. Two things fix it: don't add your own surrounding quotes around a multi-select parameter if the values already come through pre-quoted and comma-separated (so it resolves to IN ('C0158','C0152') rather than IN ('C0158,C0152')); or, more robustly regardless of how the parameter is quoted, split it programmatically with something like CONTRACT IN (SELECT REGEXP_SUBSTR('$SITE$', '[^,]+', 1, LEVEL) FROM DUAL CONNECT BY REGEXP_SUBSTR('$SITE$', '[^,]+', 1, LEVEL) IS NOT NULL) — this reliably turns a comma-separated parameter value into multiple matchable values regardless of quoting, and can be combined with a similar company-level filter for filtering by company down to that company's sites.

← Browse Platform, Aurena, and customization questions