thisPage object (as thisDocument or thisRow)

[Blaise_d_Estais]

Have a thisPage object.

Example use case :
button in a table with multiple views in multiple pages,
Action -> openlink(“coda.io/” + thisDoc + “/” + thisPage.slug + “/” + thisRow.rowID + “modal=True”)

I simplified the code, but you get the idea, it opens the modal view of this page.

[Colin_Nickerson]

We would like this as well.

Our use case has to do with template pages that display various tables for a particular topic. The topic key is usually the page slug.

We currently need to manually adjust the filter of a half dozen tables every time we create a new page using this format. We could instead have a template page that would fill based on its page slug reducing the work to almost nothing.

[Paul_Danyliuk]

@Blaise_d_Estais — while I see how thisPage could be useful overall and how it could offer a more convenient way to do what you need, FYI here’s the solution that you can use right now:

Mega trick: Different "Expand row" layouts for the same row

Most likely you’re familiar with “Expand row” feature that lets you see a popup for a row by clicking here: [image] [image] And perhaps you know the action Activate() to open that popup programmatically with a button, or at least used the “Add new row and open for editing” checkbox. And also you may know that you can configure row details popup layout just like you can edit the layout in Detail view: [image] What you may not know though is that you can configure this popup’s layout indi…

@Colin_Nickerson in your use case what I’d do is have only ONE page with a view with common settings (and not a separate page per e.g. topic), and implement user-specific filters of a sort (e.g. so that every user can individually look at a different topic, all in the same page)

[Video] User-specific filters (each person tweaks controls independently)

Yet another question that has been asked and answered so many times: How do I let multiple people use the doc at the same time and change filters just for themselves? Time to have the ultimate answer in one place. I recorded the video explaining how to do that using a helper table. I call this approach the Flows Table pattern. [Coda trick: User-specific filters] TL;DR: Create a table where each row is linked to each Coda user. Set up its columns to act as controls (checkboxes,…

[Colin_Nickerson]

Thanks for the suggestion Paul, but in our case these are pages of documentation with common attributes like related tasks, documentation status etc.

The page content varies from topic to topic. Also, the pages of documentation are referenced elsewhere and having a link to a single page that uses a filter isn’t sufficient.

At first, I tried working around this by making a documentation table and using a detail view … but inserting images, videos, and other media was too difficult. I also was unable to use a page outline which is important for longform docs

[Colin_Nickerson]

@Paul_Danyliuk you seem to hack around things in Coda a bit so I was curious if you ever looked into JS injection to add custom formulas to coda? We really need a proper thisPage as we have 40 pages with a common header, unique body, and common footer. Every time I add a new page I have to create new header and footer view but a thisPage function would eliminate all of that.

I have raised this with support but I understand that their priorities align more with average need across the community so I want to start to look into hacking in support myself for our team … but not sure if it is possible.

Because coda runs on client I assume there is a way to add a custom formula … perhaps getting the URL of a view and parsing out the page from it in the url would work … hmm

[Marko_Petrovic]

thisPage is something that should really be added to Coda. One use case that comes to mind right away is for wikis and knowledge hub. You could easily see who and when updated the page last time (as a mini automatic version control). There are many other ways this could be used, its just something that comes to mind as we run into the similar problem in knowledge base we are building for us.