Think most likely you are using the Navigation\Tabs wizard? The screen shot didn't show how the ticket(s) are being selected. 

Nonetheless, each tab have their own aggregates/data actions getting the required data right? So in the filters, have to include one more,

ie. Data.Ticket = NulltextIdentifier() or Data.Ticket = SelectedTicket (Local variable)

At the UI portion, where user choose the ticket etc, the OnChange handler, have to do a data refresh for all the aggregates

Hello,

What data are you referring to specifically, and what type of data are we filtering? Based on the data type, the filtering approach will differ. For example, if Java, or the skill set in general, is coming from a static entity, you would pass the Java ID that exists in the static entity into the block that contains the data, or directly in the same screen if you are not using a block, and then filter using something like Data.SkillsetId = PassedInputParameter.

If, on the other hand, you are referring to the skill set as text, then you can simply filter it using the LIKE keyword. For example, let us say you are using an aggregate and filtering on the SkillSet column using LIKE '%' + your input filter + '%'.

Basically, if you want the search to work across every piece of data inside the ticket, you first need to identify where each piece of data is retrieved from, meaning which specific column it belongs to, and then add it to the condition. For example: 

Name LIKE '%' + @SearchText + '%' 

OR 

SkillSet LIKE '%' + @SearchText + '%' 

OR 

JobTitle LIKE '%' + @SearchText + '%' 

OR SecondOption LIKE '%' + @SearchText + '%', 

and so on (this is not present in your screenshot, so I made a guess).

But the core idea here is not the tabs, in my opinion. It is how you filter the data. Clicking on the tab is just one small step; based on it, you filter the aggregate or the SQL query based on the passed parameter.

So, as an example to wrap things up, say you have a tab called Java and you click on it. There are two scenarios here: either your specific data is inside a static, in which case you pass the ID of Java to the aggregate to filter with it, assuming it comes from a static entity, or it does not. In that case, you follow the same approach but replace the ID with the LIKE operator, for example SkillSet LIKE '%' + @SearchText + '%'. The same logic applies to the rest of the tabs, with keeping in mind of course refreshing the aggregate each time.

Hi,

I believe you are trying to search by multiple data fields, @Sherif El-Habibi has recommended the good approach to achieve that. I just notice some of possible cases that you may check:

• miss / wrong refresh of the aggregate / data action on filter changed
• wrong filter condition by and / or: because you search by multiple fields, any field has the search text will appear in the result
• I saw a checkbox, is it affected to the result, can remove the condition of that first to check

Actually, the bug can be anywhere, I think you should share the oml for further investigation if possible

Can anyone please provide the OML to better understand the issue.