Forum Discussion

ms-user-1's avatar
ms-user-1
Copper Contributor
May 03, 2024

Connector Compatibility Issues with Updated Microsoft Teams

Hi,   We have been successfully using our app connector for several years without issues. However, since upgrading to the latest version of Microsoft Teams, we have encountered significant function...
developer
microsoft teams
Settings
ChetanSharma-msft's avatar
ChetanSharma-msft
Icon for Microsoft rankMicrosoft
May 21, 2024
Hello Smonnahan - Thanks for your inputs.
We will check on it and let you know the updates.
Marcos_Almeida_360's avatar
Marcos_Almeida_360
Copper Contributor
Jun 04, 2024
Are 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-msft's avatar
    ChetanSharma-msft
    Icon for Microsoft rankMicrosoft
    Jun 06, 2024

    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_360's avatar
      Marcos_Almeida_360
      Copper Contributor
      Jun 06, 2024
      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,
      • Dinesh-MSFT's avatar
        Dinesh-MSFT
        Former Employee
        Jun 06, 2024

        Hi Marcos_Almeida_360 - We are checking this issue with engineering team and let you know the update.