How do I solve thee? Let me count the ways ...
I suspect you'll get better suggestions than this, but here's an easy solution ...
(This assumes you want a Value List and not a portal)
- in your parent table, create a global calculation field that is set to "Available"
- create a relationship to the child table based on this field (e.g. parent:: g_static_Available <-> child::Status)
- base your Value List on this relationship
What you describe is called a conditional value list. Since you don't want the user to select a filtering value, this becomes what I call a "hard wired" CVL.
One option is to set up the typical relationship based CVL, but use a script or calculation field to set up the match field value to link to only "available" records.
I usually prefer to instead define a calculation field such as
If ( status = "available" ; valuelistfieldhere )
i can then set up a field based value list that lists values from this field to get only available values. Note that if you use two fields in your value list and sort or display the second field, this calculation should refer to that second field.
1 of 1 people found this helpful
Oh, got it,,,, I had an additional relationship to my puppy table and it was taking the new relationship as an "and" argument. Fixed and working. Thanks tons David!!!