I am using Office 365 activities 2.0.1- to connect to SharePoint and Microsoft.teams.activities 0.5.1 to retrieve the messages from a channel. When i work indivdually, they are working fine, but I try to use them together in a same workflow : Get the list of all joined Teams: Method not found: ‘Void Microsoft.Graph.BaseRequest.set_Method(System.String)’.
I tried with different different versions on it but the error remains the same, I think it is a bug in studio itself , can you tell me which two versions(preferably to access sharepoint files and to retrieve messages from a channel).
The error you’re encountering is related to the version mismatch between the Microsoft Graph API library used by the Office 365 activities and the Microsoft Teams API library used by the Microsoft Teams activities. To resolve this issue, you need to use compatible versions of both libraries that work together.
I am experiencing the same issue as @Vi_Quad. This is a curious issue, as it’s enough that Office 365 activity package is installed in the same project as Teams activities, that the Teams activities do not work.
@ABHIMANYU_THITE1 - I can’t find the actity versions for Teams that you are referring - for UiPath.MicrosoftTeams, the highest activity version that is available for me is 0.5.1.
as an alternative, i had to divide this completely separate processes, have to run them separately.(First I am accessing SharePoint and downloading the files in process 1, then in next process, I am using the teams).
We are working to release a new version for Microsoft Teams that will work smoothly with O365 package.
There is some massive work there, so it might take a bit more time.
Thank you for your understanding.
I am looping also @Akshay_Agnihotri who is owing Microsoft Teams.
Best regards,
hi @cshan the Microsoft Teams package (v5xx) will be the latest connector offering (would be going GA this month or early next month) from Integration Service which should seamlessly work with Outlook and other IS connectors/packages. Can you please, let me know, if there are any issues in transitioning to IS package? If there is any particular activity/functionality/use-case that is needed on the IS MS Teams package, we could certainly prioritize and help in getting that enabled. The legacy/classic packages are under maintenance mode i.e. only bugs will be fixed, but there won’t be any further enhancements on the old/legacy package.
We cannot use IS because client is hosting UiPath On Premise.
However, we are looking to upgrade all processes to Windows compatibility, but the “legacy/classic” package, as you called it, is only Windows-Legacy compatible.
Would an upgrade to Windows compatibility be a consideration considering many customers will not have access to IS through On Prem hosting?
No, the issue still remains, i had to divide the process into separate process, for the next process, we shifted to sharedrive instead of sharepoint, i suggest you the same thing.
