Forum Discussion

Re: Pipeline Record Search Advanced Filter didn't find any records

At your skill level (and mine!!), I would dumb this down. 


Make a native checkbox formula field in QuickBase. Use that single field in your regular filter (not advanced query). 


But if you want to learn the syntax others in this forum will have to wade in or you will need to research the help if it exists. Or the QuickBase Junkie may have courseware. 



------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------

1 Reply

  • DanielJohnson2's avatar
    DanielJohnson2
    Qrew Trainee
    Giving this a bump.

    I posted a thread yesterday about trying to use formula fields as key fields/webhooking in text to a key field and the limitations I was facing there. I'm trying instead to solve the problem with a pipeline:

    Step A
    Trigger when status or currently assigned to fields change. Include date of assignment and currently assigned to and related parent field for future steps.

    Step B
    Search for records in the parent table where the user in step A equals the user in the record being searched AND where the date field in the record from step B equals the assignment date in step A. Jinja expressions:
    {% if b.name_current_user.id == a.currently_assigned_to.id %}
    TRUE
    {% endif %}

    {% if b.date == a.date_assigned %}
    TRUE
    {% endif %}

    Step C
    Update the related parent field of the record from step A with the record ID of the record found in step B.

    The pipeline gets triggered and when it gets to step B the activity log says, "Found no Records of Record type" even though both of the Jinja expressions evaluate to true. Also, I have to use a Jinja expression for the date because the native expressions for date fields in pipelines doesn't have an "equals" or "is" option.

    Thoughts?

    ------------------------------
    Daniel Johnson
    ------------------------------