Sigma and OneDrive
Hey everyone,
I'm currently looking into creating a custom extension that integrates Zoho Projects and OneDrive. Currently, I have it as far as reading items from OneDrive, which is dandy and all, but am looking to expand into file uploading.
I would like to be able to drag-and-drop files onto the extension, then upload those files to OneDrive. I'm currently attempting to upload a simple sample text file via the extension, but to no success.
Here's some example code, lifted mainly from the documentation found here:
- var url = "/me/drive/root:/FileB.txt:/content"
var file_details = {
type: "PUT",
headers: {
"Content-Type": "application/binary"
},
files: [{
"Value": "01010100 01100101 01110011 01110100 00100000 01000010 01101001 01101110 01100001 01110010 01111001"
}]
}
zohoprojects.request(url, file_details, "onedrive").then(function(response) {
console.log(response);
});
I'm assuming that I want to run things through zohoprojects.request() since the connector is handling the auth tokens in the background, but all it ever spits out is "Oops! Something has gone wrong., status: failure" with no additional information.
Zoho's JS SDK documentation here states that the request object can have a "files" key, where the value is a JSONArray, and has some mentions about the body being ignored if the actual file is uploaded, and mentioning a binary type, but I don't quite understand the actual meaning. Is there an example I can check out that handles file uploading?
Can someone point me in the right direction here? Am I building the request incorrectly? Is there a way to get more meaningful information from the zohoprojects.request() response?
Thanks again,
Lee
Sticky Posts
Building extensions #10: Fetch customized user inputs, store them globally at the app level, and access them across entities
This data storage concept enables you to store data related to your extension for both entity properties and extension properties. In our previous piece, we looked at how to store data for entities using entity properties. In this post, we'll look atBuilding extensions #9: Store, retrieve, and access entity-specific data in widgets using data storage
Data storage - Overview Storing data related to the extension you are working on is essential. It can be saved as key-value pairs for an entity or extension, known as entity and extension properties, respectively. Data can be saved for the following entitiesBuilding extensions #7: Create custom widgets for a simplified end-user experience
Discover the benefits of using widgets! We explored the significance of widgets, prerequisites, and the availability of JS SDK methods as part of our previous post. In this post, let's go over a detailed example of using widgets along with certain ZohoBuilding extensions #6: Custom user interfaces with Widgets
Welcome to our post on Widgets for Zoho Projects! In our last post, we explored the significance of the connections feature, showed how to use it, and provided an example use case. In this article, we'll look at the importance of widgets, another featureBuilding extensions #5: Integrating applications with Zoho Projects through Connections
In our last post, we discussed the essential features that a Zoho Projects extension can provide. Starting with this post andin every subsequent post going forward, we'll go through each of those features in depth, one by one, with an example use case.