Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

Restricting a value list based on found set?


This topic is 5217 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted (edited)

I have a table with 12 subjects. The user can go to a layout where they can select, through check boxes, any number of these subjects to create a found set of records. At any time they choose, I would like the users to be able to go to a layout, where using a dropdown list, they can select one of the subjects in the found set only, and go directly to the first record that contains that subject name. I don't want them to see all 12 subjects - only the ones that they originally selected. I also want to keep the found set that contains the selected subjects. I know that value lists will always show all the subjects available, not just the ones in the found set in a circumstance like this. How can I accomplish restricting the dropdown? (I have a kludgy work-around that involves copying the found subjects to a small table and then basing the dropdown on those records but this seems kludgy to me because I am duplicating information, then I have to find the record in the main table that matches and this is relatively slow in Filemaker)

Any suggestions would be appreciated.

--Peter Brooks

Edited by Guest
Posted

The user can go to a layout where they can select, through check boxes, any number of these subjects to create a found set of records.

How is this done - is there a global field for this?

Posted

I have a similar situation. For one of the fields in my solution, one user chooses from one set of values, another chooses from a different set of values.

I defined a field in a single-record table that is used as the 'Values from field' in a Value List definition.

I set that field to a list conditional upon the user (in your case, just set it to the field corresponding to the checklist that defined the subset of 'subjects' of interest).

Then I use that Value List for entry in the field whose content varies by user.

The field in the single-record table used in the Value List definition can not be a global.

It may cost you an extra table if you don't have any single-record reference tables laying around, but I think it will get the job done.

Hope that helps.

Posted

Yes - but it uses a script that stores multiple values in one field, then generates multiple finds ("OR" finds) to create a found set.

This topic is 5217 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.