List Lobby Element - Navigation

​@ZTC ZTC JGOTA you may want to use the Odata syntax of “startswith” or “contains”

This may be coupled with changing the lobby data source so that the wildcard ‘%’ is concatenated after the parameter. This way you don’t need to pass those characters in the url when navigating 

Lastly, maybe explore using the projection data source (if your query is simple enough). Your end result for filtering and navigating would look very similar 

Hello ​@PhillBronson , Thanks so much for your answer.

How does the Navigation will look according to the option below?

“This may be coupled with changing the lobby data source so that the wildcard ‘%’ is concatenated after the parameter. This way you don’t need to pass those characters in the url when navigating”

​@ZTC ZTC JGOTA the easiest way I’ve found is to go the page you are trying to navigate to and enter your filter criteria. The url will contain the syntax that you need to use. Additionally, the ‘advanced’ option will show a more readable version of the same thing.

With your search, enter the same thing without the wildcard and it’ll show how to format ‘startswith’ as that is the default search behavior 

you should see something like this:

​@PhillBronson 

I tried to use the following

page/PaymentScheduleForPurchaseOrder/Form?$filter=(contains(Contract, '%')) and (contains(tolower(VendorNo), '%'))

and it failed. Any idea?

All, be aware that using toupper in a navigation link $filter=Contract eq toupper($SITE$), will insert a space between the equal sign and the data on search, thus Contract = data. The navigation link will open the page and provide the results, but if you go to search, you will see that space there. In this scenario, say someone hits search for additional filtering, then the search will fail because of that space.

As a workaround, we tried to use trim. $filter=Contract eq trim(toupper($SITE$)), but then all search parameters disappear.

We are in 24R1 (sr2) in AST1.