A couple of basic questions:
- What's the approximate volume of data? The reason I ask is that FM's native portal filtering is great, up to a point - i.e. a couple of hundred records. Beyond that, you'd be better off using relationships to filter the records that the user can see.
- How many sites are there? If it's just a few, you could have a tick-box selector to control the filtering - user puts a tick against 'London' to see London's records, removes the tick to hide them, etc. The field on which the tick-box is based could be a 'Boolean-style' global field (i.e. either set to 1 or 0), perhaps called SHOW_LONDON. This is a tidy approach if you have up to about 10 sites, beyond which the dashboard may get a bit clumsy.
Happy to provide more detail if you need it.
Dave's right. I might even use a native FileMaker FIND/SORT (script) instead of realtionship if the data set is really huge. Done in another window can be helpful, even if "off screen". I might then "gather the keys" to be able to then 'filter' by those in the original layout/window.
Thank you Dave and Beverly for your thoughts on how to approach this , site wise, there are currently just 5, I couldn't see that rising significantly in my lifetime!
Typically each site would have somewhere in the region of 30 to 40 staff records each. (Staff not FM users)
Related records to either staff or the site could become rather significant, we're not a demanding organisation, if there were to be some degree of lag, they'll live with it! ( Well, they have two choices.. LOL)