cancel
Showing results for 
Search instead for 
Did you mean: 

Modified trigger should give previous values for fields changed

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. 

 

Status: Started

Hi all,

 

Happy to announce that we started the development of building granular trigger for SharePoint item and file changes along with the plan to provide old and new values.

 

To be able to infer and provide old and new values, we will first need the ability for a trigger that can run when an item is modified and then the ability to get what changed for that modified item. So, to support this, we will be releasing a new trigger and a new action that works along with this new trigger to help you get started. 

 

  1. 'When an item or file is modified' trigger
    1. Only triggers on an item or file updates, not on an item or file creation.
  2. 'Get item or file properties changes' action
    1. This new action returns information about whether or not a column's value was modified.
    2. This action when released will:
      1. Only work with the 'When an item or file is modified' trigger.
      2. Require versioning to be turned on for the associated list or library 

 

With these two updates, you can now build a flow when someone modifies a list or library and then using the new action check if a particular column or file property was modified since the last flow run. For example, you can check if the Status column was modified since the last run and then get the current Status value, else do something else.  

 

After this update, we will continue to work on enabling the 'Get item or file properties changes' to provide old and new values of the columns. 

 

Thank you all for being patient with us. Will update this thread as we have more updates.

 

Thanks,

Chakkaradeep

Comments
Helper II

I found this post while looking to do exactly this.

A thousand vote-ups to this suggestion.

 

I am looking to create a history entity in CDS to record all updates and deletes from my primary CDS entity. A flow triggering on updates and deletes seems like a simple way to do this but without the functionality asked for here I need to insert into my history table on inserts and updates and record the current values rather than the previous ones. This makes the history table is not a history but a history plus all current values. Not what we want.

Suggestions for alternative implementations are welcome.

Frequent Visitor

Can't understand why MS have not done this yet. Their servers must be getting hammered by these requests. I had two flows doing this for over a week and only have just seen the warning when I looked to update. The Before and After property should be available in Flow.


 



 

Frequent Visitor

Yes, we definitely need this! 

Regular Visitor

Yes. This will add more value to Flow. 

Advocate V

Yes, very basic feature which is often needed.

Power Automate
Status changed to: Under Review

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

Advocate V

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?

Frequent Visitor

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.

 

Advocate I

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.

New Member

Must to have