Forum Discussion
Connector Compatibility Issues with Updated Microsoft Teams
Dinesh-MSFT - I'm using the connector from Teams which is an outgoing webhook but managed only through Teams, not through the application and it broke with the New teams
Unable to edit those connections now
And this documentation is not updated that I could find:
https://learn.microsoft.com/en-us/azure/devops/service-hooks/services/teams?view=azure-devops
We will check on it and let you know the updates.
- SmonnahanJun 04, 2024Copper ContributorThis is severely hindering some processes, can you give me an update here. Or show me how I should do these differently and how I can update pre-existing connectors??
- Marcos_Almeida_360Jun 04, 2024Copper ContributorAre there any news on that? ChetanSharma-msft Dinesh-MSFT
On my side we are having similar problems with the office 365 connectors to MS Teams
https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/connectors-creating?view=msteams-client-js-latest
`teamId` is not returned anymore as part of `settings.getSettings()`
Could we get away without a `teamId`, i.e. are there guarantees that a `channelId` is unique inside a tenant without needing to resort to a `teamId` to achieve unicity.
Thanks in advance,- ChetanSharma-msftJun 06, 2024
Microsoft
Hello Marcos_Almeida_360 - Sorry to ask but just wanted to clear how you are checking the channedId value?
As per documentation here: https://learn.microsoft.com/en-us/javascript/api/%40microsoft/teams-js/microsoftteams.settings?view=msteams-client-js-1.13.1#@microsoft-teams-js-microsoftteams-settings-getsettings
I can't see any parameter related to teamId or channelId.
We can see only below values:Settings interface - Teams | Microsoft Learn
Could you please share the steps so that we can quickly check and try to resolve this issue?- Marcos_Almeida_360Jun 06, 2024Copper ContributorI am so sorry, I meant `getContext` just like in the topic:
https://learn.microsoft.com/en-us/javascript/api/@microsoft/teams-js/microsoftteams?view=msteams-client-js-1.13.1#@microsoft-teams-js-microsoftteams-getcontext
It should return a context object:
https://learn.microsoft.com/en-us/javascript/api/@microsoft/teams-js/microsoftteams.context?view=msteams-client-js-1.13.1
It returns a teamId
https://learn.microsoft.com/en-us/javascript/api/@microsoft/teams-js/microsoftteams.context?view=msteams-client-js-1.13.1
Before, we were getting a teamId along with a channelId when setting up a connector.
https://learn.microsoft.com/en-us/javascript/api/@microsoft/teams-js/microsoftteams.context?view=msteams-client-js-1.13.1
This made sense as the channel you set your connector on appears under a team on the UI; now we are NOT getting a `teamId` anymore.
Hence my question: can we consider that the channelId is unique for all channels in all teams in a tenant or this is a bug a we would need to have a channel and a team Id to know exactly where the connector is setup on.
Thanks in advance,