Forum Discussion

Todd Lane's avatar
Todd Lane
Brass Contributor
Mar 13, 2022

Best Approach for a kind of change history

Hi,   I have a Sharepoint Contact list with about 7000 records.   I would like to create a history on a couple of specific fields that captures old content, new content, when changed and by who. ...
developer
seanachim's avatar
seanachim
Copper Contributor
Mar 29, 2022

Todd Lane 

 

I'm guessing that you want a broader auditing capability that the typical version control can't satisfy. I'm sure that you've already spent a bit of time enabling version control and going through the various versions and then found out that it was a pain to report on...

 

The Use Case you are describing seems to point toward a common auditing list that has the capabilities you have described as columns.  This can then be updated whenever you target/intended list or library is changed using Power Automate, which can be fired off on any CRUD statement made to a SharePoint object.  It can also perform CRUD actions on any other SharePoint/Exchange/Supported Environment as a specified action.

 

If Power Automate were to update your "Auditing Table" you could then pull any report you wanted using Power BI, Excel or any other of your favourite reporting tools.

 

If your SP environment is On-Premise (excellent choice in my opinion) then you will need to install the connectors and gateway for Power Automate to work, but if it is on a 365 tenant then you already have the tools.