Forum Discussion
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
------------------------------
There'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?
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
- HunterB2 years agoQrew Cadet
yes the pipeline records are being added to a different table than the one the user is currently in. I hope that answers your question.
Original Message:
Sent: 07-13-2023 13:15
From: Mark Shnier (Your Quickbase Coach)
Subject: Using pipelines to create records-slow to createThere'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?
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
Original Message:
Sent: 07-13-2023 13:12
From: Catie Bruno
Subject: Using pipelines to create records-slow to createIt's about 23 records
------------------------------
Catie Bruno
Original Message:
Sent: 07-13-2023 13:07
From: Mark Shnier (Your Quickbase Coach)
Subject: Using pipelines to create records-slow to createCan 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 createI 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
------------------------------- ChayceDuncan2 years agoQrew Captain
Are the records being created dynamically or are they a static list like set tasks? Either way - you can put them into a webhook to create them that way. I have processes that create upwards of 300-400 dynamically based on a template from different tables and typically it fires and creates them for the users to access within 1-2 seconds max.
------------------------------
Chayce Duncan
------------------------------ - MarkShnier__You2 years ago
Qrew Legend
It's possible to make the Pipeline run a bit faster by having the pipeline record the Record ID# of the trigger record in a special table with just one record in it.
That value would then be looked up own to the source table of the templated records to be copied.
You would then create a saved table to table copy to copy the records from the template source table to be children of your trigger record. Then use that lookup value from the special record to populate the field for Related Parent.
Then Pipeline would just have threeSteps.
1 Trigger on record created.
2. Write the Record ID# into the special record.
3. Do a Quickbase "Make Request" step to run thje saved T2T copy.
the syntax is easy foe that
https://mycompany.quickbase.com/db/xxxxxx?a=API_RunImport&id=10
(Method = POST)
The T2T copy runs on a blink of an eye, so this would be quicker to run.
Free to post back with any additional questions if you decide to tackle this methodology.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------