Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
10,521 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 13%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
I have the same issue.
SharedWithMe endpoint wrong size and lastModifiedDateTime
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(121.6, 97%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDJ%3C/text%3E%3C/svg%3E)
Drake, Jared Bradley
6
Reputation points
https://graph.microsoft.com/v1.0/me/drive/sharedWithMe?$top=5000 returns incorrect information including LastModifiedDateTime and Size:
When getting the item with https://graph.microsoft.com/v1.0/drives/b!jWogh66yJkGn88Bx39SZEq8nWcMIu4xBtHRml83oI_eUjSojCZAtSpb-eAdT6rLP/items/01VHOGXYI7B5ELUDPMH5ALEPSMHCGPREZY it returns the correct information:
{count} vote
-
CarlZhao-MSFT 36,736 Reputation points2021-07-09T07:42:25.813+00:00 Are you requesting these two APIs at the same time?
-
Drake, Jared Bradley 6 Reputation points
2021-07-09T13:07:47.123+00:00 Yes, they were done at the same time. The second screenshot is the accurate information. The sharedWithMe endpoint is returning incorrect data based on size and last modified.
Sign in to comment
2 answers
Sort by: Most helpful
-
-
CarlZhao-MSFT 36,736 Reputation points
2021-07-09T10:06:08.933+00:00 Judging from the screenshots of your two requests, it is obvious that the file has been modified once in "2021-07-08T14:36:33Z". From the
lastModifiedByparameter in the second screenshot, should use the application permission without user participation, and the application modified the file on behalf of a principal. So thesizeandlastModifiedDateTimeparameters in the second screenshot have been changed.As for the different results you got using the
/sharedWithMeendpoint, I think there should be no synchronization.-
Drake, Jared Bradley 6 Reputation points
2021-07-09T19:01:33.053+00:00 I'm not sure I follow this. Those calls were done at the same time. Shouldn't they have the same size and lastModifiedDateTime's regardless of which user/application modified it. I guess I don't understand why sharedWithMe is outdated, while the specific item call shows the correct new size and lastModifiedDateTime.
-
CarlZhao-MSFT 36,736 Reputation points
2021-07-12T02:24:12.25+00:00 Append
?allowexternal=trueto the GET request. -
Drake, Jared Bradley 6 Reputation points
2021-07-12T02:32:28.05+00:00 Thanks for the reply, but we are still getting the same outdated information. The following is the item specific call:
vs the sharedWithMe call:
-
CarlZhao-MSFT 36,736 Reputation points
2021-07-12T06:50:32.807+00:00 Do you have
Files.ReadWrite.Allpermissions? -
Drake, Jared Bradley 6 Reputation points
2021-07-12T12:20:00.907+00:00 It looks like we do.
-
Drake, Jared Bradley 6 Reputation points
2021-08-04T13:08:39.917+00:00 Have we had any updates on this?
-
CarlZhao-MSFT 36,736 Reputation points
2021-08-05T09:48:40.297+00:00 Best @Drake, Jared Bradley , I have submitted this issue to Microsoft, I will follow up any updates on this thread and reply to you as soon as possible.
Sign in to comment -