Cross-doc actions and solution structure help needed

[Paul_Danyliuk]

Hey @Thomas_Robbs2,

1. Regarding setting a reference vs string, here’s what worked for me:
   
   — sending an actual Row object for the Thing in your case.
   But if you can change your workflow where you can send a row ID / some other identifier instead, and do the lookup back to the Thing on the backend side, I think that would be more reliable than this undocumented behavior. It’s quite possible that this action isn’t even sending the Row object but converting it to text using some display value, then resolving that display value to an object on target table.

2. Yes, this is the right approach, although I’d say Coda isn’t really there yet to make it enjoyable.

Here’s a (better) guide to cross-doc actions:

In case you missed: 2-way Cross-Doc is here (sorta)

In case you didn’t notice it yourself, Coda cross-doc already supports adding, modifying, and deleting rows in other docs. This isn’t hidden functionality: it’s in the formula editor hints as well as the docs. However it seems it’s not quite ready for release too: the UI for setting this up without a formula is still incomplete, and the docs leave quite a lot for you to figure out on your own. Hence this topic to clear things up. Here’s how you add a row into a cross-doc table: [image] Fir…