Forum Discussion

QuickBaseJunkie's avatar
QuickBaseJunkie
Icon for Qrew Legend rankQrew Legend
5 years ago

Re: Address field with Pipelines QB channel?

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
https://quickbasejunkie.com
------------------------------

6 Replies

  • MarkShnier__You's avatar
    MarkShnier__You
    Icon for Qrew Legend rankQrew Legend
    5 years ago
    Thank you Sharon and Evan.
    Wow.  That bug really should be fixed.  I will put in a ticket.

    I was trying to create a QuickBooks Customer when a Quickbase Customer was created.

    I encountered a similar error as Heather.

    Validation error: Incorrect template "{{a.Billing address_city}}: expected token 'end of print statement'. got 'Address_city"

    The solution was to hand edit the code to insert an underscore in place of the space. "{{a.Billing_address_city}}

    ------------------------------
    Mark Shnier (YQC)
    Quick Base Solution Provider
    Your Quick Base Coach
    http://QuickBaseCoach.com
    mark.shnier@gmail.com
    ------------------------------
  • MikeTamoush's avatar
    MikeTamoush
    Qrew Elite
    4 years ago
    I ran into this same issue, and adding the underscore allowed the Pipeline to run, however, the address does not actually copy. I get this error:

    "Skipped because set values are the same as in source object."

    Which is bizarre because My Address Field 1 is filled in, and Address 2 is blank. I tried in another case where I was copying multiple fields, including an address field. It copied ALL fields EXCEPT simply skipped the address field. No explanation or error, just didn't copy it.

    Has anyone else had trouble using pipelines to populate one address field to another?

    ------------------------------
    Mike Tamoush
    ------------------------------
    • QuickBaseJunkie's avatar
      QuickBaseJunkie
      Icon for Qrew Legend rankQrew Legend
      4 years ago
      @Mike Tamoush

      If you are trying to update Address 1 (filled in) with Address 2 (blank), you have to use some Jinja because the null value in Address 2 is being ignored.

      So, rather than enter something link {{a.address_2}} in the spot for Address 1, you would enter:

      {{CLEAR if a.address_2 is none else a.address_2}}

      It's a ridiculous workaround in my opinion, but it does the job.

      This isn't specific to address fields either, this would be true anytime you have the possibility of overwriting a value with another value that could be null.

      -Sharon

      ​

      ------------------------------
      Quick Base Junkie
      ------------------------------
      • MikeTamoush's avatar
        MikeTamoush
        Qrew Elite
        4 years ago
        @Quick Base Junkie

        Thanks, but it turns out this was a different issue relating to the bug where a address field name cannot have a space in it. If it does have a space, the typical jinja code will​ not work, nor will a modified jinja where you add in the underscores for the spaces. Contacting customer support, they told me I must use this format:

        {{a['Physical Address_city']}}

        (where my field name was Physical Address).

        This worked for me, but they really need to work on the bugs in the addresses. For clarity, I was trying to fill a blank Address (2) with a completed address (1) and that wouldnt even work unless I used the above alternate code.

        ------------------------------
        Mike Tamoush
        ------------------------------