[Bug]: SharePointReader fails to load file directory about llama-hub HOT 12 OPEN

@arun04cbe

I eventually got it working.

This seems like less of a bug and more so the documentation on config variables could be more clear. Provided permissions are set up correctly consider the following:

sharepoint_site_name - is just the name of the site like “Data Science” or “Data”.

sharepoint_folder_path - is just the name of any top level folder in Documents like “Tests”. If you add “Documents/Tests” or “/Tests” it will fail. Only the folder name. Note: I only tested with recursive = True

from llama-hub.

@arun04cbe @brandon-vidoori

I changed a site without changing any code, and the code executed successfully; I changed other sites again, and it worked.

I feel a little strange, this failed site name is GPT, I don't know if it has something to do with this name, I used a mixture of English and Chinese sentences when I created the site again, the system automatically generates GPT as the site name.

The sites that I succeeded in executing were all single English word site names without exception.

I'm not sure if it's a problem with sharepoint itself

from llama-hub.

@jamiesun could you check if the permissions are set as mentioned here - https://llamahub.ai/l/microsoft_sharepoint?from=loaders

from llama-hub.

Same issue. Permissions are set up correctly in Azure/SharePoint

from llama-hub.

@jamiesun or @brandon-vidoori could you confirm whether you were trying to access only folders present in the documents component of the sharepoint site and not other components like pages or site contents

from llama-hub.

Yes, I am only trying to access folders/documents present in the documents folder. It seems to fail on the graph search for SharePoint site specifically the query for the site name returns nothing.

from llama-hub.

I am also getting the same error: An error occurred while accessing SharePoint: {'code': 'itemNotFound', 'message': 'The resource could not be found.'}

for doc in documents:
TypeError: 'NoneType' object is not iterable

from llama-hub.

@jamiesun @arun04cbe

The sites that I succeeded in executing were all single English word site names without exception.

The site I have been testing with is like “Data Science” so that might be causing the issue. Will try with a site named “Data” to see if that succeeds.

The documentation for the Graph REST API search sites is not clear on expected behavior for a partial match and would seem to suggest a search for “Data” would return sites named “Data Science” and “Data Management”. GetSite seems more appropriate for requiring exact match so the inflexibility we are noticing is bizarre to say the least.

from llama-hub.

I too faced this issue. I am reading through the msft documentations for the fixes. The current loader is only application based but we also need user based loader, which is well I am working on it. Will post the updates here post fix.

from llama-hub.

Can we store indexes in the SharePoint document library itself for persistence? That was the data will be secure within the same domain.

from llama-hub.

@jamiesun @arun04cbe

SharePointReader returned the same with a single word English named site like "Data" from my previous example.

I know have set up permissions correctly because I can debug SharePointReader locally, set breakpoint and step through code until the access_token is generated, then use that same access_token in postman with GET https://graph.microsoft.com/v1.0/sites?search=Data and success. Not only do I get Data site but I also get DataScience site that I previously created.

from llama-hub.

@brandon-vidoori Thanks for pointing out the exact problem. Will look to fix this up.

from llama-hub.