Audit SharePoint Field Changes with Power Automate Version History
Diesen Beitrag auf Deutsch lesen
Use the SharePoint REST versions endpoint to compare the two newest item versions and record field-level before and after changes.
TL;DR
Use Power Automate Send an HTTP request to SharePoint with a GET request to the item's /versions endpoint. Sort versions by VersionId, compare the two newest entries for selected internal column names, and record old and new values. Versioning must be enabled, and the flow should require at least two versions.
Original by Marcel Lehmann, on PowerPlatformTip. Read the original
This is our own summary, not a republication or full translation. Both publications are edited by Marcel Lehmann.
Governance takeaway
- Makers: Compare selected internal column names between the two newest versions to produce clear before and after values for each audited field.
- Admins/CoE: Enable versioning on relevant SharePoint lists and libraries, then guard flows against items with fewer than two versions.
- Security/Compliance: Store or distribute the generated field-level deltas as an audit trail, because the standard trigger exposes only the new state.
Frequently asked questions
How does Send an HTTP request to SharePoint retrieve previous field values?
A GET request to the item's /versions endpoint returns the field values stored in each retained SharePoint version. The flow compares those entries.
How can Power Automate compare the two newest SharePoint versions?
Sort the returned versions by VersionId in descending order, assign the first two entries to variables, and compare selected internal column names.
Why does a SharePoint version comparison need versioning enabled?
Versioning must be enabled on the list or library because the /versions collection supplies the historical entries required for a before and after comparison.