I have table A that has embedded table B. Once a new record is added to table A then a pipeline is ran and adds new records to table B. However with using pipelines the user needs to save and keep working on the form for table A and then refresh a few times for all the pipeline records to show up. Is there a better way to do this?
Qrew LegendCan you tell us how many records are being added as Child Records?
It's about 23 records
Original Message:
Sent: 07-13-2023 13:07
From: Mark Shnier (Your Quickbase Coach)
Subject: Using pipelines to create records-slow to create
Can you tell us how many records are being added as Child Records?
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
Original Message:
Sent: 07-13-2023 12:17
From: Catie Bruno
Subject: Using pipelines to create records-slow to create
I have table A that has embedded table B. Once a new record is added to table A then a pipeline is ran and adds new records to table B. However with using pipelines the user needs to save and keep working on the form for table A and then refresh a few times for all the pipeline records to show up. Is there a better way to do this?
------------------------------
Catie Bruno
------------------------------
Qrew LegendThere's nothing we can really do to make the triggering of the pipeline quicker. However it appears to me that the pipeline steps Ron at a rate of about five per second. So if you're adding 23 records it could take five seconds for sure.
Is the source of these child records from another table? For example are these standard tasks that get added to a project?
Webhooks are an option as opposed to Pipelines. You can do an API_ImportFromCSV or use the REST API to configure your records for creation. Webhooks are typically faster than pipelines for simple direct tasks like this, but they're a little harder to configure than your pipeline given the lack of a visual builder.
