…it would seem logical to put each resource in a parent directory according to job type and then use TVs for the other options but I’m wondering if there’s a more ‘holistic’ or logical approach. Thank you.
Also, if you expect a lot of resources (or additional filters), you could take a look at ClassExtender or ExtraFields. A solution with one of these extras might be easier and faster to query than using multiple TVs.
Thank you - certainly fast. I’m going to have fun though, trying to work out how to use it for Location, Salary, Job type. Any tips or examples, gratefully received!