Automation retire deadline extension?
I swear I saw an email a month or so ago saying that we no longer need to switch our automations to Pipelines by Jan 1, 2023. There is no current date but they will give us 6 months notice. I cannot find that email now, and want to be sure I saw that correctly. Can anyone confirm? ------------------------------ Mike Tamoush ------------------------------
Pipeline speed and workarounds.
I have been testing my pipelines that I have migrated from automations and they run much slower comparatively. A process that took maybe 5 seconds max to do in my automations, now takes 40 seconds to 2 minutes. I understand the Blaze engine was supposed to make pipelines faster, but the speed is still a far cry from the autos. I put in a support ticket to see if this was normal for the steps the pipelines were using. The response that I got, was that it was normal and that while pipelines are slower, they scale better than autos. Most of my pipelines are triggered by creation or update events. A common process in my app is when a user enters in data on a parent record which gets copied to a child record. The parent record that triggered the event is updated to have the input-text cleared from the field for future use. Here is why I did this. Most of the users in my company are looking at many different tabs, windows, Outlook, shared folders, and remote desktop screens while they are doing their work. I wanted to make record creation and updating as convenient as possible by minimizing the amount of child records that they had to go into. The solution that I originally had, was to have automations allow users to make all of the child records that they needed while inside of a parent record. It worked worked perfectly. I have tried other methods like embedding child forms on the parent via iframe, but they are hard on the eyes and they do not work. There was also the option of having the child form appear as a pop-up, which I wanted to avoid as users are inundated with enough visual stimuli . In the image below, other tabs in this record like Referrals, Notes, and Quotes, represent child records which relied on the same autos described above. Generally, this process translated to pipelines is this: 1.) Record Update (parent record updates). 2.) Create Record (child record created). 3.) Prepare Bulk Upsert (staging parent record to have input-text cleared). 4.) Search Records (search for parent record that triggered event). 5.) For Each Record (only one record in most cases) 6.) Add Bulk Upsert Row(add blank formula-text field that clears the input) 7.) Commit Upsert (merges upsert changes to parent record) For anyone who has migrated automations to pipelines, do you have any tips or work-arounds to make things faster? Also, will pipeline performance improve soon? Thank You, James ------------------------------ James Dalton ------------------------------
Full Application Overwrite Restore - Automations and Pipelines
On requesting a full Application Overwrite restore, I have read it will not restore Automations. What exactly happens, are the ones that exist in the current app before the restore still remain after the restore or are they deleted completely after the restore? On the same note, how about Pipelines? The ones that are there, are left there or are they deleted after the restore? ------------------------------ Rick Miller, Trinity ------------------------------
Automation to change edit a field in a parent table from child table
I would like to create an automation in a table that will allow me to modify a record in a parent table if needed. Here is my scenrior: I create or edit a record in Table B, before closing the record i would like a pop up to ask if ( or anything else that can ask me to change the record in the parent table) I would like to modify a specific field in the parent table ( the field is "reminder date" in table A) Basically I create or modify a record in my "estimate" table, I would also like to be able to change my "reminder date" for the parent record (patient table).... I will eventually use pipelines to do this, but I need to set up this up quickly. Any thoughts? ------------------------------ Kelly Lyons ------------------------------
[Urgent] Reposting: Automation to create multiple records based on a multi-select text field using pipeline
How can create multiple records based on a multi-select text field using pipeline? So I can get the easy of a drop-down with the power of a join table.... If you can share the detailed solution that would be great.. Really need some help Lashell ------------------------------ Lashell Thomas ------------------------------
Automation turned itself off
Is there something which would cause an automation to turn itself off? I built a new automation that adds X child records when a button is clicked, where "X" is number field on the parent record. (I had posed a question last week on how to do this where it loops through the automation, counting down). I had tested this, and it worked fine. I put in quantities of 5-10 for testing. It looped through the automation the correct number of times, a little slow, but no problem. Today my colleague noticed it stopped working in the middle of adding records to a table. In this case, "X" was set at 108. It ran through 102 times creating 102 child records and then apparently the automation shut itself off. I know this because when I looked at it today I could see the automation was off. There are only two of us here with the admin rights to do this and neither of us did. I can see the countdown quantity is now at 6. Is there some limit on the automation runs related to something? That doesn't make sense because I can see the automation has run over 200 times in the last week and I'm sure other users are running much higher numbers for automations. Has anyone else run into this issue? It does not show there were any errors. ------------------------------ Kim G ------------------------------How to make my automation repeat X times
Hi I have a button that adds a child record to a table with various data from the related table. It's involves three tables: a Company, Quote and Asset. When products quoted turn into a sale, the user clicks the button to create an Asset record on the related Company record with info pulling from the quote regarding the type of equipment purchased, sales order number, etc. Clicking a button causes a checkbox to be checked. The automation runs based on that checkbox being modified to checked; the last step of the automation is to uncheck the box. This works just fine. Since it's capital equipment most often sales are 1-2 items, meaning the button may need to be clicked once or twice to record the assets. Sometimes we get bigger orders at which point it becomes annoying to click the button 10-20 times. Also if the user isn't patient between clicks giving the system time to run the automation, it may not register all the assets. I'd like to add a field for adding multiples, but am not sure on the right syntax for getting my automation to loop for x times. I know it probably involves snapshots, and a formula to subtract one for each loop, but could use some help on setting up this structure. Yes, I've set this up in Automations rather than Pipelines since it's far more easier to figure out how to do. I've attended several Pipelines training, but it all hasn't soaked in very well. Thanks for the tips! Kim ------------------------------ Kim G ------------------------------Pipeline Bulk Record question
I've migrated most of the simple automations to pipelines and have started on the more complex automations. The first ones I started with are replacing the table to table import automations. I started with the documentation provided by Quickbase in the help section, but wasn't sure what to enter in the Headers section for the Name and Values fields for the Make a Request step. Then I looked at this post, Building Table-to-Table (T2T) Imports using Pipelines and saw it did not include the step for Make a Request. I deleted the step and the pipeline worked as needed. I have two questions, first, do I need the Make a Request step since it worked as needed without that step. Second, What values should go in the Name and Values fields of the Make a Request step? Thank you in advance. ------------------------------ Paul Peterson ------------------------------Automation/Pipeline Current User Question
This may seem like an odd question, is the current user when a pipeline or automation is running the person who created the automation or pipeline? I'm asking because I have an automation (soon to be converted to a pipeline) that is throwing an error when updating some records because there is an issue with the custom data rule in the table. I was thinking if the user when the automation or pipeline is updating the record I could add a condition to the custom data rule to fire only if the current user is not an admin. ------------------------------ Paul Peterson ------------------------------
Any word on moving Pipelines back into each app for multiple dev visability?
Haven't really touched pipelines yet for our other apps and projects since all developers cannot see them. Still do not understand this design choice... Any word from QB on fixing this to work like Automation so our development teams can work together? ------------------------------ John Ross ------------------------------
