Updating a custom field via Excel Migration works fine for plain text custom fields, but fails specifically for a custom field that's linked to a custom list/enumeration (backed by a custom page/custom LU) — entering the display value from the custom list into the migration spreadsheet's mapped column produces an error rather than actually updating the field.

All FAQ questions / Data migration

Answer

For a custom field backed by a custom list/enumeration, target the underlying '_DB' suffixed column in your migration mapping (for example, CF$_YOURFIELD_DB) rather than the plain CF$_YOURFIELD column — the plain column reflects the presentation/display value, while the _DB-suffixed column holds the actual stored database key that Excel Migration needs to write to for this field type. Mapping to the _DB column instead of the display column resolves update failures specific to custom fields linked to custom lists or enumerations.

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

← Browse Data migration questions