Comments in Cross-Docs

[Jerod_Wallace]

I am trying to create a table that updates from a master table using Cross-docs. The table updates just fine, but the comments in the comment section does not transfer over. Is there a way to do this??

Thanks!

[Admin_istrator]

Hi Jerod,

From what I know, cross-doc does not support transfer of comments. Only cell values can be transferred.

[Cliff]

This would be helpful to sync the comments. We have a table that is read-only (cross doc) but want to engage in discussion; however those comments should reside with the “master” table. Is there a workaround?

[Aine_Martinkenaite_Martyniuk]

Cross-doc comments sync is very needed feature. When could we expect an update. Or at least a formula, that could pull comments.

[Ryan_Polomsky]

I’ve developed a solution to run projects and tasks through Coda for my creative agency, utilizing one ‘control center’ doc and then unique, project-specific docs filtered by our project codes. It’s been a great solution overall, except that we’ve discovered comments don’t carry through in a sync.

Comments are getting lost, and this single missing feature will effectively kill my attempt to overhaul our workflow and replace Asana.

[Pablo_DV]

Yeah, I also hate that comments are not synced with cross-docs.

What you can do is disable the native comments and build your own commenting system with one/several tables, that you can make visible in all the relevant detail views and keep them synced across documents.

For example, in this post I created a simple commenting system

Visual cue for comments on cards

Hi guys, After a long search (or was it a chase?), I chose to venture into Coda for my small consultancy’s project and client management to see if I can build something useful. So I am just starting on this journey. Suggestion 1: Core requirement: Comment action visibility at board level I would love to see a little visual cue (they’re so important!) of new comments on cards in kanban view - see image mock-up sketch. I know Smartsheet has little red dot and Kanban Zone shows a nice red spe…

It will never be so nicely integrated as the native solution, but you have the power of coda to customize it and taylor it to your needs just like any other table.

Hope this helps,

Pablo

[Ryan_Polomsky]

I actually just resolved this problem, kind of by accident. I’m thrilled, shocked - all of the above.

I’ve always been syncing tables in cross-doc syncs. You can sync entire pages, and if you do that it will carry through comments.

[Pablo_DV]

If you don’t need to secure the data, syncing pages is a very good option.

Glad you found something that works for you!

[AJM]

True, but then you can’t use buttons unless everyone has access to the source doc

[rroman79]

exactly it would help a lot!!!

[rroman79]

I imagine how it hurts(( I faced the same frustration with my expectations. @Ryan_Polomsky have you found the alternative solution to share comments?

[Ryan_Polomsky]

Here’s how I’m successfully running Coda right now:

1. Internal Doc - Built on one DB, with pages/table views specific to each client/project for our own internal tracking purposes.
2. External Cross-Docs - Filtered by client / project codes, these are views and two-way writable with our Internal DB. Clients have full access to their doc, but don’t do more than comment.

The only real “break” I have between my internal and external docs are comments, whereas everything else syncs. This is fine for us. We run everything in two monthly sprints, and will have internal commentary within the Internal Doc where a dev gives me an update, etc. Only myself and my account manager generally communicate with the client in the cross-doc. Occasionally a dev might post an update / ask a question there.

We’ve so far been able to keep things untangled with our self-imposed governance, and clients who don’t care enough to try to tinker and are just focused on deliverables.