Forum Discussion
Connector Compatibility Issues with Updated Microsoft Teams
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,
MicrosoftHello 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?
- I believe they discontinued the functionality now instead of producing a fix. you need to delete and recreate differently. I could be wrong, but that's what we ended up having to do.
Hi Smonnahan,
We didn't have repro earlier. we are checking this issue internally and we have raised a bug recently for this.Dinesh-MSFT what does that reply even mean? Were you able to replicate the issue? were you able to figure out this bug? I've seen no posted updates on this bug in over 100 days and when a bug is a blocker, I would think your team would be giving actual updates and there have been zero updates on what's going on here. You raised the bug, but where did it actually go and what type of expectations should we have here?
Hi Marcos_Almeida_360,
Sorry for the delay in the response. We have raised the bug, and we will keep you posted on the updates.Hi Marcos_Almeida_360 - We are checking this issue with engineering team and let you know the update.
- I 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,
