Expand all | Collapse all

Address field with Pipelines QB channel?

  • 1.  Address field with Pipelines QB channel?

    Posted 06-30-2020 13:54
    Hello... I am trying to enter Street 1, Street 2, City, State, Zip from one app's address field to another app's address field and get the error below. The pipeline is set up correctly and runs fine when I don't include the address fields. I am using the individual sub fields.

    This is what I get...has anyone else? 
    "Validation error: Incorrect template "{{a.address_city}}: expected token 'end of print statement'. got 'Address_city"
    I don't see that error in the Troubleshooting section of Pipelines Help.


    Heather Bryant

  • 2.  RE: Address field with Pipelines QB channel?

    Posted 06-30-2020 15:57
    Hi Heather, 

    I just touched base with the dev team on Pipelines on your issue to see if they had any ideas and it looks like this is related to an issue they have found with the address fields. It has to do with some of the field mapping causing an error, it is one they have a bug for and are looking into. If you wanted to be tied to this issue if you create a Care case they can tie it to the bug and you will get updated as they look into it. 

    The dev I spoke to wasn't sure if it would work in all instances but he suggested trying to rename your address field so that it has no spaces in the name if your address field currently has spaces. That has helped in some instances but not universally. Certainly let me know if you have any further issues creating a case or with your Pipelines. I hope the information is helpful.

    Evan Martinez
    Community Marketing Manager
    Quick Base

  • 3.  RE: Address field with Pipelines QB channel?

    Posted 07-10-2020 18:21
    Hi @Heather Bryant!

    I'm not sure if this was your issue, but I posted this in the QB Slack a few weeks ago:

    FYI I just resolved a Pipeline error that showed up when populating an Address field with another Address field (both from Quick Base) when the field name has a space, such as, "Contact Address". The syntax shows up as {{c.Contact Address_street_1}}. The fix is to add an underscore between "Contact" and "Address" directly in the Pipeline (no need to rename the actual field).​

    Sharon Faust (QuickBaseJunkie.com)
    Founder, Quick Base Junkie