I upgraded a process to the new “windows” process type (alert at the top of studio), but now that I have done this my process can’t compile bcause the sharepoint package I was using is no longer. When I went into project dependancies the only option was to uninstall it.
I was using the uiPathTeam.SHarepoint.Activities because the other microsoft scope I could not get to connect and upload.
This is now permanently broken and I don’t know what to do.
It seems UiPathTeam.Sharepoint.Activities doesn’t support Windows compatiblity (.net6) yet. Please use Window-Legacy until it supports Windows compatibility (.net6).
The problem I am running into, is that now, with the new studio when I move a file (and its supposed to create a new folder for that file) its creating a folder shell without the proper extensions for a folder
Thank you very much for raising these issues. We are looking into them.
Regarding SharePoint Activities, we are working on making an upgrade to them so, you can use them on Cross-Platform as well as on Windows. The UiPathTeam.Sharepoint.Activities won’t receive an upgrade anytime soon, but, we will bring those functionalities in the Microsoft Office365 package.
What use cases are you trying to do, so we make sure we capture these features in the new package?!
Regarding your second issue, what activity are you using?
The new SharePoint Activities are working on Windows and Cross-Platform as well. They are meant to be used with Integration Service as they have Connections.
With the next release, we will offer you the possibility of using it with M365 Scope.
Also instead of using Find Files and Folders which is a very old activity I am suggesting for you to use