How can I use a button to create a new section?

I am trying to use a button to do two things:

  • add a row to a table (duh, got this)
  • create a new section/ page with the name of that row

I’m not sure if a formula can do this. My goal is to be able to use a button to create a new page which is referenced as a new row in a table. Does that make sense?



Hi @Russell_Jones,

Welcome to the Coda Community!

We don’t have the ability to create a new section with a button. The question definitely makes sense, and there have been a couple conversations about this, but we’re not sure what the full solution is just yet. It’s noted and discussed though.

1 Like

Thank you for the quick response! Much appreciated!

Maybe we can put our heads together to figure out a solution? I am so new to Coda so maybe I’m not quite thinking with full knowledge.

We are trying to imitate Jira/ Linear. In other words, we want to be able to create a project/ page, wherein we will add a table/ database, where each row links to other pages/ sections.

So our goal would be to be able to create tables/ databases where each row is actually a link to another page. Does that make sense? Is there a simple, automated way to do this?

+1 that a button or formula to create a subpage would be very useful

1 Like

I haven’t checked Coda for an updated list of hidden formulas in a while, but there is one you can still use:

DuplicateSection([Section reference], "New name")

with two more optional parameters to control whether the tables and the data are copied as new tables or views of the original table. So you can have a template page and use this action to make copies of that page.

The action works, and it is also sufficiently documented, so I believe aside from the old name (sections are now called pages) it is rather stable. However, be advised that it is a hidden experimental undocumented formula and it may break or be removed at any point, and potentially break your doc. So only use if you assume all the risks and know what you’re doing.

In general, I advise to only create new pages when you actually need a different perspective into your data (e.g. a differently grouped table). If your intention with separate pages is to show different subsets of data (e.g. have a page per Project each showing a differently filtered view of the same Tasks table), consider using a single page with user-specific filters instead.

That is, unless you’re simply building a wiki with pages to fill out with text, not data. Then make pages to your heart’s desire.

Also, re original request. Even with the DuplicateSection() action, it doesn’t return a page reference or a link or anything that you could automatically put into a table of links. You’d still have to enter those links manually. You can use e.g. this trick to populate the table of page links more easily.