This feature was already requested 3 months ago but it was never answered except by other people saying how important it is! So I’m doing it again.
Please please let us use views on linked fields, not just tables. The capacity for corrupting the data is huge when we can’t control what can be selected. For example, I have a list of events at which something can be hired. I want to prevent the selection of an event in the past, the selection of an item that’s already hired out, the selection of a blacklisted user. When I process the return of a hire I select the hire from a list - I want to only display current hires, not have to trawl to the bottom of a list of past hires first. There’s so many ways this is essential!
At the moment I solve this by using a sort order to push the most likely selections to the top of the list. But given that the sort order isn’t applied unless you actually click the button, this creates quite an overhead. For example, when I add a user it’s probably because I want to immediately add a hire for that user. So I want the user at the top of the list, which is where my sort order would put it, but first I have to go into the base and reapply the sort.
