I’m trying to set up a Cross-doc Modify Row action, but I’m completely stuck.
I have a Doc A with Table A and a Doc B with a Table B. I want to merge the data from A & B to an Overview Doc with Table X.
When data first gets entered in Table A, I can push the data to Table X via a Cross-Doc Add Row button in Table A. So far so good.
But now I also need a Cross-Doc Modify Row button to push changes made to a row in Table A that was already created in Table X via the Cross-Doc Add Row action. For that to work I need to specify which row needs to be modified in Table X.
I already added a column to Table A with it’s UID (generated via Split(thisRow+ "", "/").Last() which i found in this forum, thanks! ). When the Cross-Doc Add Row is executed it also sends the UID from Table A to Table X. I thought I could come up with a way to reference that UID in the Cross-Doc Modify Row formula, but alas I can’t get it to work.
I also thought of trying to push the rowURL from Table X to Table A once the row is created in Table X via the Cross-Doc Add Row action so I can reference that, but I can’t get that to work either.
What am I doing wrong here? Is there a way to fix the formula or is my method wrong to begin with? I’m trying to “push” changes to Table X, but maybe I should “pull” from Table A? (I don’t think so?)
I’d appreciate any pointers as I’m super confused rn.
Yeah I get that cross-doc is not exactly Coda’s finest… But I don’t see another solution for my needs.
Again, my needs are different tables in different docs (Table A, B, C, etc.) that need to be merged in another Main Doc / Main table. The reason for the different docs/tables is that they are operated by different users (customers) who are not allowed to see each others data. I can’t think of a way to do this in 1 doc with different views.
Your solution looks decent to me though. Do you think it’s unstable? / Would you recommend me not using it? It would be a critical part of our company work-flow, so I need it to be as solid as possible.
