Hi Densingh,
Although I agree with Ozan I do want to provide you with a solution. The issue probably is that you are using the data from the aggregate straight in the table (normally a correct method) but for this it is hindering your. What you can do is the following;
- Create a structure with all the fields in your table.
- Create two(All and Selected) variable with a list of this structure in your screen
- In your Preparation or OnAfterFetch event parse the data from the aggregate just as you currently do in your expression and add each parsed record from the aggregate as a new record in the All variable.
- Create a filter function that selects the correct records from the list in step 3 and add those selected records into the Selected variable.
- Configure the table to that it shows the Selected data
- When the Search key changes exectute the filter function from step 4 ago and this will repopulate the list and thus the table
Why two lists? The first (All) contains all records from the aggregate and will do so to not put to much pressure on the database. Why retrieve the data when you already have done so in the past? Please note that having two variables could not be the correct method for a Web Traditional application or when you have a very large dataset. In that case you need to make a complex query with perhaps some calculated fields in your aggregate for filter purporses.
Greetings,
Vincent