Create new record in Parent Y Table. Then create new record in Child Table, which then automatically creates new record in a different Parent X Table. Possible?

  • 0
  • 1
  • Question
  • Updated 3 years ago
  • Answered
To clarify - There is one child table that has two parent tables.  First we create a parent record in Table X.  At any point in the future we create a child record in Table Y which is related to Table X.  The moment when this child record is first created QuickBase would automatically create a related record in Parent Table Z based on one or more fields from the other two tables.  Is this possible?   

I attempted to provide a more detailed and specific explanation but it is quite complicated.  So I guess I'm just looking for a generic 'How to' answer.  

Photo of Robin CC

Robin CC

  • 200 Points 100 badge 2x thumb

Posted 3 years ago

  • 0
  • 1
For now, I would just put a button on that child record for the user to click to create he Parent Z record if it does not already exist.

When Webhooks (a new feature demo'd at EMPOWER 2016) are out of Beta and into general release later in the fall, then you will be able to go back and further automate it.
Photo of David Maskasky

David Maskasky

  • 100 Points 100 badge 2x thumb
This is possible now.  Although, whether you can define this as native is another discussion.  It is possible in Quickbase using Dan's Image Onload Technique to add javascript to your form.  From there, you can implement (Dan again) his Save And Scooby Doo technique.  This technique is used to capture the record id of the record you are saving.  Now that you have the record id, you can use ajax to add a child record and relate it back to this parent.

In a more complex example, I have implement this for a customer.  The customer wanted their users to save document their work in Excel instead of in Quickbase.  They needed the records in these Excel files to be routinely imported into Quickbase when the user was ready.  We didn't want to give them the ability to use Quickbase's import feature since it would be dangerous as they could accidentally write to the wrong field.  Instead I gave them an import table where they can add an import record.  I put a drop zone for drag-n-drop functionality and implemented Save And ScoobyDoo in the form to capture the record id on save.  When the import record was saved, it would capture the record id and send it via a CORs request to my Django web service.  My web service would then download the attached excel file and read it using Microsoft's API.  It would respond to the client with a matrix of their data.  The client would then asynchronously import this data into the target table.  Ta da!

Ok, I realize this was long-winded, but the point here is that this ability exists today.  For that matter, I can't think of anything that webhooks brings to the table that isn't already possible.  Finally, webhooks are great for developers but not so great as a no-code solution.  In other words, you will need a developer either way, but at least rather than wait for webhooks, you can solve this problem today.


David Maskasky