Address field with Pipelines QB channel?
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 w...
Forum Discussion
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
------------------------------
"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
Qrew Legend
Qrew Legend@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:
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
------------------------------
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
------------------------------
- @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
------------------------------- QuickBaseJunkie@Mike Tamoush WOW! That's nuts!
Thanks for sharing the solution.
I'll keep my fingers crossed for a fix and if I have the opportunity to talk with the 'powers that be' at Quickbase about Pipeline issues, I'll add this item to my list.
-Sharon
------------------------------
Quick Base Junkie
------------------------------- MarkShnier__YouJust confirming what Mike said. I had the same issue myself.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
