I’m building a resource catalogue which will be publicly accessible. One feature I was happy to get up and running was the ability to take input from the public for new entries in the database, via a form.
The form currently submits to a “holding” table for review. If we accept a suggested entry, we’ve been manually copying the information over to the appropriate table (we have 3 total master tables which feed around 20 views). Then I delete the entry from the “holding” table.
I’m looking for a way to streamline this “approve & move” process. Ideally I’d be able to check out a suggested entry, fill in any missing details, & send the entry to the right table & view (views are driven by column filter).
I’m not a coder and I’m probably describing something very basic but I don’t know where to start in terms of looking up the right formulas etc. Thanks in advance.
Your holding table pattern is a great way to handle this situation, so you’re already on the right track. Are you always sending to the same destination table? Or are there different tables you might decide to send the info to?
(The fact that you have a select dropdown makes me think there are multiple possible destinations, but the fact that the data seems so uniform makes me think that you should have only one destination table. If you have multiple destination tables, can you say a bit more about why?)
Hey thanks for validating I’m at least on the right track.
Good catch on the data similarity thing; it’s a little misleading in this screenshot since those happen to be several similar entries. There are several tables in the project; one big table proved to be infeasible because of fundamentally different data and display needs (i.e. it was more than just a simple filtering challenge).
Ok cool, if you’re sure.
Here’s a demo, can explain more tomorrow. Open this in Coda, Copy the doc, and then you’ll be able to inspect the button formulas.
Thank you Nick, this is totally amazing and exactly what I want. Super appreciative you rigged up a whole demo for it.
FYI, and maybe this is old news to power users, there is a native Notion feature that does what I’m looking for out of the box. Just noting that this would be an as-good or better solution for my case.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.