I built a workflow in Studio that uses several of the Integrations/Microsoft/Office 365/Files activities (these are the Windows activities that utilize connections from Integration Service).
My workflow in Studio works perfectly–it accesses several different Sharepoint and Teams sites that the Connection has access to. So the next step is to make it run unattended from Automation Cloud.
So I created a Process in a modern folder on Automation Cloud. While setting up the Process, on the “2 Package Requirements” page, I see two Connection (Microsoft OneDrive) sections. My workflow has 6 activities that use an Integration Service Connection. Presumably, the two that are displayed are the “first ones”(?). I am unable to configure them to anything other than the default of “In Location* – OneDrive”. There are options on the dropdown for Sharepoint, Shared with Me, and Groups, but all three options just present a screen that says “Loading” forever.
The problem with “In Location* – OneDrive” is that when the Process runs, it tries to access OneDrive files for the user of the Connection (For Each File/Folder, etc.) and ignores the URL path or O365DriveRemoteItem that is supposed to be used per the code.
Has anyone successfully configured a Process for O365 connectors that uses multiple activities so that it runs Unattended and accesses files in Teams/Sharepoint?
@Anil_G ,
Yes, the connection named “Corp Accounting” is the one I used in all the activities in Studio as well.
I created that connection in the browser in Automation Cloud / Integration Service using the credentials for a “bot account” that has access to the appropriate Sharepoint/Teams sites.
I will try creating a different connection and seeing how that goes.
Interestingly, I did try to configure the Process to run from Assistant on my local machine and could never get past the “configure connection” for the Integration Service.
I have successfully used that “Corp Accounting” connection unattended previously in simple demos where there was only one or two activities and one .xaml in the workflow, so I don’t know if this is a bug with more complex workflows. I am also opening a support case with UiPath and will post here if that yields answers as well.
An update–I had a hunch that the problems I was experiencing with the Integration Connections might be related to the fact the original workflow had been converted from Windows Legacy to Windows (before I replaced all the old O365 classic and/or SharepointActivities code with Integration Service). So I rebuilt the entire workflow from scratch as a clean Windows project, and no more problems! All works fine. UiPath support said they would investigate whether there is some kind of issue with workflows converted from Legacy.
Once you rebuilt the bot what settings did you use to allow the bot to use the user defined locations vs what is available in the connector. I am creating nested folders using variables and adding the Parent folder in here undoes all of the variables in the bot.
