Microsoft SharePoint Graph API - Error in accessing sites and files

[AmruthaSivaraja]

Hello Everyone,

This post is a repetition of one I shared in the open discussion section four days ago, but unfortunately, I received no replies.

I have two questions related to SharePoint.

Question 1:

I need your advice on an issue I'm encountering while attempting to access SharePoint through the connector available in DX. My goal is to upload and download files from a SharePoint site.

I've successfully authenticated SharePoint using the provided Tenant ID, Client ID, and Secret key. However, when trying to perform other actions in the SharePoint VBO, I'm encountering the following error. Can someone help me troubleshoot this issue?

I've listed the permissions granted to the application account below. Can you suggest if I'm missing any other permissions for SharePoint?

Question 2:

Is there an alternative method or API call that allows me to avoid direct interaction with SharePoint and make folders available locally?

I've tried mapping SharePoint to a local network drive, but it has some limitations of connecting the network drive. I'm looking for an alternative method to map a drive.

I've explored manually syncing or creating shortcuts for OneDrive, but this raised concerns from the organization that it should be automated. Is there a way to automate these steps through an API call or by running a batch file?

 Thanks in advance.

------------------------------
Amrutha Sivarajan
------------------------------

[Sasank]

Hi Amrutha,

Were you able to manually upload the folder/file to sharepoint

------------------------------
Sasank Sai Mekala
Developer
Tata Consultancy Services
Asia/Kolkata
------------------------------

[AmruthaSivaraja]

@Sasank Sai Mekala Thanks for the response.

Its in client environment and don't have a service account for the bot id in MS O365 to upload file manually, so couldn't check it manually.

------------------------------
Amrutha Sivarajan
------------------------------

[harish.m]

Hi Amrutha Sivarajan,

 There is a workaround to fix the issue with mapping shared  point site as a network drive,

Here are the steps to  follow and implement in BP process.
1) Map share point  to local network drive

2) Create bat file  
Here I mapped  the sharepoint  drive as "N" 
3) Open Note pad And add the below code in notepad and save as bat file something like "SP_Site.bat"

start N:\
timeout 2
taskkill /FI "IMAGENAME eq explorer.exe" /FI "WINDOWTITLE eq *N*"

Note: Here the mapped network drive is "N" and window title is "N" but it might change based on how it is mapped. Time out value used as 2 seconds but you can tweak based on your file explorer response always good to have more time.

4) Update file explorer setting to handle this batch file
a) Open file explorer select the view> Options> change folder and search options
b  Make sure " display   the full path in the title bar" is checked
c) Similarly make sure  update if it is not selected for  "Launch folder in a seperate process"


5) Once these settings are completed Make sure the bat file is placed in VM bot is running  and  use "Utility Environment VBO - Start Process Action" and point the file to Open it.
6) this will make sure to connect the sharepoint site

Note: , I used  this logic in sharepont 2013 But I'm pretty sure it will not work on Sharepoint online

Check below post for more  info
https://community.blueprism.com/question/access-sharepoint-properly?DraftKey=e589be4f-6590-4aa4-8bc6-018aa84fe01b#e589be4f-6590-4aa4-8bc6-018aa84fe01b

------------------------------
-----------------------
If I answered your query. Please mark it as the "Best Answer"

Harish Mogulluri
Lead developer
America/New_York TX
------------------------------

[AmruthaSivaraja]

Thanks Harish for the suggestions. 

Unfortunately it didn't work.

The client SharePoint is migrated to MS O365.

Do you have any alternate method to resolve the error using the VBO?

------------------------------
Amrutha Sivarajan
------------------------------