Forum Widgets
Recent Discussions
Pipeline Jinja For Duration in Seconds
I would like to have a pipeline condition where nothing happens if the current time is less than or equal to 30 seconds from the value in a given field, which is a date/time field. I have tried multiple variations of jinja code and mostly get the error message: Validation error: Incorrect template "whatever my jinja is". ValueError: invalid literal for int() with base 10: 'my_date_time_field_name' I have tried subtracting and converting the time.now and my field to an integer before comparing to 30 for seconds, I tried using time.delta(seconds=30) and adding it to the date field then comparing it to the current time, and some other things. I get the above error each time. I would really like to do this with Jinja, if at all possible. If anyone can help, that would be greatly appreciated. I know, worse comes to worst, I can add a helper field and just work off of that, but I am doing this for learning purposes. Thank you in advance to anyone who can help.
Help with searches...
i set up a report that lists each vendor and what states they checked off for service area, they are checkboxes, i don't know how to make it group all vendors that service alabama, all vendors that service alaska, all vendors that service arizona, etc... my ultimate goal is to create a search widget that will filter by service area i inherited this app and it was seriously lacking. i'm new to creating and working on app setups. i have taken the intro to app building and intro to pipelines courses so that i could make some changes and i just can't figure this out.
Pipeline Error trying to Create a Record
I am not a fan of Pipelines. I miss Automations. I used to be able to build an Automation in like 30 min and it did what I wanted. I've been working two days to build this Pipeline, even using the AI to do the framework, and I get nothing but errors or issues like this one. The intent of this pipeline is, if a record is created/updated in one app, it will look to see if there is a matching record in another app. If there is a matching record in the other app based on a site # & uniquely created identifier, it will update any modified changes in the second app. If there is not a matching record, it will create one in the second app. After tweaking several different things, I finally got it to create the record. At first, it was saying it was finding a record that matched the criteria despite no record being present. But now, whenever it does the search for a "Matching Record" based on the criteria I asked it to look at (site & unique identifier), it continues to have a FALSE finding and just creates a duplicate instead of updating. And the Activity log seems to say that it couldn't find the record based on the search criteria but created duplicate records with the exact criteria it was asked to look for. (I now have 5 records with identical site #s and unique #'s. What am I missing to get it to have a TRUE finding of the record. Also, is there any way to change the "Query" to look at anything besides the Record ID??Counting Instances of String across records for use in a Gauge Chart
Hi all, I want to use a gauge chart the displays the number of records that contain the letter 'R' as part of a string of in a 'Job Number' field, out of the total number of records in the table. Typically a job number field value would be in the format of 00000_00, or 00000_A0, or 00000_R00. With R denoting revised. I've tried using a query report formula, but whilst it's a valid formula attempt, it displays 0. The total number of records for the gauge var text QUERY = "{6.EX." & Contains([Job Number], "R") & "}"; Size( GetRecords($QUERY)) My logic to the above is that its querying the data table, for job number field (ID 6) to see if it contains a string with an 'R' in it, and if so count the total number of true records. Any ideas? It would be awesome if the gauge can be coloured to show the revised element in red, but the remainder of the gauge in green. But I really think that's beyond the limits of what is possible. However, if anyone has an idea how this could be accomplished, that would be absolutely appreciated!
Report link - target field value is contained in
I have Table A and Table B. I would like to create a Report Link in Table A, which returns multiple records from Table B. In Table A, I have a text field called AllDataPoints with value: 189-261 ; 189-21 ; 189-101 (It was originally a summary field of combined text, i.e., multi-select text, so I can play around with the delimiters and such.) Table B has a field called MatchID (text). I want the Report Link to return 3 records from Table B -- the record with MatchID equal to 189-261, the record with MatchID equal to 189-21, and the record with MatchID equal to 189-101. In other words, I want records where MatchID is contained within AllDataPoints. I tried changing Value Matching to contains and wildcard. My guess is that it would work if values in A were substrings of values in B, but I want it the other way around -- return records where B is a substring of A. Any ideas? Thanks.
Copying Apps that contain imports
A lot of automation occurs in our application using imports. Most times it is an import from and to the same table to update content based on conditions. Problem: if you create a copy of an application, it appears that all the imports still point back to the original application name and tables. It would be simple enough if we could simply update the import target application name and have all the configurations update, but when you change the app name and select the table, all the import configs get lost, so you basically have to rebuild them all from scratch, risking potential human error. Does anyone have a known method out there for updating imports when copying an app?QuickBase Pipeline Best Practices
After working with QuickBase Pipelines for years, one thing is clear: Every real-world use case is unique, from API limits and Jinja logic quirks to race conditions or silent failures. That’s why I believe we need more shared knowledge and real-time collaboration around building smarter Pipelines. What I’ve learned: Pipelines are incredibly powerful but not always intuitive. The best solutions often come from hands-on trial, error, and teamwork. Every failure teaches us something about logic, structure, or scalability What I’ve learned: Share lessons from the field Explore patterns that reduce manual tasks outside the system Let’s learn by doing — together. #QuickBase #Pipelines #Automation #LowCode #WorkflowAutomation #NoCodeDevelopment #QuickBaseCommunity #APIIntegration #ProblemSolving
