has anyone successfuly implemenbted the Onedrive Pipe and could help.
I hope this is the right method i have adopted so far.
In my documents table i have an Add Document popup. In the popup is a ‘files field’.
In table rules i have a rule for when a record is created. Within the rule I have added the OneDrive pipe to upload a document.
I have set the parameters in the Pipe. I have linked the ‘File’ parameter to Record Value - Document Name, being the files field and have set the folder to a custom value of the folder name in OneDrive. in this instance ClientFiles
A document is uploaded OK and the record saved but it looks like the documents is still being sent to TBs server at amazonaws.com
What would i need to do please to get the document sent to OneDrive.
The OneDrive pipe allows you to upload your files to OneDrive in addition to Tadabase.
This can be helpful if you would like to be able to manage your files in OneDrive folders (For example, you can create a folder for each client’s documents.)
Check your OneDrive account to see that the file uploaded correctly.
Note: In the rule where you triggered the OneDrive pipe, you can update a record field to the pipe response of OneDrive file ID to confirm that the pipe was triggered correctly. This will allow you to delete the file from OneDrive via the pipe.
See a demo here.
If you do not want to store your files in Tadabase, you have the option to store your files in either in your personal AWS S3 Bucket or in your DropBox account.
Thanks @Sara and thank you for the demo. OK, ill work on the response. The field you have in the demo with the onedrive filelink. is that a seperate field to the standard filelink? My filelink is opening the document from AWS.
Are you using a File or Link field? Attachments fields are not supported.
Another note, If you are testing in the Live App, you can Enable Debug Mode to get a more detailed explanation of the error.
You can also test in the Pipes section of the builder, by navigating the OneDrive pipe → API Calls → Test to see the JSON Response from the API Call.
Turns out, we wont be able to use OneDrive anyway. the ideas was to store clients documents for our self serve portal but they may not have a onedrive account so won’t be able to access the documents.
Hi @moe is this AWS S3 Bucket? i did start to look at it yesterday. A video would be great if you don’t mind.
Can you confirm if i understand this correctly - any documents upoloaded to our own S3 account will be able to be downloaded by our clients without another login once logeed in to our app?
Can we still send documents to OneDrive in addition, so employees can access the documents via the OneDrive desktop app rather than downloading from our app?
I maybe understanding this incorrectly, but I don’t think this will work. It’s not user friendly to have to generate a download link eact time a document needs to be viewed.
From further research in to this, am I right in thinking that any files in our own AWS bucket will not be secured and this is the same for dropbox?
@richardch372, there are different ways to make this more user-friendly. For example, you can name the Action Link - “View Document”, and then add a display rule to only show the Secure File Link field once it’s not blank or expired. Another option is to use the Pipe in the Data Source, and trigger the pipe automatically each time the page is loaded.
Regarding your second question, you can secure your files in your own AWS bucket with the S3 Pipe, so that the resources cannot be viewed unless you generate a secure link. You can learn more here: Secure the files in your Amazon S3 bucket | AWS re:Post.
This could work, thanks @Sara. Can i just clarify the point you mentioned about using a pipe in the data source. If this pipe is triggered when the page loads, is that pipe generating a secure file for all of the records in the data table with any filters applied? i.e. documents for just the client we are working on or for the client logged in to the client portal. Meaning as far as a user is concerned, all documents are ready to be viewed on demand.
Right, the pipe is just triggered for the records displayed in that component, and sure you can also upload and share your files with your users via the OneDrive pipe as well.
Ok, so i am getting there slowly. I now have successfully uploaded a file to my own AWS S3 Bucket via my app. when downloading the test document i can copy the URL, paste it in to another browser where i am not logged in to my app and view the document.
I have watched the video on how to seucre the file which i think i will be ok doing but before i start that work i wanted to check as the content of the video in the AWS setup is contradictory to this updated method.
Should i go ahead, follow the video and use the IAM method?
and one last question. When i uploaded the test document, a folder was automatically created in the Bucket to store the document, it was named as per my apps account ID. Am i able to set a default value for this?
