Forum Widgets
Recent Discussions
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.
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??
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
Validate New Drop-Down Options Before Saving
I have a drop down field that allows user to create new options, but I'd like to prevent people from adding any options with a specific key word. I thought I could accomplish this with a formula field that would just check if the drop-down field contained the key word. The problem I've run into is that it seems the formula fields are reading the new option as '_other' rather than what has been entered. I assume that is the placeholder that's used because the new option doesn't actually get saved to the drop-down field options list until the record is saved, but I cannot think of an alternative way to validate the field because of this issue. Here was my formula, just for reference: If( Contains([field],"Keyword"), Case([field], "Valid Option with Keyword",false, "Other Valid Option with Keyword",false, true), false )
