'teamsAsyncOperation_Retrieve' is ambiguous in the namespace

[pere]

I’m trying to ask for help here as a last resort after trying opening a ticket. Unfortunately, after hours of wait, UiPath staff asks for the same as always: to share my projects which them, which they already know I can’t.

I have this project I’m using the Microsoft Teams → Advances → Get Record, from UiPath.IntegrationService.Activities.Runtime.Activities.ConnectorActivity. I’ve used this successfully in the past. I’m using it with on object of “Teams async operation”. This performs a Microsoft Graph API operation, and stores the result in a variable. When I define this variable with CRTL+K in the “Output” textfield of the activity (as it doesn’t provide the functionality of CREATING the proper variable), it creates it as of “teamsAsyncOperation_Retrieve” type.

Well, when I try to run or debug the project, I get an

Framework/Process.xaml: BC30560: 'teamsAsyncOperation_Retrieve' is ambiguous in the namespace 'UiPath.IntegrationService.Activities.SWEntities.C53D8DD64B7_teamsAsyncOperation_Retrieve.Bundle'.

error.

I tried deleting the activity and recreating it, and the same for the variable; didn’t work.

After reading similar posts in the forum, I tracked it down to being caused by a dependency. I’m using a custom one that consists of a custom library I created and imported via “manage packages”. That comes from another Studio project I converted to a library. And it’s using that UiPath.IntegrationService.Activities.Runtime.Activities.ConnectorActivity package too.

So I tried removing the other same dependency (the one coming from the UiPath.UIAutomation.Activities package), as it’s the only of both that allows me to delete. It did nothing.

I also ensured both instances have the same version. That’s the case. But it doesn’t solve it.

I’ve read references saying that I sould be using custom namespaces but couldn’t find a single reference ever, anywhere, explaining how to accomplish that. Gosh, I even asked ChatGTP - after inventing and allucinating things fro some attemps, it confirmed that it doesn’t have an idea on how to do that.

Can anyone give a hint?

[ashokkarale]

@pere,

You can try to import this ambiguous namespace into workflow from Import panel.

Thanks,
Ashok

[pere]

Thanks. I never had to do such a thing before for it to work, with this or any other activity, but, anyway, that “ambiuous namespace” already appears on the list of “Imported namespaces”.

If there’s something else I’m missing when you say “importing it into workflow”, I’d be very grateful if you could explain it.