Right now you canโt link to views or subtypes (selected candidates).
It is a shame that is the state of affairs.
Regarding this point:
You could create a second table for your selected candidatesโฆ
(Lets call that table โAโ)
โฆfilter + copy & paste those people (thatโs only 1 action)โฆ
(Lets call this table โBโ)
and create a link to the new tableโฆ
(Lets call this the โfiltered promptโ)
What happens when the user updates table โAโ? Wouldnโt the user now have two tables to maintain? Maybe that will help in the OPโs situation. But for most users, wont that create double the amount of work in terms of maintenance? The โfiltered promptโ will be obsolete as soon as a row gets added to table A without adding it to table B.
Your suggestion might work better if there were a way to create a query type of tableโฆ (going do research to see if that is available in airtable)โฆ
Nice![quote=โTuur, post:4, topic:1408โ]
The query solution is not available either, which is why Iโm working on a custom Airtable scripting web service.
Looking forward to thatโฆWould be nice if the โlink to recordโ pop up could use your service! :grinning_face_with_big_eyes:
There are many use cases for this - and the feature is required for both normal views and views to be published on a eb site - for exampleโฆ
In a leave request form you would want the employee to be able to say which type of leave they were asking for from a table of absence types. However, you would only want the to be able to request absence types identified as โrequestableโ.
At the same time, HR users would need to be able to enter leave records for leave types which are not requestable.
All, how can I limit the dataset presented in linked field โdrop-downsโ/โpop-upsโ to external form users?
Right now I have a form that allows you to select an employee via field linked to a separate table. And though I can sort that table to move inactive employees to the bottom, I cannot hide ex-employees. For that, it seems that the Linked Field needs to honor filtering, or Link to a specific viewโฆ
Can this be solved via Lookup? Iโve poked at it; but not cracked the issue.
Itโs not possible (as far as I know) to limit a drop down or linked field - a workaround would be to have the key field as a calculated field with an if test - and if the employee is a leaver set the value to say โdo not useโ or something otherwise set it to the employeeโs name.
Ideally, of course, we would all like to be able to filter it!