Custom fields added to active work orders (the Active Separate logical unit) don't automatically appear on the corresponding record once the work order completes and moves to Historical Separate — what's the correct way to make sure both the fields and their data carry over to history?

All FAQ questions / Asset and maintenance management

Answer

Define the exact same custom fields (same names, same definitions) on the Historical Separate logical unit as well — once both sides have matching custom field definitions, IFS automatically carries the custom field data across when a work order transitions from active to historical. No separate migration or mapping step is needed beyond making sure the custom field definitions themselves exist identically on both LUs.

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

← Browse Asset and maintenance management questions