O365 Find Files And Folders: Code: itemNotFound OneDrive

Help Studio
#1

Hi Everyone,

I am trying to use the Find Files and Folder activity inside the Microsoft O365 Scope. I keep getting the error ItemNotFound. If I put “Input PDF” inside the query I get an error saying Invalid request even though there is a folder inside my OneDrive named “Input PDF”. If I don’t put anything in the query and leave it blank it brings back the DriveItem with all of the folders in my root. Even if I name one of the folders in my root path of OneDrive I get the error ItemNotFound.

Also this was working perfectly last month when I ran my flow but now it is no longer working.

I don’t know if this is a Microsoft issue that won’t allow me to interact with OneDrive or if it is an issue with the UiPath activity.

Thank you in advance.

#2

Hi,

Are you using Microsoft Graph as an integration, or are you accessing your OneDrivre through UiPath’s Open Browser?

#3

I am using the Microsoft Graph Integration for this.

#4

I’m having the same issue currently, while searching for a file. The account being used has access to the entire path to the file, and when searching on Sharepoint can find it. But when using the Find Files and Folders activity, it produces an ‘InvalidRequest’ error. I’m currently working with support and will let you know if we determine the source cause of the issue.

#5

Hi, I’m curious if anyone made progress finding the cause, or better, found a solution?

I can reproduce reproduce the error while using the Microsoft Graph Explorer, however I don’t know how to fix this in UiPath Studio.

Reproducing the error:
Go to Microsoft Graph Explorer (https://developer.microsoft.com/en-us/graph/graph-explorer).
When using the url (/v1.0/me/drive/root/search(q=‘klanten’)) as provided by the docs (https://docs.microsoft.com/en-us/graph/api/driveitem-search?view=graph-rest-1.0&tabs=http#example) the same ‘invalidRequest’ is shown.
When using a different url (/v1.0/me/drive/root/children/?search(q=’klanten’)) everything works well.

#6

is this issue resolved ?

#7

We didn’t - we ended up dropping the automation as it was a throwaway and wasn’t worth the time investment at that point.