Hi @sinyb 

I am not quite sure about the requirement here. Assume, you are looking for creating a navigation from a counter element?

A reference: Service Manager Lobby

Element:

Data source:

Please let us know, if it answered or send more details to help you.

/Sanjeewa

Hi Sanjeewa,

You are correct, that is what I’m trying to do. However, I can’t make it work like I want to. I have a dataset which contains some data, and the conditions in the dataset looks like this (Note that # won’t work for us in the conditions, we need to use $ instead). Note that SALES_GRP_D and user_def17 are conditions that the user can change:

And, the element looks like this:

However, when clicking on the element, it opens the search in the request screen like this, instead of having actual values:

Try $SALES_GRP_D$ and $OWNER$ in your element navigation (below highlighted) instead of #SALES_GRP_D# and #OWNER#

Hi,

Thanks, tried this, a little silly mistake to make. When changing that value, the value is passed correctly to the search screen, however, the filtering created in the dataset is not used in the request search. In this example, we had 13 requests in the counter, but over 1000 requests was found in the search screen.

Reason - DSP_booking_date_expires database view may contains additional conditions. So it filters to 13 records. But Request screen is querying directly from the request table. So, you cannot expect same number of records in those 2 result sets.

/Sanjeewa

Hi,

Yes, that was my initial question, if it was possible to use the same conditions in the dataset to filter in the request screen when navigating from the counter.

I guess I’ll have to make it work in another way, thanks for your help.