A custom field's SQL-based value uses a WHERE clause referencing another custom field on the same screen as a bind variable (like `:CF$_OTHER_FIELD`), but this doesn't work the way a normal argument would — how should the current record's own field values be referenced in a custom field's select statement?

All FAQ questions / Platform, Aurena, and customization

Answer

Inside a custom field's own select statement, reference another field on the same current record using the v. prefix (e.g. v.CF$_OTHER_FIELD) rather than a plain bind-variable-style colon prefix — v refers to the view row currently being evaluated. Using the v. form for the argument, rather than treating it like an ordinary bind parameter, is what makes the cross-reference to the current record's own field value actually resolve correctly.

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