Just thought I'd post here to say that I have just starting using Webhooks and they do provide some interesting solutions to previous QuickBase Limitations.

  • 0
  • 1
  • Question
  • Updated 3 years ago
  • Answered
Photo of QuickBaseCoach App Dev./Training (Mark Shnier)

Posted 3 years ago

  • 0
  • 1
For example:

One Quotation has many Quote Lines and the need is to sequence the order lines from 1 to whatever.  The previous solution would be to do a Summary Maximum or count of the line numbers, lookup back down to the Quote Lines Table, and then use a snapshot field.  But then the user cannot Resequence the lines.

With a Webhook, you can still do that Summary Maximum of the Line # and a lookup down to the Quote Lines Table.  Then have a formula field of the [# of Quote Lines ] + 1, and then have a Webhook edit the new record when created to apply that [Next Line#] into the Line # field.  The nice thing is that the user can grid edit the Quote lines to resequence if they like, but in general the Quote Lines will auto sequence like 1, 2, 3, 4 , 5 ....
Another example was more crazy.  The need was to build a complex app  for Managing "Opportunities" but a requirement was that the Opportunities needed to be able to be copied along with all their children and grandchildren.  As you may know, Copy Master Detail does not work if you have "Looping Relationships", but I needed a Looping relationship to get some lookup fields way down to the end of a series of complicated relationships.

So I made a saved import and then every time an Opportunity is edited, I am copying across selected fields from all records in the the Opportunities table to the Opportunity mirror table by triggering API-RunImport when an opportunity is added or certain fields are edited.
Photo of dwhawe

dwhawe, Champion

  • 886 Points 500 badge 2x thumb
I have been using PHP with a Cron job to activate Table to Table merge.  Due to the nature of the beast in some cases, I have the Cron firing off at 30 minute intervals.  The purpose being to catch any new records in the master.  That causes unnecessary API calls at times which can impact performance in a single thread environment.  With Webhooks, the activity only happens with a new record.

It also makes it a "native" solution.