cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Helper I
Helper I

How to determine if a specific field in sp list has been updated in my Flow

I've seen previous threads on this topic from 2018, but just wondering if we're REALLY expected to create a duplicate SP column and manage the check in our flow between previous status column and current status column with the trigger of When a SP item is created or modified just to see if a field has been updated in our SPO to trigger some actions...... please tell me this has been fixed and is easy to do and I'm just not able to figure it out.

 

Here's my scenario;  

When a specific field (Status) in the SP list has been updated (can be from pending confirmation, Fast Track or Design Track), then we need to trigger a planner creation or sending of emails etc based on the status change.  We already have over 100 columns in this complex SP list, and many changes can be made.  It seems pretty poor if we really have to manage the duplication of columns and set previous and current etc or worse, create a shadow list to compare with for each change and update to synch. 

 

Can't we check if the item field has been updated with the edit date or something?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Community Support
Community Support

Hi @LC1Ama,

 

@efialttes's method is very close to the way of your issue, actually, get the previous version of an item is the only way could do in Power Automate for now:

Get the previous version of item>> compare with the lasted version>>If the special column changed>>do the next steps.

There is a blog write by @ScottShearerCheck-for-a-Change-in-a-SharePoint-List-Column-Value.

Hope it will help you something.

 

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

 

View solution in original post

4 REPLIES 4
Highlighted
Dual Super User III
Dual Super User III

Hi!

There are several techniques to solve the limitation you describe. One of them is to add a new column to store last status value. Another approach is to activate Version History on your SP list, so your flow can compare current Status value and also last value stored by means of 'Send an HTTP request to Sharepoint'; in order to avoid infinite loops. IMHO, this second approach is the most precise strategy, but also the most complex to implement. You will find an example here

 

You can get a good overview of most of these approaches in the following post

https://powernimbus.com/2019/06/microsoft-flow-avoiding-the-sharepoint-list-update-trigger-infinite-...

Hope this helps



Each time you click on any of our inspiring answers 'Thumb up' icon...
...an ewok scapes from the stormtroopers.

Be grateful, Thumbs up! Save the Galaxy for free!


Escribo sobre Power Automate en:
https://medium.com/anyone-can-automate/

Proud to be a Flownaut!



Highlighted
Community Support
Community Support

Hi @LC1Ama,

 

@efialttes's method is very close to the way of your issue, actually, get the previous version of an item is the only way could do in Power Automate for now:

Get the previous version of item>> compare with the lasted version>>If the special column changed>>do the next steps.

There is a blog write by @ScottShearerCheck-for-a-Change-in-a-SharePoint-List-Column-Value.

Hope it will help you something.

 

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

 

View solution in original post

Highlighted

Thanks for the feedback.  It is in fact what we're doing, but just seems sooo incredibly sloppy for a solution and actually adds additional processing for the Flow and size of the SP List.  For example we have 3 fields that we need to monitor so therefore we have an addition 3 columns to manage with every update.  NUTS - I just can't believe MS can't give us the simple option to check If fieldx = updated.

 

Hoping MS are looking into this option for future versions!

Highlighted

Thanks for the feedback appreciate the idea to check the version history - hadn't thought of that!!

I'll look into that option.  However, a bit worried about the processing time to connect to the server for every change that is made to to the SP list.  We already have some processing time issues with the flow - sometimes takes 20 minutes to complete the flow!  This might be due to internal connectivity issues though, not sure.

 

 

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

Top Solution Authors
Top Kudoed Authors
Users online (9,816)