Forum Discussion

LesKimbler's avatar
LesKimbler
Qrew Cadet
2 days ago

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??


Pipelines

4 Replies

  • Mez's avatar
    Mez
    Qrew Assistant Captain
    5 hours ago

    You could also try using Make Request (MR) within the Quickbase channel using the standard api structure for querying (using new rest api). If you go this route, you can then check for the existence of a record from the data returned in the conditional: evaluates to true: {{step.json.metadata.totalRecords}}==1

    I was forced to use this step, MR, instead of Search, I know you said Look up (but as you've noted you can only match on the Record ID or a Key field, if you set a unique one on the table that isn't the Record ID), because of performance issues. This way you can also query on multiple fields versus just the one. And, you can even test this in their online api playground: api

  • Maria's avatar
    Maria
    Community Manager
    7 hours ago

    Everything you described here (I just read it again) should be possible. I'd like to look at the app structures and fields involved to better understand what's happening. 

  • Maria's avatar
    Maria
    Community Manager
    7 hours ago

    I'm sorry you're running into friction with pipelines. Once you're back on track I'll send you some resources you can use to get more comfortable with Pipelines. I've checked in with your CSM and let them know you're running into this roadblock, they'll be reaching out soon.

    First, however, let's make sure we help you get this particular Pipeline gets to where it needs to be. Are any of these fields that are triggering the pipeline formulas? I think we'll need to look closer at the apps the pipeline is working between to help guide you better. 

    If you make a support case, front loading csr access can help expedite things: 

    https://helpv2.quickbase.com/hc/en-us/articles/7377332729620-My-preferences#:~:text=Tech%20Support%20Access,have%20access%20to%20your%20pipelines

    They'll also probably ask for access to the apps to have a look at the elements being referenced in the pipeline as well.