A custom Aurena Navigation Link that worked fine on an older update stops working correctly after upgrading (search no longer works on the destination page) — the destination side of the link now shows the underlying Oracle column name instead of the Aurena field name in its filter configuration. What changed, and how is it fixed?

All FAQ questions / Platform, Aurena, and customization

Answer

On some update levels, a Navigation Link's destination filter can end up populated with the raw Oracle/database field name instead of the Aurena field name the page's search actually expects — the two aren't interchangeable even though they refer to the same data. The fix is to manually overwrite the NavigateFilter value back to the correct Aurena field name (e.g. CustomerId rather than its underlying database column name) so the destination page's search works correctly again.

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

← Browse Platform, Aurena, and customization questions