I just attempted to install Studio 2023.4.2 onto another person’s computer (still logging in as myself to orchestrator) and that did NOT fix the problem.
I tried creating an entirely new shared folder and giving access to the Administrator group (of which my user is a member) the “AllView” and “Administrator” and “Folder Administrator” roles without any luck.
I also attempted to assign my user with the “AllView” and “Administrator” and “Folder Administrator” roles directly (without any luck).
Finally, I just saw (as I created a new UiPath “New Process” project from scratch) that the Package version for UiPath.MicrosoftOffice365.Activities has just be updated to version 2.2.2 today. After installing the new version of the package, I still cannot see any shared folders.
Some new information (still not solving the problem but perhaps shedding more light on the issue):
I updated the MSOffice365 Package to v2.2.2 then published my project again
In the newly published version, I edited the process to use the correct shared connections and while the “OneDrive & SharePoint” connection works correctly, when the automation reaches the point of using the first “Outlook 365” activity’s connection, I get the following error message in the logs: “For Each Email in Inbox: User does not have Connections.View permissions on the connection folder”
I do not understand how the same unattended user can access one of the shared connections in the shared folder but cannot access another shared connection in the same shared folder.
For greater clarity, both my account and the unattended robot account have “AllView” and “Administrator” roles assigned on the Shared Folder that contains the relevant shared connections. I have also created a new role called “ConnectionViewExplicit” that gives the granular permission of “Connections | View” to the unattended robot.
Additional information (no solution yet but a potential short-term workaround)…
Just a few minutes ago, I reinstalled 2023.4.0 (from the .msi installer package I still had saved on my laptop) on a different computer and confirmed I can see all the shared connections using my user in Studio 2023.4.0. Unfortunately I do not have the download for the 2023.4.1 msi. I intend to suspend the automatic updater if I can.
My latest response from UiPath support asked that I try with v2.2.2 of the Microsoft 365 activities package but as I mentioned above, I already tried that with no difference in behaviour in Studio 2023.4.2.
Well that is at least some good. I wanted to go back to 2023.4.0 as well after we figured out there is some issue with the integrations and 2023.4.2, but I only have the .msi for 2022.10.7, and I believe I got 2023.4.0 from an auto update.
Do you know if/where the 2023.4.0 .msi installer is available? I do not see it as an option to download from the Orchestrator-Downloads page.
I haven’t found a location where the specific version of the 2023.4.0 file can be downloaded from UiPath but I have uploaded a copy to dropbox that I can share. I don’t know how comfortable you are downloading .msi files from a relatively random dropbox link os please let me know if you would like me to share the link and I will do so until you have downloaded it, then I will remove the link.
I have now re-published the project (using Studio 2023.4.0 and UiPath.MicrosoftOffice365.Activities v2.1.1) that was experiencing errors in unattended mode when published from 2023.4.2 on the Outlook 365 shared connection. The process worked successfully in unattended mode using the same shared connection that was generating an error of missing “connection.view” permission when run after being published using Studio 2023.4.2.
My current theory is that when Studio 2023.4.2 generates the DLL’s, there is an error in how the Outlook 365 (and perhaps other activities) activity is generated in the object code.
I appreciate that Steve, but I found a workaround to get version 2023.4.1. I uninstalled UiPath 2023.4.2 from my machine, and then installed 2022.10.7 (I still had that .msi), and then I was able to use the auto-Update feature in Orchestrator, and then choose a specific version to be installed for my machine, and got 4.1 installed. Then I immediately disabled auto-update so I hopefully don’t run into this problem again haha.
Thank you for sharing your insight on this problem!
I am happy to hear that you found a workaround Mitchell. I may take the same approach to upgrade to 23.4.1.
I really appreciate your messages because I believe that having more than 1 customer reporting the same issue got the UiPath support team investigating the issue rather than endless suggestions of ineffective things to try.
I have now upgraded to 2023.4.1 (from 2023.4.0-beta) and the shared connections functionality is still working in Studio (as expected). I also successfully published a new version of my automated process and it is working correctly in unattended mode.
NOTE: I made no changes to the shared connections, permissions or logic/code or versions of packages to the process that was failing when published with Studio 2023.4.2. The net effect of my changes were to “roll-back” to Studio v2023.4.1 (from v2023.4.2). I accomplished this process by manually uninstalling UiPath from my local computer, then installing an old version of UiPath (2023.4.0-beta), then using Orchestrator to push a specific version to my machine (I forced the upgrade from 2023.4.0-beta to 2023.4.1 by Using Orchestrator | Tenant | Machines | | Edit Machine | Maintenance [tab] | Specific Version | 2023.4.1
@loginerror@Charlie_Greenberg@Anil_Vezendla Are you aware of the issue in UiPath Studio 23.4.2 that shared connections do not show? I am also facing the same issue that other people are mentioning, that when upgrading to 23.4.2 the shared connections do not show up. Even if we upgrade to the latest version of Microsoft 365 dependency (2.2.2) it still doesn’t work.
Hi @oscar - yes, I have submitted a support ticket to UiPath last week about both this issue and the missing shared folder connections in 2023.4.2 and yesterday evening, they acknowledged that they can reproduce the issue.
We had a similar issue as we were on 2023.4.2 studio release. I have managed to fix it by upgrading to 2023.4.4.
Here is a more detailed info from my response on a similar topic on forum.
Has there been any update on this? I am in the same scenario, the connections are useless for us unless we are able to access them across tenants using the same name or passing the ID via an asset etc
You can change the connection on the fly once you publish the process.
When you are the process to a folder in the Orchestrator you can configure the connection.
Infact it works so well I requested they extend the functionality to other activities.
Anil_G
sudster
rockchord
ashokkarale
Erimateia
rashmisingh2695
Yoichi
Santhosh_Perumal