please make sure you dont have sharing via link enabled on your doc - and if it is not shared there - please get in touch with us via in product chat - we would definitely want to see what is going on there.
Hey Krunal ! this was SO Handy . Thanks a lot for this insight. Game Changer
Any idea on how to do the same with the Open Big Cell Note Function with a button ?
The normal function would be this 
OpenWindow(Concatenate( Url(thisRow),"&columnId=c-ZK6pMUygtu&modal=true"))
Hi @Krunal_Sheth 
do I need to add for each layout a new view? As I understand, and what happend now with my doc, that I reached the size limit as I have like 10 different layout I want to use. Any thoughts on this? Thank you very much 
Hi @thomas_raizedai,
If you’re looking to have a different display show for each scenario, then you’ll need to have a view with each display to point to. This workaround is using the view as the identifier to find the display. It would be nice to be able to set a custom layout without the need for the view, but we don’t have that at the moment.
1 Like
Hi!
Any idea on how I can create a button that would open a link from an adjacent lookup table?
Here’s my setup :
- Test projects
- Test tasks with lookup on test projects
Here’s my goal
- add a button in test tasks that would open the related project
thanks in advance for your response !
Activate(thisRow.project)
This should probably be added as an option in the button dialogue’s “Action” menu.
3 Likes
Thanks @Ben_Lee for your feedback, even during weekend, much appreciated
Question: what then counts to a doc size, having various views from a table? e.g. each column I display? I have a table with around 1000 rows, but 30 views of it which the API tells me 131% size
super useful, in particular now that is has the layout choice option.
Thank you Coda!
1 Like
Sorry, if I am being thick, but haven’t we had OpenRow() for a while now ? what changed?
Despite its name, the viewOrLayout parameter only accepts views - thus we still need to create views for no reasons other than to have some specific layout we need opened by a specific button.
Why can’t this parameter alternatively take the name of a layout to open?
2 Likes
Yes, I was confused too. I thought this was an update, but the only change is the interface in the button menu.
2 Likes
Sorry for the confusion, not a new feature! I just wanted to close the loop on this old thread.
1 Like
I really want to be able to open a row in a VIEW of a table, from an arbitrary place. Is this a possibility yet? If I use the action OpenRow(), then it opens the row on the current page.
So I don’t fall into an XY problem: Notifications in Coda are clickable, and they take you to the base table (for me, in a hidden page!) – it will not take them to a view, even if the notification was generated from a view. This confuses my editors.
So I want a button that can take them to a view of the row in a non-hidden page, the place they should be working. The closest I can get is to open a url go to the view on the page I want, but I haven’t been able to actually open that row in that view on that page.
Any tips?
Hmm… you have to reference that specific row using “@”, but if you put the button on page, then the value will be a static one. In regards to base table, you can create a general layout for the base table with only specific things available, then create a view of that base table “EDIT DB Base Table” and expose in there all columns for when you need to do admin/doc maker work on all columns.
This way if someone end up in your base table, they will see just a few general columns that they will see in every other view.