Combining a wildcard character with a Lobby page parameter in a data source's filter condition (to do a partial/contains-style match) produces an error in Aurena — how do you write a working wildcard-plus-parameter condition?

All FAQ questions / Platform, Aurena, and customization

Answer

Build the wildcard pattern using string concatenation around the parameter substitution, rather than trying to embed the wildcard character inside the parameter reference itself — for example, upper(description) LIKE upper('%' || '$SEARCH_PART_DESCRIPTION$' || '%'). Concatenating literal '%' characters on either side of the substituted parameter value is what lets a wildcard/contains-style match work correctly in a Lobby data source condition.

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