Access a table in another doc

1

Hello guys,

I’m trying to figure out what’s the best setup for this scenario:

  • Table A inside doc A accessible by the sales team.
  • Table B inside doc B accessible by the tech team.

Table B has a column that gets the customer email from table A.

This is what I tried so far:

1/ Create table B in doc A, and sync it to doc B: in this case the tech team can’t edit the table, unless they have access to the source doc
2/ Sync the table with Cross-Doc pack: in this case the sync is only once a day (once per hour if I upgrade to Team, which is still not ideal)

Am I missing something?
Is there a better approach to this scenario? (maybe with automations?)

Thanks!
Daniele

2

hi @Daniele_B ,

For the moment there is no easy solution for this tricky problem. While we are waiting for cross doc with 2ws for makers without access to the source doc (doc B people needing doc A info) there are few options.

webhook logic may help you out in this scenario. Although I created a webhook pack and found a way to make it 2WS (edits on both sides come through fast) I don’t consider it as a general good solution. It is not intuitive enough for non tech users and Coda is all about empowering non technical users in my opinion.

So for the moment you may need to create a third doc where the main table lives and give A & B people access to it and then share cross docs in doc A and B of this table in doc C.

The team plan syncs once per hour or you refresh manually, I know this not great, but maybe good enough for the time being.

Cheers, Christiaan

1 Like
3

Thank you very much Christian, you’re always precious! :slight_smile:

The webhook logic is in-line with the automation I was thinking of.
I found your CodaExpert_Webhook pack, besides the technical setup are there other issues that don’t make it a good solution?

Thanks

4

hi @Daniele_B ,

merci for the compliment, I’ll try to be as helpful as I can
the webhook logic is for free and works fast and is technically speaking easy to implement.
It is only that people not familiar with this type of set up, may dislike it and when people add columns, you have to add that in your button or automation as well and when they delete columns the set up breaks as well. These are the inconveniences of a more technical set up.
I use it myself as you can imagine, but I try to avoid it with clients to keep my client work 100% coda supported (so when they contact the helpdesk, they only handle coda stuff, not my pack for example)

courage!, bàt, Christiaan