After an upgrade, modifying a field (like the wanted delivery date) on Customer Order Lines fails with a `FUNCTION_NOT_FOUND` error referencing a function import (like `CheckReplication`) being called with more parameters than it actually has.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

This points to Page Configurations left in a "Behind" status after the upgrade — a new release can change an underlying API's parameter signature in a non-backwards-compatible way, and an existing Page Configuration built against the older signature will keep calling the function with the old, now-invalid parameter list until it's rebased. Rebase the affected page's configurations to the current API version (following the platform's documented configuration-rebase procedure) rather than troubleshooting the function call itself, since the function signature change is an expected part of the upgrade, not a bug.

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