Adding a custom field that needs to pull a value from a different, related object, for example showing a Purchase Order header's Coordinator field on the Project Miscellaneous Parts screen, doesn't work using the usual Reference implementation type, since Reference-type custom fields can't reach across to an unrelated object this way. How is this kind of cross-object custom field actually built?

All FAQ questions / Platform, Aurena, and customization

Answer

Use a SQL-statement-based custom field instead of a Reference-type one — call the appropriate API getter function for the value you need, parameterized using the current form's own bind variables (such as :order_no and :contract), following the general pattern SELECT <Some_API>.Get_Some_Value(:bind_var) FROM dual. For a Purchase Order header's Coordinator-style field specifically, this means calling the relevant Purchase Order API accessor function with the current record's own order number as the bind variable, rather than trying to configure a direct object reference between two otherwise-unrelated Logical Units.

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