I would prefer Multiple Reverse Lookup columns for additional flexibility, but with a twist.
Can’t it be both?
By default Coda can create Paired Lookups.
If a user needs additional Reverse Lookup columns, these columns can be created by:
right click on the Paired Lookup column header → select something like “Insert related Reverse Lookup column”.
Same as you can do with “Insert related column” for a Lookup column now.
And I strongly disagree with @Paul_Danyliuk that Coda doesn’t need this feature. I think it’s one of the top missing features that hold Coda back. Paired Lookups will make Coda so much easier to use, and docs will feel much more like real apps.
I greatly appreciate Paul’s examples and help in this community, but much of the functionality in some of his examples (like Best Practices Showcase (8 hours of videos & a doc)) is “hardcoded” and relies on buttons. And often you can’t drag and drop rows. Maybe sometime it’s good. Paul wrote it’s intentional:
If that’s what some docs benefit from, people can continue creating them the old way.
But many of us and our docs will benefit greatly from bidirectional Lookup columns.
Do it, @Ben_Huynh! 