Hello everyone. I’m trying to create a form for use in collecting responses by sharing the form via a generated sharing link.
My question is — is there any way to fix any of the following (somewhat lackluster) things?:
In relation fields . . . the utter lack of any ability to filter/sort the universe of entities available for linking.
In relation fields, with respect to the entities available for linking, the total absence of the usual visual appearance of such entities (e.g., the lack of color, database icon/color, avatar, etc.).
My many thanks in advance for any insights on this. Thank you.
No, but relation filters on form view is a feature in the backlog
If you’re filling in a field on a form, there should only be one type of entity to choose from, so not sure why you’d need to show database colour :-/
If you mean showing information other than just the name field, then no, but again, there is a feature in the backlog to provide more details of entities in drop down lists (not just for form view but other places as well)
Thank you, Chris. I think this is a pretty crucial functionality, and I look forward to it (hopefully) being implemented sometime in the near future!
You’re right that there’s no need to show an entity’s database color/icon in this context, just like there’s never any such need to show an entity’s database color/icon. In my view, the showing of the color/icon here in this context — just like in any other context — makes everything look better and more visually appealing/categorized/cohesive/professional/cool, and therefore also more functional. I wonder: why do/should entities available for relation/linking in form-view appear as antiseptic, boring, unpolished, basic, anemic, black-and-white things rather than in the color-coded, cohesive, awesome way in which they organically appear in literally every other Fibery view?
Well actually, there are many places where it’s possible that entities from multiple databases can be visible at the same time (list, board, grid, timeline, calendar…) and so distinguishing them by db is useful.
My point was merely that the picker on form view is not one of these such situations.
No, but relation filters on form view is a feature in the backlog
Is there any update on this? I couldn’t see it on the current roadmap.
Currently forms are mostly useless to me because I want to add entities with relations and there’s still no filtering at all. It seems their current use case is mainly to create entities with no relations or relations with short lists that don’t require filtering.
It’s not the end of the world as we can add things in other ways, but more usable forms would be great.
(Apologies for necroing this post, I checked the rules and couldn’t see anything against it so I hope that it’s okay here.)
I may have a workaround for applying filters on forms for the form view. Will see if it works. Basically I want to add a table in between. For example, if you only want to add Projects with status = “active”, you make an ActiveProjects table and you create a Rule that adds an entity to ActiveProjects when you set a Project to “active” and when removes it again when you set it to “inactive”. With a bit of manual work this should work but I realize there are a few loose ends to figure out. But if I am too busy to do this then you can get it working quicker than me feel free to share it (and let me know how you made it work, you can even share an example Workspace as a Template that is what I will do when I have time).
Anyways my vote for Relational filters for forms still stands, it is very valuable to be able to filter easily.