RobHenderson
Quickbase Staff
Joined 7 years ago
User Profile
User Widgets
Contributions
September Release Enablement
Life comes at you quick. Releases come at you quicker. Welcome to the September 2025 Release Enablement here at Quickbase As you might have heard, our new Release Notes App is going to keep you informed, but you are a busy person, doing busy person things. May I suggest taking a listen over at my release enablement to get a quick, informative, and often comical breakdown of what has changed this month in our humble Base of Quicks. In under 5 minutes you can listen to my soothing baritone* walk you through the recent changes. Highlights include: AI-Powered Help Right in Tech Support Quickbase AI has officially joined the support squad. When you access the technical support portal, you’ll now see AI help suggesting articles and troubleshooting tips. Don’t worry—our friendly, knowledgeable flesh and blood human support team isn’t going anywhere and are still here to work on your cases. 15 new chart and reports to use Donuts, Bullets, Heatmaps and so much more! Performance increases for both formula queries and apps being read into memory These are the types of things that can pay off big in larger apps. Pipelines Channel Accounts update Lets you manage all the external accounts your pipelines are using. Also shows the all the pipelines that an account is tied to. You can now also add account alias to better keep track of your accounts. All this and much much more, so please consider checking out our Release Notes App if you want all the details, but if a quick summary is what you need, you can listen to my break down right here:Re: Difference between "Apply Regular Expression" and "Find all matches to Regex" in pipeline text stage
Hello Andrew, You are definitely on the right path, as using regex is exactly how I would recommend doing that. If the output is not showing in the activity it is because it's not finding a match. This is just a guess but one thing that's easy to overlook is the formatting of the email. What the regex actually looks at is the code behind the email, so that includes formatting things like html tags and whatnot. I would double check the output of your trigger step to see exactly what the regex needs to be compared against and see if that requires any change in your regex formula. If this isn't what's going on or you would like a hand at this, please open a support case with your CSR ID# and Pipeline ID and link to this article, the agent will escalate it up to me and I'll be happy to take a look into it for you. Hope that helps, ------------------------------ Rob Henderson for ------------------------------Re: Calculate a future date in a pipeline
Hello Julie, An easy thing to miss is that in Jinja (which Pipeline uses) when you are doing calculations like that, they should be within the same curly brackets. This is very different than how Quickbase functions work. For example: if a.value = 5 b.value = 2 {{a.value + b.value}} comes out to 7 If you put in {{a.value}} + {{b.value}} it will print the literal text of "5 + 2" This is why you are getting that error, instead of a time stamp, it is returning the text: "2021-07-13 00:00:00+00:00+ Days(14.0)" Specific to your use case, I would recommend the following: {{a.complete_date + time.delta(days=b.maintenance_interval)}} Information on how to work with dates in Pipelines can be found here: https://help.quickbase.com/pipelines/working_w_date_time.html I hope this helps! -Robert Henderson Support Integration Engineer for Quickbase ------------------------------ Rob Henderson ------------------------------
