MatthewMatthew3
8 years agoQrew Cadet
Zapier Zap - Form Fields to New Table Row Addresses Not Working
I have stumbled onto an issue regarding a new Zap that I created for QuickBase Application. To avoid the issues associated with utilizing the HTML Form Wizard on QuickBase's website (especially with as dated as it is and needing to import into multiple tables simultaneously), I created a zap from my Ninja Form on my wordpress website to the QB App I am using.
EVERYTHING.... Worked great.... Until... I got to the Address.
I've tried multiple scenarios....
None of the above seem to work. The data just refuses to cross over into the database, which is becoming quite inconvenient having to manually input addresses for every form submission that comes in, which is defeating the purpose of having this process automated.
Support seems to think it is an issue with Zapier. I however beg to differ... I can take those same form fields and get them to populate any other database field I want. EXCEPT Address Fields... I know that they are somewhat special compared to other fields... And I really don't want to have to re-create my secondary address field just have have data in the database and have to transfer that into the "Quickbase Address" field type every time either... That's just extremely redundant and not pretty.
Hopefully someone has experienced this before and can help assist me in finding a swift resolution to the problem, or an alternative solution. I am open to ideas, such as potentially using Workato or something else. But it's just kind of crappy that outside of this one problem it's all working else-wise.
EVERYTHING.... Worked great.... Until... I got to the Address.
I've tried multiple scenarios....
- Zapier Template to Address Parent Field Directly
- Zapier Template to Each Individual Address Sub-Field Direclty
- Zapier Template to Both Parent Field and Sub-Fields Simultaneously
- Using Address 1 & 2 or Address 1 Only
None of the above seem to work. The data just refuses to cross over into the database, which is becoming quite inconvenient having to manually input addresses for every form submission that comes in, which is defeating the purpose of having this process automated.
Support seems to think it is an issue with Zapier. I however beg to differ... I can take those same form fields and get them to populate any other database field I want. EXCEPT Address Fields... I know that they are somewhat special compared to other fields... And I really don't want to have to re-create my secondary address field just have have data in the database and have to transfer that into the "Quickbase Address" field type every time either... That's just extremely redundant and not pretty.
Hopefully someone has experienced this before and can help assist me in finding a swift resolution to the problem, or an alternative solution. I am open to ideas, such as potentially using Workato or something else. But it's just kind of crappy that outside of this one problem it's all working else-wise.