-
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
When storing data on Microsoft SharePoint, Microsoft willfully changes your file, thus the online timestamp and hash is always being updated. This is a feature (bug) of Microsoft SharePoint that cannot be turned off. The database stores the 'online' size as reported by the Microsoft Graph API. When a file is downloaded, this timestamp is used to set the timestamp of the local file so that:
In your scenario:
What should be happening is:
This is clearly not occurring, and defaulting to changing the online date. Because the online date is being changed, this is why a new version is being created. When the application is being run, is Additionally, file indexers (tracker, baloo and other) track that they have 'indexed' a file by modifying the local file timestamp to the timestamp that the file was indexed.
There is no work around for this issue - this appears to potentially be a logic issue.
This will not solve your issue. Next StepsI would like to review a debug log if possible, or, if you can share reproduction steps I can see if I can replicate this. To generate a debug log, create a new SharePoint site just for testing, and use dummy data, but keep all other environmental aspects the same. This will keep all sensitive data away, and only be pertinent to the test data / test SharePoint site. Once I have reviewed a debug log, and this is a logic issue, a bug will need to be raised for tracking purposes. |
Beta Was this translation helpful? Give feedback.
-
|
@mayasd Please raise a bug report. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. I created a new issue from this discussion #3521 |
Beta Was this translation helpful? Give feedback.


@mayasd
I have reviewed the code, and I think this is a bug and I have also already identified a potential fix.
Please raise a bug report.