A custom field pulls a value (like a Group ID) from a related record (like a Serial Object) and keeps recalculating whenever that source record changes — but the requirement is to capture and keep the value as it was at the moment the record referencing it was originally created, not track live changes.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Use a genuinely persisted custom field rather than a live-computed read-only one, and populate it once via a Custom Event with a SQL action that fires specifically on creation of the referencing record (for example, on insert into the relevant transaction table) — this captures a one-time snapshot of the source value at creation time into stored data, rather than a read-only field that recalculates its value from the current state of the related record every time it's displayed.

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