Scott! This is so awesome, thanks so much for sharing this. Im curious if you have thoughts on a workaround or if there's an elegant solution based on a use-case I'm working through: I'm using this marvelous hook/catch feature to feed into a central table, but what we *really* want to do is hook from multiple tables into one catch table (we'd like to track projects from various teams (hook tables) in a single tracker (catch table)). My hypothesis, I think, gets snagged on the RowID filter in the catch table-- since each RowID in each of the various hook tables create duplicative "unique" RowIDs, the filter wouldn't actually be able to distinguish them. Buuuut, I wonder if for each table, could I assign a value ahead of the RowID (i.e. A1, B1, and C1 for tables, A, B, and C, rows 1)? Would love to know if it's possible to connect multiple hook tables to a single catch table, whether by my hypothesis or something else entirely!
Oh you can for sure send images and attachments, but the VALUE you need to send over in your button is the codahosted URL of the image/attachement. There are many ways to find/unearth that, but the easiest way is using the button action in the ImageURL pack which is free in the Coda gallery
Hei!. I am trying to use this method to sync a like button from the second document to the first document. So that I can have external users to my organization see some content I chose to display and vote on ideas without letting them into my working document. However, I figure the like button actions are not being sent back. Any clue as to why this happens?
Great tutorial! Is it possible to sync buttons too? There might be a better way for what I'm trying to do but I have a master doc of jobs that a few people will be using/updating at various job phases. Some of the activities involve answering questions from a checklist and uploading a picture (if applicable) per question. When that's done the user submits a report (button) that hits another button to upload photos to google drive (I have this working). The problem is I have 160 jobs with about 50 questions per job. Factor in photos and column buttons for responses (yes, no, minor, moderate, etc.)...It's getting to be a big doc and causing memory issues on the mobile side of coda. I figured I could break this big doc into smaller docs with 2-way sync..or is there a better solution?
Specialized Use Case: I have a Table 1 (let's call it 'Today' that refreshes nightly. Before it does, I want to copy its data over to my Archive folder so that the data isn't lost. So each day's Today table would get copied over to Archive, and then refreshed to give me a fresh Today. I anticipate I can use your webhook for this, but the scenario changes slightly because the rows I want to sync in my Today table will always be the same rows (refreshed values each day), but I don't want them updating the values in Archive; rather, I want them added as a new row in Archive. Is this possible?
Yeah for sure! In my video the [Catch] automations action uses a "add or modify" rows action. You would just want to use the simple "addRows" action instead of the modify one
Notes: Worthless. Why? "No need for CrossDoc pack" and then a minute later still uses a pack, but just one made by him. Do a vid on crossdocs, not this.
if I have 3 table with same columns . Can I merge it into 1 table (Master)
Thanks so much for sharing this with us. What would happen if a row were deleted though? Would it just disappear from both tables?
How do you use "hooks" to fetch data, and put it in a row. And then use keywords to minimize your pick lists
Been looking for that CODA row.ID(thisrow) in Notion for 3 years.
Scott! This is so awesome, thanks so much for sharing this. Im curious if you have thoughts on a workaround or if there's an elegant solution based on a use-case I'm working through: I'm using this marvelous hook/catch feature to feed into a central table, but what we *really* want to do is hook from multiple tables into one catch table (we'd like to track projects from various teams (hook tables) in a single tracker (catch table)). My hypothesis, I think, gets snagged on the RowID filter in the catch table-- since each RowID in each of the various hook tables create duplicative "unique" RowIDs, the filter wouldn't actually be able to distinguish them. Buuuut, I wonder if for each table, could I assign a value ahead of the RowID (i.e. A1, B1, and C1 for tables, A, B, and C, rows 1)? Would love to know if it's possible to connect multiple hook tables to a single catch table, whether by my hypothesis or something else entirely!
whoops, never mind-- looks like a nice little concantenate was the answer for the filter here! :D
Awesome, got the template. How would this work with attachments and do columns have to be same type to sync? Thanks
Oh you can for sure send images and attachments, but the VALUE you need to send over in your button is the codahosted URL of the image/attachement. There are many ways to find/unearth that, but the easiest way is using the button action in the ImageURL pack which is free in the Coda gallery
@@thecodaguy Thanks a lot!
Hei!. I am trying to use this method to sync a like button from the second document to the first document. So that I can have external users to my organization see some content I chose to display and vote on ideas without letting them into my working document.
However, I figure the like button actions are not being sent back. Any clue as to why this happens?
Are the comments from the rows carried over to another doc?
Great tutorial! Is it possible to sync buttons too? There might be a better way for what I'm trying to do but I have a master doc of jobs that a few people will be using/updating at various job phases. Some of the activities involve answering questions from a checklist and uploading a picture (if applicable) per question. When that's done the user submits a report (button) that hits another button to upload photos to google drive (I have this working). The problem is I have 160 jobs with about 50 questions per job. Factor in photos and column buttons for responses (yes, no, minor, moderate, etc.)...It's getting to be a big doc and causing memory issues on the mobile side of coda. I figured I could break this big doc into smaller docs with 2-way sync..or is there a better solution?
Specialized Use Case: I have a Table 1 (let's call it 'Today' that refreshes nightly. Before it does, I want to copy its data over to my Archive folder so that the data isn't lost. So each day's Today table would get copied over to Archive, and then refreshed to give me a fresh Today.
I anticipate I can use your webhook for this, but the scenario changes slightly because the rows I want to sync in my Today table will always be the same rows (refreshed values each day), but I don't want them updating the values in Archive; rather, I want them added as a new row in Archive.
Is this possible?
Yeah for sure! In my video the [Catch] automations action uses a "add or modify" rows action.
You would just want to use the simple "addRows" action instead of the modify one
Notes:
Worthless.
Why? "No need for CrossDoc pack" and then a minute later still uses a pack, but just one made by him. Do a vid on crossdocs, not this.