search

SharePoint / sp-dev-docs

SharePoint & Viva Connections Developer Documentation
https://docs.microsoft.com/en-us/sharepoint/dev/
Creative Commons Attribution 4.0 International
1.24k stars 1k forks source link

GetChange API Appears to Not List All Changes #9813

Open eogkdlty opened 1 month ago

eogkdlty commented 1 month ago

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

SharePoint REST API

Developer environment

Linux

What browser(s) / client(s) have you tested

Additional environment details

Describe the bug / error

Hi Microsoft,

When recursively fetching the latest changes using the following API:

GET "https://mitchellplasticwelding.sharepoint.com/sites/*************/_api/Web/Lists(guid'a4f73e8d-a560-4665-88be-64126730a419')/GetChanges"

we noticed that some items were retrieved via:

GET "https://mitchellplasticwelding.sharepoint.com/sites/*************/_api/Web/Lists(guid'a4f73e8d-a560-4665-88be-64126730a419')/Items"

do not appear in the GetChange API response. For example: Item ID: 474480 Relative URL Path: /Executive HR/Personnel Files//01. Contracts/09102023.pdf Could you please confirm if there is an issue with the GetChange API or if we are using the API incorrectly?

Thank you.

Steps to reproduce

  1. Recursively get changes by GetChange API until there are no more changes to get
  2. List items of the list that have the same list_id with step 1.
  3. Compare the results of steps1 & 2

Expected behavior

All the items obtained by the ListItems API should appear in the GetChange API.

ToshoSP commented 1 month ago

EDIT: Versioning works for me now as expected, so comparing file properties of two version of the same file is possible again.

I believe this issue is closely related to mine (https://github.com/SharePoint/sp-dev-docs/issues/9798).

From your description, it seems you want to compare changes in the Document Library file properties. Currently, these changes are not registered chronologically; only the most recent version is being saved. Consequently, there is nothing to compare with. The same problem occurs when using the API to get versions: only one version is returned even if the file had multiple changes to its properties. I have already sent a support ticket regarding this issue, but have not received a successful resolution.

I am extremely frustrated with Microsoft over this matter. This is a significant compliance issue if version tracking is malfunctioning across all SharePoint libraries. Accurate version tracking is essential for compliance and auditing purposes. The inability to properly track these changes undermines our ability to maintain records accurately and could potentially lead to serious compliance violations.