I have a pipeline that is setup for our Accountant to run when they select a date range and client and then it will assign all the entries in the child table to the parent invoice record. To make sure the Accountant doesn't create the invoice until all records have been linked are there any 'fool-proof' mechanisms to show the pipeline is finished on the Parent Record? I have been testing and there will be instances where I have to refresh a few times before the the Total Invoice amount is correct.
------------------------------
Ryan Locke
------------------------------
Question
Pipeline Notification
+4This topic has been closed for replies.
+22I have two ideas. The first is I am guessing that your current pipeline search his records and then as each qualifying record is found it is updating the records individually. If if you were doing that, that is not really a best practice for Quickbase because essentially you are pinging against the QuickBase app many times as you do these individual updates.
A recommended practice is that you would create a Bulk Upsert, then do your search and then in a for each loop in the search you put records into the bulk upsert. Then at the end of the process you do a step called commit bulk upsert. The effect of that is that all the qualifying records will be imported all at once so it is basically impossible for your users to see half the results. They will see nothing and then they will see everything.
But, another thing you can do is to have a step at the beginning of your pipeline, or ideally if the pipeline is being triggered by a form of the URL button, the button can do this update to set a date time field for the time that the pipeline was started and then have the last step in the pipeline update a different field [Pipeline completed at] to the current date time. Then you could have an icon which displays a completed check box when the completion time is greater than or equal to the start time.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
A recommended practice is that you would create a Bulk Upsert, then do your search and then in a for each loop in the search you put records into the bulk upsert. Then at the end of the process you do a step called commit bulk upsert. The effect of that is that all the qualifying records will be imported all at once so it is basically impossible for your users to see half the results. They will see nothing and then they will see everything.
But, another thing you can do is to have a step at the beginning of your pipeline, or ideally if the pipeline is being triggered by a form of the URL button, the button can do this update to set a date time field for the time that the pipeline was started and then have the last step in the pipeline update a different field [Pipeline completed at] to the current date time. Then you could have an icon which displays a completed check box when the completion time is greater than or equal to the start time.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
Sign up
Already have an account? Login
Login to the community
Login with Quickbase US – quickbase.com Login with Quickbase EU – quickbase.eu
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.