Export API getAllMessages lastModifiedDateTime is not updated

Question

Export API getAllMessages lastModifiedDateTime is not updated

Nikita Krivets 501

Hello,

When I use Export API ( https://learn.microsoft.com/en-us/microsoftteams/export-teams-content ), say "users/335f3c99-ff13-42b4-99c7-2664e1a03deb/chats/getAllMessages" endpoint, it provides me the the following response:

{  
    "@odata.type": "#microsoft.graph.chatMessage",  
    "id": "1655935493202",  
    "replyToId": null,  
    "etag": "1655935493202",  
    "messageType": "message",  
    "createdDateTime": "2022-06-22T22:04:53.203Z",  
    "lastModifiedDateTime": "2022-06-22T22:04:53.203Z",  
    "lastEditedDateTime": null,  
    "reactions": [  
        {  
            "reactionType": "laugh",  
            "createdDateTime": "2022-07-22T18:50:45Z",  
            "user": {  
                "application": null,  
                "device": null,  
                "user": {  
                    "id": "f16736b6-02f1-4240-b5b4-fd6e16d3cbaf",  
                    "displayName": null,  
                    "userIdentityType": "aadUser"  
                }  
            }  
        }  
    ]  
}

lastModifiedDateTime is not changing to the time of reaction.

message -> "lastModifiedDateTime": "2022-06-22T22:04:53.203Z"  
reaction -> "createdDateTime": "2022-07-22T18:50:45Z",

But if you use a different endpoint e.g. "users/user@tenant .onmicrosoft.com/chats/19:9677d27140684c9aa74012ff4883c604@thread.v2/messages", you will get a different response:

{  
    "id": "1655935493202",  
    "replyToId": null,  
    "etag": "1658515845455",  
    "messageType": "message",  
    "createdDateTime": "2022-06-22T22:04:53.203Z",  
    "lastModifiedDateTime": "2022-07-22T18:50:45.456Z",  
    "lastEditedDateTime": null,  
    "deletedDateTime": null,  
    "reactions": [  
        {  
            "reactionType": "laugh",  
            "createdDateTime": "2022-07-22T18:50:45.47Z",  
            "user": {  
                "application": null,  
                "device": null,  
                "user": {  
                    "id": "f16736b6-02f1-4240-b5b4-fd6e16d3cbaf",  
                    "displayName": null,  
                    "userIdentityType": "aadUser"  
                }  
            }  
        }  
    ]  
}

and lastModifeddateTime is actually updated here.

message -> "lastModifiedDateTime": "2022-07-22T18:50:45.456Z",  
reaction -> "createdDateTime": "2022-07-22T18:50:45.47Z",

Is Export API supposed to handle such situations and update lastModifiedDateTime?

Nivedipa-MSFT 3,946 Reputation points Microsoft External Staff Moderator

2022-07-26T06:44:26.607+00:00

@Nikita Krivets - We are investigating your query. We will get back to you once we have any update.
Nivedipa-MSFT 3,946 Reputation points Microsoft External Staff Moderator

2022-08-02T10:29:52.11+00:00

@Nikita Krivets - We are checking this with engineering team. We will update you soon
Nikita Krivets 501 Reputation points

2022-08-02T16:40:13.62+00:00

@Nivedipa-MSFT Ok, thanks!
Nivedipa-MSFT 3,946 Reputation points Microsoft External Staff Moderator

2022-08-05T08:18:46.127+00:00

@Nikita Krivets - There is already bug raised for this issue. We will let you know once we have any updates on it.
Graham Norris 66 Reputation points

2024-02-27T17:18:37.7533333+00:00

Hello @Nivedipa-MSFT , has there been any progress on this bug? I am also seeing that new reactions on old posts don't get picked up as modifications by the Export API filtering on LastModifiedDateTime.
Graham Norris 66 Reputation points

2024-02-27T18:53:27.5966667+00:00

I would love to be able to query for messages that have new reactions using the Export API.
ChetanSharmamsft 1,036 Reputation points Microsoft External Staff Moderator

2024-03-01T15:02:24.46+00:00

Hello @Graham Interop - Sorry for delay in response.
We will check on it and let you know the updates.
ChetanSharmamsft 1,036 Reputation points Microsoft External Staff Moderator

2024-03-01T15:04:03.6066667+00:00

Update: We have checked with engineering team and this issue is fixed.
Could you please verify it once and let us know if it is fixed for you?
Graham Norris 66 Reputation points

2024-03-13T05:50:18.6433333+00:00

The issue is not at all fixed, sorry. If I react to a message of mine from January today, its LastModifiedDateTime is updated to today. But the message doesn't arrive if I use the Export API to filter on messages whose LastModifiedDateTime is in March. It does however arrive if I filter on messages whose LastModifiedDateTime is in January.

Here are the parameters I am using to filter on LastModifiedDateTime

Here is the code that generates the filter. I'm definitely filtering on LastModifed.

Here is the message they bring up. Its LastModified is in March, months later. But that was caused by adding a reaction, so the Export API can't see it. It comes on an Export pull filtered by LastModified dates in January.
Nivedipa-MSFT 3,946 Reputation points Microsoft External Staff Moderator

2024-05-27T05:06:35.6433333+00:00

@Graham Norris - We are checking this with engineering team. We will update you soon.
G 5 Reputation points

2024-09-10T17:03:45.78+00:00

@Nivedipa-MSFT any update on this issue?

1 answer

Your answer

Nivedipa-MSFT 3,946 Reputation points Microsoft External Staff Moderator

2022-07-26T06:44:26.607+00:00

@Nikita Krivets - We are investigating your query. We will get back to you once we have any update.
Nivedipa-MSFT 3,946 Reputation points Microsoft External Staff Moderator

2022-08-02T10:29:52.11+00:00

@Nikita Krivets - We are checking this with engineering team. We will update you soon
Nikita Krivets 501 Reputation points

2022-08-02T16:40:13.62+00:00

@Nivedipa-MSFT Ok, thanks!
Nivedipa-MSFT 3,946 Reputation points Microsoft External Staff Moderator

2022-08-05T08:18:46.127+00:00

@Nikita Krivets - There is already bug raised for this issue. We will let you know once we have any updates on it.
Graham Norris 66 Reputation points

2024-02-27T17:18:37.7533333+00:00

Hello @Nivedipa-MSFT , has there been any progress on this bug? I am also seeing that new reactions on old posts don't get picked up as modifications by the Export API filtering on LastModifiedDateTime.
Graham Norris 66 Reputation points

2024-02-27T18:53:27.5966667+00:00

I would love to be able to query for messages that have new reactions using the Export API.
ChetanSharmamsft 1,036 Reputation points Microsoft External Staff Moderator

2024-03-01T15:02:24.46+00:00

Hello @Graham Interop - Sorry for delay in response.
We will check on it and let you know the updates.
ChetanSharmamsft 1,036 Reputation points Microsoft External Staff Moderator

2024-03-01T15:04:03.6066667+00:00

Update: We have checked with engineering team and this issue is fixed.
Could you please verify it once and let us know if it is fixed for you?
Graham Norris 66 Reputation points

2024-03-13T05:50:18.6433333+00:00

The issue is not at all fixed, sorry. If I react to a message of mine from January today, its LastModifiedDateTime is updated to today. But the message doesn't arrive if I use the Export API to filter on messages whose LastModifiedDateTime is in March. It does however arrive if I filter on messages whose LastModifiedDateTime is in January.

Here are the parameters I am using to filter on LastModifiedDateTime

Here is the code that generates the filter. I'm definitely filtering on LastModifed.

Here is the message they bring up. Its LastModified is in March, months later. But that was caused by adding a reaction, so the Export API can't see it. It comes on an Export pull filtered by LastModified dates in January.
Nivedipa-MSFT 3,946 Reputation points Microsoft External Staff Moderator

2024-05-27T05:06:35.6433333+00:00

@Graham Norris - We are checking this with engineering team. We will update you soon.
G 5 Reputation points

2024-09-10T17:03:45.78+00:00

@Nivedipa-MSFT any update on this issue?

Answer 1

Graham Norris 66

Any update to this issue @Nivedipa-MSFT ?

I created a demo of the problem here
https://www.youtube.com/watch?v=kM55e60zTQw

Graham Norris 66 Reputation points

2024-08-13T16:23:31.41+00:00

@Nivedipa-MSFT we are still seeing this bug. Is it possible that MS are uncomfortable having filtration based on the real lastmodified time of messages when it is due to reactions? My thought is that perhaps this is seen as not a "real" modification because it's performed by someone other than the message's author. My other idea is that maybe because new reactions do not cut a new version of messages in the getAllRetainedMessages API, they are seen as unimportant. Can you confirm or deny either of these speculations?
Nivedipa-MSFT 3,946 Reputation points Microsoft External Staff Moderator

2024-09-16T17:51:43.1933333+00:00

Graham Norris - Apologies for the delay. We are checking the status of the bug with engineering team, we will let you know once we get any updates from them.
G 5 Reputation points

2024-11-12T20:30:15.1+00:00

@Nivedipa-MSFT Any update on this issue?
Nivedipa-MSFT 3,946 Reputation points Microsoft External Staff Moderator

2025-02-04T07:01:44.97+00:00

@Graham Norris, @G - Thank you for your inquiry regarding the status of the bug.

We understand your concern. We are actively checking with the engineering team for any updates on the issue. While there are no new updates at this time, we will inform you as soon as we have more information.

We appreciate your patience and understanding in the meantime. Thank you for bringing this to our attention.
Graham Norris 66 Reputation points

2025-02-04T07:19:36.1466667+00:00

Not to worry, I believe that MS fixed this issue quite a few weeks ago now.
G 5 Reputation points

2025-02-04T12:34:05.8233333+00:00

Appreciate the follow up Nivedipa. Microsoft fixed this for us as well.

@Graham Norris - thanks for the video showing this behavior.

Share via

Export API getAllMessages lastModifiedDateTime is not updated

1 answer

Your answer