Forum Discussion
AustinK
6 years agoQrew Commander
Pipelines is pretty much brand new so you basically are the first one I've seen do this.
I don't have the dropbox plugin enabled but do you have the ability in the Pipeline to update a record after receiving the response? You should be able to add that in as another step at the end. Or is the issue with parsing the response?
I don't have the dropbox plugin enabled but do you have the ability in the Pipeline to update a record after receiving the response? You should be able to add that in as another step at the end. Or is the issue with parsing the response?
BradLemke
6 years agoQrew Assistant Captain
Update: I got everything operating incredibly smooth and efficient now. Here's the Pipelines steps:
A - Trigger - Quickbase Channel - Record Created - Inspection photos table (one photo=one record)
B - Action - Dropbox Channel - Upload a file - using the photo's url from the record
C - Action - JSON Handler Channel - Fetch JSON - Execute Dropbox API command previously set up in Webhook channel
D - Query - JSON Handler Channel - Iterate over JSON records - Enter sample JSON Response into 'Schema Sample' - This lets you pull and use data from the response to the previous step!
E - Action - Quickbase Channel - Update record with the URL in step D, and the file ID from step B (into their own unique fields).
Next, I created a standalone webhook that will delete the file from Quickbase once the Dropbox URL field is filled in.
Lastly, I created a Rich-Text Formula field that modifies the Dropbox URL into an embeddable format (removing dl=0 from the end and adding raw=1).
And voila - my app now has virtually unlimited attachment space with no attachment management upkeep, all while using the mobile user-interface without intruding on existing workflows. All this allows my app to use the 'email notification' feature to send the attachments (in addition to the rest of the report) to our customer the instant the inspection is completed on-site and not a day or two later after being processed in the office.
------------------------------
Brad Lemke
------------------------------
A - Trigger - Quickbase Channel - Record Created - Inspection photos table (one photo=one record)
B - Action - Dropbox Channel - Upload a file - using the photo's url from the record
C - Action - JSON Handler Channel - Fetch JSON - Execute Dropbox API command previously set up in Webhook channel
D - Query - JSON Handler Channel - Iterate over JSON records - Enter sample JSON Response into 'Schema Sample' - This lets you pull and use data from the response to the previous step!
E - Action - Quickbase Channel - Update record with the URL in step D, and the file ID from step B (into their own unique fields).
Next, I created a standalone webhook that will delete the file from Quickbase once the Dropbox URL field is filled in.
Lastly, I created a Rich-Text Formula field that modifies the Dropbox URL into an embeddable format (removing dl=0 from the end and adding raw=1).
And voila - my app now has virtually unlimited attachment space with no attachment management upkeep, all while using the mobile user-interface without intruding on existing workflows. All this allows my app to use the 'email notification' feature to send the attachments (in addition to the rest of the report) to our customer the instant the inspection is completed on-site and not a day or two later after being processed in the office.
------------------------------
Brad Lemke
------------------------------
- MarkShnier__You6 years ago
Qrew Legend
Thank you posting,
BTW, that Pipeline setup you did is exportable as YAML. The recipients (or yourself using this technique in a different app), would edit the references to the Quick Base table IDs and the field numbers.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------ - ChristineSuarez5 years agoQrew CadetThanks for outlining everything you did here!
------------------------------
Christine Suarez
------------------------------ - QuickBaseJunkie5 years ago
Qrew Legend
Thanks for sharing this @Brad Lemke! I'm building something similar, but for the life of me, I cannot get the file to properly upload to Dropbox.
Can you share how you're getting the attachment from the QB record into Dropbox?
This is what I'm doing, but it's not fully loading the file to Dropbox:
- A Quick Base record is added with an attachment triggering the pipeline
- It has a formula URL field with this formula URLRoot() & "up/" & Dbid() & "/a/r" & [Record ID#] & "/e9/v0"
- I'm then using that in the Dropbox Upload a File Chanel in the URL field
I've double checked the link is correct and opens the attachment in the browser (even when I click on it in the Pipeline activity, it displays the file)
Perhaps there is a different formula for the file that I should be using?
As someone who got this to work, I would love your input.
Thanks!
-Sharon
Result in Dropbox
ā
------------------------------
Sharon Faust (QuickBaseJunkie.com)
Founder, Quick Base Junkie
https://quickbasejunkie.com
------------------------------- BradLemke5 years agoQrew Assistant CaptainI remember seeing this exact issue when testing and it was a bear to figure out. Your URL formula is exactly how I set mine up. Is your File Attachment field set up to 'Allow Open Access'? I don't remember if that specifically was the fix for me, though it couldn't hurt to test.
------------------------------
Brad Lemke
------------------------------- QuickBaseJunkie5 years ago
Qrew Legend
Great question @Brad Lemke. Yes, it was/is set to allow open access.
Might there be a dropbox setting or configuration needed?
ā
------------------------------
Sharon Faust (QuickBaseJunkie.com)
Founder, Quick Base Junkie
https://quickbasejunkie.com
------------------------------