How can connect two tables with two different sheets?

I need an help. I saw all coda’s channel YouTube video but I don’t find the solution…
This is an image that recap the problem.

I need that a specific value (sheet 2 - Table 2) be inserted in Sheet 1 - Table 1 - Row 2

Sheet1 is an operative sheet, where I add values, Sheet1 is a “Dashboard”, an hub where, when I open Coda, I see the recap of all my sheets (goals, tasks etc.).

Someone can help me?

The problem is that your sheet 1 and sheet 2 are in different documents. Documents are like Apps on a phone. For the most part, your apps on your phone are separate entities that don’t talk / interact with other apps.

There is some overlap (For example, if you are on Instagram, that app has, if you allow it, access to your photos in order to post photos).

But for the most part, you should assume separate docs live in their own universe without talking to one another.

So your solution is to bring those sheets/tables (we call them tables in Coda) into the same document.

Or, if you need them in separate docs (which you really shouldn’t), you can use cross-doc to bring one table over into the other doc.

Thank you for your response, @Scott_Collier-Weir. In your view, what is the best approach for creating a dashboard in Coda that summarizes the work you do?

When I access Coda, I want to immediately see an overview of all my documents, including goals, tasks, etc. Clearly, it’s not feasible to compile all my data (financials, tasks, goals, etc.) into a single document as it would become too cluttered, disorganized, and difficult to manage.

Hi Roberto,

Welcome to the community, glad to have you.

I think you will be surprised at just how many different pieces of information you can work with in a single, well designed doc.

At (SAP implementation and support) work I have a single doc to manage the functional design documents, the technical designs, enhancements, configuration, project plans and meeting minutes for product costing, cost centre accounting, general ledger, banking customers and vendors. Also the research into new implementation topics.

It is much easier to split apart a doc, than to convince. So I always suggest to people to have a single doc, until they absolutely have to split it. Usually it is for authorisation purposes. I have had ONE example due to size, I was moving towards hundreds of tables.

But, it’s just a ramble,.
Rambling Pete

1 Like

Thank you @Piet_Strydom ,
Unfortunately I disagree. Comparing it to storing all files on a computer desktop, no matter how neat, isn’t an ideal organization strategy, in my view.

For every client or project, I maintain a dedicated folder with a systematic arrangement of data. I ensure that different categories like accounting, graphics, and reports are not intermixed.

Similarly, in Coda, I aim for a comparable level of organization.

Returning to the main point, I believe I’ve found a solution. In Coda, each ‘document’ (which I equate to a folder) allows me to create multiple interrelated pages. This structure seems to align with my organizational preferences.

Perhaps that’s what you were suggesting :sweat_smile:. I’m just beginning to explore it now and am still in the process of understanding how it works.

Yip. :wink:

Coda works VERY differently to traditional documents (Word, Excel and Windows folder structures) than what we are used to. I would sincerely recommend that you be prepared to build some prototypes that you are willing to throw away for a few months. It WILL be a very worthwhile investment of your time.

Especially since you are talking about a relatively complex setup:

Explore the functionality around tables and their views, including the very strong concept of canvas columns. Personally I have gone to a very extreme use of tables, with views to group things across different dimensions. (Tasks, design docs, training info, testing info, etc)

It’s just a ramble,
Rambling Pete

Sometimes it is better to show than to explain:

Enjoy, :wink: