I cannot see your screenshots for some reason, but have you had a look here? https://docs.ifs.com/techdocs/22r2/040_tailoring/250_lobby_configurations/080_navigation/#supported_navigation_parameters

Thanks for you reply. I have read this document before I submitted a ticket. It does not help so far. I have attached my screenshots again. Please review. Thanks

Hi @jgrace 

We have found that the name of the column being passed is case sensitive, so using your screenshots it should be $filter=PartNo eq $ PART_NO]

I tried as suggested. It still would not work. Please see my screenshots. Element is a List in Lobby.

Two more screenshots - from lobby to page/SupplierForPurchaseParts/

When I filtered the partno manually from the page, I can see it.

Hi @jgrace

I’m sorry, but I can’t see the screenshots, only the one associated with your last message.

We have navigation to Inventory Part In Stock from a list in a lobby which is using a custom view, hence the slightly different names, but this also has a page parameter and the navigation works fine.

The navigation link is defined slightly differently to yours as shown in your earlier screenshot, with no path element and no semi-colons: 

page/InventoryPartInStock/List?$filter=PartNo eq $ Part No] and Contract eq $ Contract] and ProjectId eq $ Project Id]

We’re using 22R2 but the lobby was defined and worked in 21R2.

I got it to work now by using »

page/SupplierForPurchaseParts/List?$filter=PartNo eq $$PART_NO]

instead of

page/SupplierForPurchaseParts/List;path=xxxx;$filter=PartNo eq $$PART_NO]

Thank you very much for your help.