Create a new page everytime you fill an entry in a column

Is there a way to create a new page every time you add an entry in a column? In my case the column is for projects. I want to create a distinct page/ spreadsheet for every project number entered that can be individually customized.


What’s fairly easy is to create a page that consists of one widget (e.g. a narrow single-column table, or a single-record card view) that serves as a selector for a project, and several other sections that show project details and related records. That way, you use the selector widget to pick the project, and use the rest of the page to work with the selected project.

What this setup doesn’t do is let you individually customize what this page looks like for each individual project. It can show different data, it could have different colors (using conditional formatting), but it wouldn’t have different layouts.

What do you hope to customize that should differ across projects?

I guess the look of each project page doesn’t need to be customized, just the data. I want to be able to track tasks, sub-tasks, and sub-sub-tasks that may be different for each project.

I work for a small mechanical engineering firm. Something like a car motor project would be split into 5 different assembly tasks>25 sub-assembly tasks>500 individual parts. Each project has a lot data in many different spreadsheets. I was thinking organizing each project as it’s own document at first, but I’m not sure if you can link different documents together to get a master list of all projects

I’m not sure how to translate this setup into grist.

Hello @Electric_GT_ERP

How do you think this can help solve your issue?

Also, take a look at this template, which might give you ideas for a setup: Custom Product Builder.

The page I linked to allows configuring how many of which component go into a product. Another page allows listing how many of each product to add to an order, and then calculates how many of each component are needed for the order, and the total cost.

It’s not quite what you need, but I think it’s similar types of relationships, and shows the benefit of organizing such data in a single document.