A Lobby Link-type element built from a Saved Search on Customer Order Lines can't be configured with a target Page (the Page field is empty and unselectable), so clicking the link doesn't navigate anywhere — the same setup works fine if the data source's underlying view is changed to the plain CUSTOMER_ORDER_LINE view instead of the view actually used by the Customer Order Lines screen. Why does this happen, and is there a way to keep the original view?

All FAQ questions / Platform, Aurena, and customization

Answer

This happens because the view actually used by the Customer Order Lines screen doesn't have a default home page connected to it for lobby-link purposes, unlike the plainer CUSTOMER_ORDER_LINE view. Rather than switching the data source's view (which may lose fields the saved search depends on), you can instead give the Lobby Link element a direct page address instead of relying on the view's default home page — for Customer Order Lines specifically, that address is ifsapf:tbwOverviewCustOrdLine. Specifying the address directly bypasses the missing default-home-page association entirely.

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