The Excel Add-in returns an internal metadata retrieval error when validating or executing against a migration job that uses both a base view and a custom-field view — is this caused by the custom-field view specifically?

All FAQ questions / Data migration

Answer

This has been resolved in a confirmed case by exporting the migration job and re-importing it — re-importing regenerates the migration job's underlying generated APIs, which cleared up the metadata retrieval error. If the Excel Add-in fails with this kind of error on a migration job that references a custom-field view, try an export-then-reimport cycle on that migration job before assuming something is fundamentally wrong with referencing the custom-field view itself.

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