Select from different libraries for link to entry field.
Rather than selecting a single library from which a "link to entry" field can pull from, this would allow you to select from different libraries for each entry link.
I'm creating a cocktail recipe list. I currently have a link to entry field for my ingredients that reside in a separate "ingredients" library. I would love the option to link each ingredient to separate libraries (one for juices, one for spirits, one for syrups, etc).
Christian Burkhart commented
You're right, in that case, I could do as you described. It was perhaps not the best example.
Consider this example....
I have these databases:
- POS Items
- Cocktail Recipes
I have link to entry fields in the POS Items database for the other two database. So, I have these two fields:
- link to Inventory
- link to cocktail recipes
Tim Leung commented
I am not sure this is necessary. For instance in your example, instead of having multiple libraries each representing one type of ingredient (juices, spirits etc.), you can half one ingredients library with a single choice field called "Type". Can you clarify why multiple libraries of ingredients is needed?
Faouzi Tlili commented
I d really like for this feature to be implemented, I'm going around this by creating a library called "list" containing as fields only a title and links to entry for all the libraries in my system, then i make a link to entry for the library "list". But it gets very messy, a generic link to entry would be amazing