MS Team [BETA]用于响应的消息对象属性类型的API [英] MS Team[BETA] API for Message object property type for reaction

查看:157
本文介绍了MS Team [BETA]用于响应的消息对象属性类型的API的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试为根据文档,提供的反应的示例响应属性如下

As per the documentation, the sample response properties for reaction provided are below Documentation sample response

"reactions": [
            {
                "reactionType": "like",
                "createdDateTime": "2019-01-21T19:55:51.893Z",
                "user": {
                    "application": null,
                    "device": null,
                    "conversation": null,
                    "user": {
                        "id": "e1ecb745-c10f-40af-a9d4-cab946c80ac7",
                        "displayName": null,
                        "userIdentityType": "aadUser"
                    }
                }
            }
        ]

从文档用户身份,键入

From the documentation user is Identity type identity set Identity is of type:

{
  "displayName": "string",
  "id": "string",
  "tenantId": "string",
  "thumbnails": { "@odata.type": "microsoft.graph.thumbnailSet" }
}

从示例响应以及端点响应中,不存在 tenantId .

From the sample response as well as the response from endpoint, tenantId is not present.

样品响应/实际终点响应与记录的属性有所不同:

There is a difference in sample response/actual endpoint response and documented properties:

  • 具有tenantId的一个或不具有tenantId的一个.
  • 根据属性文档,用户为1级,但根据实际响应和示例响应,用户属性的用户为in.

应该看到什么是反应特性的正确方案,因为我们看到文档和实际响应之间存在差异?

推荐答案

@KritikaVohra,请考虑您从

@KritikaVohra, Consider the response that you receive from the https://graph.microsoft.com/beta/teams/{id}/channels/{id}/messages. You don't need tenant id here. in case in conversation if you need it, you can use it from turnContext.

这篇关于MS Team [BETA]用于响应的消息对象属性类型的API的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆