MicrosoftOffice365 Activity Scope - Asset Connection: Could not retrieve the selected asset: 'Folder does not exist or the user does not have access to the folder. Ok: False'

Feedback Activities
, ,
1

Hello UiPath Community,

I’ve apparently encountered a bug with the MicrosoftOffice365 activities that I believe needs attention. Our team has developed an automation using the MicrosoftOffice365 activity scope with the Asset connection configuration, which worked flawlessly in the development environment. However, upon deploying to production, we faced a critical issue.

Issue Description: During the connection setup in the development environment, the activity requires manual selection of the asset through modern folders. Unfortunately, there’s no functionality to use variables for this process. The problem arises when the folder IDs and asset IDs, which are tied to the workflow, do not translate to the production environment. This results in the automation crashing on the scope activity due to an inability to retrieve the assets.

Error Message: Microsoft 365 Scope - Asset Connection: Could not retrieve the selected asset: 'Folder does not exist or the user does not have access to the folder. Ok: False'

Workaround: The temporary solution involves manually signing into the Orchestrator production tenant from Studio, reloading the assets, selecting the asset from production, and republishing the artifact.

Additional Information: We have thoroughly reviewed the folder names, structure, and robot permissions, and confirmed that they match exactly with the development tenant settings.

Request: We would greatly appreciate it if this bug could be addressed in the next package release to ensure a smoother deployment process for our team.

Thank you for looking into this matter.

Best regards,

Bruno Costa

4

Hi Community,

Could someone help me out with an update on this?

5

Can you try by specifying the full path of the Orchestrator asset containing connection details?

Sample path of the Asset "Folder/Folder1/Folder2/AssetName"

A screenshot displaying the error message "The authentication parameters could not be read" in a Microsoft 365 Scope within the UiPath automation workflow. (Captioned by AI)
A screenshot displaying the error message "The authentication parameters could not be read" in a Microsoft 365 Scope within the UiPath automation workflow. (Captioned by AI)1389×548 34.6 KB

Try to run the Studio project
Publish the new version of the process/library
Retry to run it under the production robot

2 Likes
6

Hey @marian.platonov,

Thank you so much. I’ve overlooked this property back when I was working on this.
I just ran a quick test and using the Runtime connection assets configuration did the trick. The only downside is that it seems to take longer to authenticate and start the inner activities, but I’ll take that.

Best,

Bruno Costa.

1 Like
7

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.