Filtering a portal?

Hi,

I have a clients screen with a portal to their accounts. My problem is that the accounts table is huge and it takes a long time to load. I want to be able to ‘filter’ the portal to show accounts for that client AND upaid ONLY. I have tried a tabpanel with two addFoundSetFilterParams but still slow.

Is there a way to filter portals using several fields at once i.e. clients_to_accounts showing UPAID only?

Dave

Hi Dave,

To use the filtered portal route you can use a concatenated pk in the client table which is a calulated result, or populate a global variable with the strings necessary to construct the concatenated pk and use this field as the base for your relationship off to accounts.

I would still use a tabpanel for this and you don’t necessarily need a related tabpanel as you can populate it with the required results programmatically !

If you look at the CRM solution again and go to the company details form you will see a tabpanel there with Addresses, Contacts, Orders, Reports

Go to the Orders tab and you will see that it uses comboboxes with value lists to drive the filtering of the list of orders shown.

You can use exactly the same principle to drive your filtering.

Check out how it works then come back with any questions !

Cheers
Harry

i think you have to look at youre indexes.
Those accounts that you display (without the filter) they are shown as related data?
Then you should look if the FKs are indexed.
Also are the filters columns where you want to filter on indexed?
It shouldn’t really matter if the table has many rows if the right columns are indexed then the load should be pretty fast.
If you show that table in its own main form. Does it then also load slow?