A key issue with connected fields is that you have no way of constraining a user from selecting anything in a pipe or database. In many situations you want to:
- Pipes: Only allow them to select cards at a stage in a pipe (e.g. DONE)
- Database: Only allow them to select where a Field = certain value (e.g. a category value)
This will make pipefy a lot more scalable for higher volume use cases. Otherwise the user has to do a lot of thinking and searching through many entries. I don’t believe there is any hack around this right now that makes sense.
This is also very typical/ standard functionality elsewhere. So I was surprised not to find it given that in general pipefy is more flexible than other similar platforms.
One hack I thought of was creating multiple databases instead of one (e.g. one database by category) - however that makes it a lot more complicated/ less well organized.
I’ve seen this requested/ discussed in other areas of the community - example here: