When triggering a Flow on the modification of a list item then it should be possile to get the current and previous values of the fields that were changed.
We are looking into this item now and we hope to use versioning as previous values will be retained by SharePoint for a finite period of time as it's configured to do so when you use versioning. For now, as a workaround, if you are familiar with the REST APIs, you could enable versioning in the list or the library and then use 'Send HTTP Request to SharePoint' to get the current and previous values of the fields that were changed.
We are looking into this item now and we hope to use versioning as previous values will be retained by SharePoint for a finite period of time as it's configured to do so when you use versioning. For now, as a workaround, if you are familiar with the REST APIs, you could enable versioning in the list or the library and then use 'Send HTTP Request to SharePoint' to get the current and previous values of the fields that were changed.
It seems I miss something. How do we use 'Send HTTP Request to SharePoint' to get the current and previous values of the fields that were changed exactly? Someone has an simple example?
What about those of us that aren't familiar with REST APIs? I'm new to SharePoint and at first had difficulty identifying when a single field changed since SP Flow looks at the entire record. I quickly found SP Designer and was able to build most of my workflows there with little or no issues. Unfortunately, I've been told that SPD is highly discouraged so I'm having to rebuild in SP Flow. I don't understand why a new and supposedly better version drops so many significant features.
Bump. This is needed. I am working on something similar now and trying to figure out how to scan previous versions of items in sharepoint to get this to work.
We are looking into this item now and we hope to use versioning as previous values will be retained by SharePoint for a finite period of time as it's configured to do so when you use versioning. For now, as a workaround, if you are familiar with the REST APIs, you could enable versioning in the list or the library and then use 'Send HTTP Request to SharePoint' to get the current and previous values of the fields that were changed.
Thanks,
Chaks