Could there be an option to define during column “link to table” creation if the field should accept many or just one reference row from another table?
I have a use case when only one relationship makes sense and I wouldn’t like to relay on users to remember that.
1 Like
Hi! I would be happy to see this feature in Baserow because so often need to make sure a linked field only has one record. For example, user by mistake can put many customers on one order or add few payments to a single transaction.
For instance, I have a table with financial details in Baserow. To make sure there’s only one item linked, I created an extra field that checks how many items are linked and shows an error if there’s more than one)) This method, though, makes everything more complicated. Adding a limit to the number of connected elements would greatly simplify the complexity of the tables.
If this will be implemented, it surely should be optional (f.e. one additional checkbox when creating the link-to-table field). In my use case I have a table with link-to-table field where I need that it can accept more than just one item from linked table.
So yes, this feature can be useful, but should be made as an additional option.
Hey @Alexander and @marcus, please use this issue Limit link to table amount of relationships (one to many) (#403) · Issues · Baserow / baserow · GitLab to track the progress.
Since this feature has already been accepted, could you please copy and paste your comments about it to GitLab? This way, we can ensure that the developer who picks up this issue will see and consider your suggestions. Thank you! 