A Custom Menu's Source Key Name (or its Condition) needs to reference a value that's only available as an API getter-function call, like an order reference resolved via a Get_ method, rather than a literal physical column present in the underlying view. Is there a way to make this work, since Custom Menu configuration normally seems to require a literal source column?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Yes — a Custom Menu's Source Key Name can actually reference an API getter-function call directly, in the format &AO.<Package>_API.Get_<Method>(<column1>,<column2>,...), passing other genuine columns from the same view as that function's own arguments. This works because Custom RMB configuration doesn't actually evaluate or validate the API call at definition time — instead, the string entered as the source key name is used verbatim as the exact column expression in the client's own generated SELECT statement, with no alias. This means any expression valid in that SELECT statement's column list, including a full API function call referencing other visible columns, can be used as a Custom RMB's source key name or condition, not just literal physical column names.

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

← Browse Developer Studio, deployment, and upgrades questions