onTeamsMemberAddedEvent()不适用于个人范围 [英] onTeamsMemberAddedEvent() not working for personal scope

问题描述

我正在使用Microsoft graph API为用户 https://graph.microsoft.com/beta/users/{userID}/teamwork/installedApps

I was using Microsoft graph API for installing the bot for a user https://graph.microsoft.com/beta/users/{userID}/teamwork/installedApps

在安装机器人时，onTeamsMemberAddedEvent()既用于个人作用域，也用于团队作用域，通过它，我向用户发送了欢迎消息.除了graph api，我还直接安装了bot，并且该功能被撤消了.

On installing the bot, onTeamsMemberAddedEvent() was called for the personal scope as well as for teams scope and through that, I was sending the welcome message to the users. Apart from graph api, I was also installing the bot directly and the function was getting revoked.

但是现在，此事件没有被调用，并且我无法从用户的个人范围获取sessionId.它仅适用于teamscope.

But now, this event is not getting called and I am unable to get conversationId from the personal scope of a user. It is working for teamscope only.

推荐答案

当您和另一个用户之间开始对话时，该对话将在以后的所有对话中保持不变，无论何时发生.当您开始与漫游器进行对话时，也是如此.只要您和漫游器存在于Teams租户中，就会创建一个单独的对话，并一直持续下去.

When a conversation is started between you and another user, that conversation is persisted for all future dialogs regardless of when they occur. The same is true when you start a conversation with a bot. A solitary conversation is created that is persisted for as long as you and the bot exist within the Teams tenant.

正因为如此， onTeamsMemberAddedEvent()在个人作用域中仅被调用一次.它仅在发生初始对话并创建对话时发生.此后，以后与该漫游器的所有对话都将被视为第一次对话的扩展.

It is because of this that the onTeamsMemberAddedEvent() is only called once in a personal scope. It only occurs when the initial conversation occurs and the conversation is created. After that point, any future dialogs with the bot are treated as an extension of the first conversation.

这篇关于onTeamsMemberAddedEvent()不适用于个人范围的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！