Martyn Houghton Posted November 22, 2019 Share Posted November 22, 2019 @Steve G We are able now to get the 'Search Drive Items' to function and return a fileid , but when we insert these into the 'Share Drive Items' the node returns cloud automation successful but no values are returned nor the share undertaken. Cheers Martyn Link to comment Share on other sites More sharing options...
Martyn Houghton Posted November 22, 2019 Author Share Posted November 22, 2019 @Steve G It appear it is not trapping the underlying error (see below) and returns success when Continue On Error is turned on. Cheers Martyn Link to comment Share on other sites More sharing options...
Steve G Posted November 26, 2019 Share Posted November 26, 2019 Hi @Martyn Houghton, That's expected behaviour unfortunately - when the Continue On Error is switched on, the node will always return a success. I'll have a look to see if there's anything I can do to trap that and send back the error in an output param rather than just throwing it. With regards to the "feature disabled" error, that's being returned from OneDrive so you'll need to speak to your O365 admins regarding that. Cheers, Steve Link to comment Share on other sites More sharing options...
Martyn Houghton Posted November 28, 2019 Author Share Posted November 28, 2019 @Steve G We have implemented a fresh tenant with a single paid One Drive account. We no longer get a permission error nor failure of the node, but the share does not occur. Permission Id is returned blank and the status parameter has the value of 'ok'. How can we diagnose what is happening? Cheers Martyn Link to comment Share on other sites More sharing options...
Martyn Houghton Posted December 18, 2019 Author Share Posted December 18, 2019 @Steve G Attempting to use the new option 'Create Shared Link' but it does not appear to have the same options as per the 'Share Drive Item' so struggling to work out how to use this alternative method. Cheers Martyn Link to comment Share on other sites More sharing options...
Steve G Posted December 19, 2019 Share Posted December 19, 2019 HI @Martyn Houghton, This integration uses the Create Sharing Link API, which will create a link to the provided specification, and will pass the shared link back to the Web URL node output param, as below. This URL can then be forwarded to the customer who requires it: Cheers, Steve Link to comment Share on other sites More sharing options...
Martyn Houghton Posted December 19, 2019 Author Share Posted December 19, 2019 @Steve G Thanks for the update. In this case the link will not be authenticated to the end user as there is no means to pass the users email address. Looking at the API details in your link this would only be applicable to sharing by organisation or anonymous. We are still not getting the permission id back from the share drive item process, so I wondering if there is another API call to retrieve the permission id by passing in the file id and the email address as a separate request. Also, I have logged an support ticket about issue with the search drive item integration step, but thinking about it a bit more I think it is down the formatting of the 'Query' parameter. Do you have any documentation on the syntax for this? Cheers Martyn Link to comment Share on other sites More sharing options...
Steve G Posted December 19, 2019 Share Posted December 19, 2019 5 minutes ago, Martyn Houghton said: We are still not getting the permission id back from the share drive item process, so I wondering if there is another API call to retrieve the permission id by passing in the file id and the email address as a separate request. Unfortunately not It appears that external share links don't have a permission ID associated with them. I have tried this API to get this information back from the share URL provided by the Send a Sharing Invitaion API, but the ID field in the output is always populated with 00000000-0000-0000-0000-000000000000 when shared externally... So it's limitations in the Microsoft Graph API's that we can't (currently) workaround, rather than issues with the integrations themselves The search integration uses this API, so we're just replacing {search-text} in the below with the string provided in the Query input: GET /drives/{drive-id}/root/search(q='{search-text}') Cheers, Steve Link to comment Share on other sites More sharing options...
Martyn Houghton Posted December 19, 2019 Author Share Posted December 19, 2019 @Steve G Thanks for checking. In terms of the query parameter I am struggling to find documentation on the syntax of the '{search-text}' and I think the issue we are having is that the file names we are searching for contain spaces. I tried encasing the file name in double and single quotes, but that does not return any matches. Cheers Martyn Link to comment Share on other sites More sharing options...
Steve G Posted December 19, 2019 Share Posted December 19, 2019 @Martyn Houghton We already wrap the string in single-quotes, so you shouldn't need to add any more. Let me take a look, might be something to do with the URL encoding, 2 ticks... Link to comment Share on other sites More sharing options...
Martyn Houghton Posted December 19, 2019 Author Share Posted December 19, 2019 @Steve G Thanks to give you an example we are inserting the file name below:- DM Desktop 5.20.020.zip File exists in the OneDrive instance with an exact match, but in a sub folder. Cheers Martyn Link to comment Share on other sites More sharing options...
Steve G Posted December 19, 2019 Share Posted December 19, 2019 @Martyn Houghton Subfolder searching works fine, but I can replicate the issue with spaces in the query. Just looking at that now... Link to comment Share on other sites More sharing options...
Martyn Houghton Posted December 19, 2019 Author Share Posted December 19, 2019 @Steve G If it helps I can give you temporary access to the OneDirve account. Cheers Martyn Link to comment Share on other sites More sharing options...
Steve G Posted December 19, 2019 Share Posted December 19, 2019 Thanks for the offer @Martyn Houghton, but I can replicate with my dev O365 instance. There are a couple of issues here. The first is that spaces shouldn't be encoded in the usual way within the query - they should be replaced by a + character. That's fine though, as I can handle that in the iBridge operation code. The second issue is a little more annoying - the API doesn't like full stops (or other "special" characters, it seems) in the name of the file being searched - except the one that separates the name and extension. I'm just trying to work out if there's a way to encode/change these characters for the API to play ball. I'll let you know how I get on... Cheers, Steve Link to comment Share on other sites More sharing options...
Martyn Houghton Posted December 19, 2019 Author Share Posted December 19, 2019 @Steve G Thanks for the update and your perseverance with us. Cheers Martyn Link to comment Share on other sites More sharing options...
Steve G Posted December 19, 2019 Share Posted December 19, 2019 Hi @Martyn Houghton, I've added a new integration that will return an drive items ID etc, when it's provided the Drive and the Item Path: So, if I have drive that contains a file in a folder within root, like this file here: Where the items filepath is: Some Demo Folder/A Screen Shot 2019-06-21 at 10.47.51.jpg I can now get its unique ID for use in further workflow nodes using the new Microsoft>OneDrive>Drives>Get Drive Item Cloud Automation: So as you know the path and file that you want to share, this new operation should hopefully workaround the drive item search API limitations... I've just released this to Live, so it should be on your instance in a few minutes. Let me know how you get on with this one! Cheers, Steve 1 Link to comment Share on other sites More sharing options...
Martyn Houghton Posted January 6, 2020 Author Share Posted January 6, 2020 @Steve G Sorry for the delay in getting back to you. The new 'New Get Drive Item' has allowed us to now get the process to share the files, which is great step forward. Still struggling with Microsoft API not returning the Permission ID whatever we do, but that a separate discussion. Thanks Martyn Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now