A value list is a rather limited selection tool; have a look into the sample file to see a better way.
If you have FM13, check out the faculty FM13 layout, which exploits Conditional Hide.
PS: If you're really keen on using a value list, you can define it in the desired way (based on the relationships in the sample file):
1. Field: Semesters::semester, 2. field: Courses__filteredForCount::cFoundCount, Starting from: Faculty
This assumes that you're using semester names, instead of keys …
Courses_eos.fmp12.zip 72.2 K
Hello, if you are using FM13, try creating a summary field for each semester. then you could put four portals on a popover. This will allow you to see the count for each semester. Then next to the portals put the filed with the value list. Then you can choose from the value list.
The reason you are seeing nine in the count field is because it is counting from the found set of records. Hope this helps.
try creating a summary field for each semester. then you could put four portals on a popover. This will allow you to see the count for each semester. Then next to the portals put the filed with the value list. Then you can choose from the value list.
Notwithstanding other problems with your suggestion (like the fact that I don't understand it … ) : you want to avoid solutions that assume a given quantity (or are optimized for it), since then you have to tweak it for every (substantial) change in the amount of data involved, i.e. frequently …
I really like this example. It's a bit more complex than what I would like for what would seem like an easy feature to add, but it would greatly help me in other scenarios. The FM13 layout is incredibly elegant, which is a real surprise, and I'm going to spend some time studying the back end so I can try implementing it into my solution.
I really appreciate the time and effort you took to answer the question. Thank you very much.