When referencing another table's column in a read-only Select-statement custom field's Arguments section, the field errors saying no such column exists on the table, even though the column is confirmed to exist when queried directly against the database — is the underlying reference supposed to be the standard table or the generated custom-field table?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

In this Arguments/Select-Statement syntax, the table alias refers to the generated custom-field table (CFT) and the view alias refers to the generated custom-field view (CFV) for that Logical Unit — not the base application table directly, even though that's the table you can query and see the column in. This convention applies from the very first custom field created on that LU onward, since creating even one custom field is what generates the LU's own CFV/CFT that all its Select-type custom fields subsequently reference through those aliases.

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