CODEWITHSUNDEEP
listrelationshipfilemaker
jfalberg
jfalberg

Reputation: 151

Filemaker Value List by calculation?

I want to have about 8 different Value Lists from a field called "ProfileName" for separate dropdown list purposes depending on certain values in a Position or type field. It seems the only way I can accomplish this is by having 8 separate relations just for this purpose, and while it would be nice to do this based on calculation, is there perhaps a cleaner way to do this without having so many extra relations?

For example: where Position = "Project Mgr", get all names associated
where Type = "O", get all names associated
where Position = "Supervisor", get all names associated

Upvotes: 0

Views: 736

Answers (1)

michael.hor257k
michael.hor257k

Reputation: 117175

It seems the only way I can accomplish this is by having 8 separate relations just for this purpose

One relationship should be quite sufficient. Your description is not quite clear but as an example, if you have a Position field and a relationship based on matching Position, then once you enter "Supervisor" into the Position field, a value list showing only related values will show only supervisors.

Added:

It seems like you have a structural problem: instead of 8 position fields, you should have 8 (or any number of) position records in another table. Your current predicament is merely a symptom of the structural issue.

Here's an example of something which I think is similar to what you describe:

enter image description here

Here, your project would have 8 related records in the Roles table. In each role record, you would select the RequiredType and then assign a staff member to the role using a value list defined to use values from EligibleStaff::StaffID, show only related values starting from Roles.

Upvotes: 1

Related Questions