cancel
Showing results for 
Search instead for 
Did you mean: 

Create a trigger for SharePoint list columns

It would be nice to have a trigger if a certain column in a SharePoint list is modified. For example, if the column "Status" is modified, or if the column "Assigned To" is populated. So we don't have to use the trigger "When an item is created or modified", where you have to create a lot of workaround conditions just to make sure that the column that was updated is what you need. 

Status: Completed

Hi all,

 

Happy to update that this feature is now rolled out to and available for use. The documentation is updated as well:

For more info about how to use this action, see this tutorial: Introducing 'when an item or file modified' trigger and 'Get changes' action

 

Thank you all for the feedback and please let us know if you have any questions.

 

Thanks,

Chakkaradeep

Comments
Regular Visitor

@Audrie-MSFT 

 

Audrie, this does help tremendously for at least my situations. 

 

You could set up flows for each state of the the status processes

 

If (Status = Pending) Do stuff

If (Status = Approved ) Do stuff

If (Status = Rejected ) Do stuff

 

Only one would fire each time, eliminating the duplicate runs and making it much easier to access the history. You could still get a lot of garbage runs where edits are made during a particular state though so it might not be perfect for every situation. 

 

In that case, you might want to filter on a dynamic value, which you can do as well by doing using a duplicate column that's only updated by the workflow.

 

If (Status Field != OldStatus Field) Set OldStatus to Status, Do Stuff

 

This would then only trigger if the status column is changed. 

Power Automate

@Stander thank you! 🙂

Adding @Chakkaradeep as an FYI too

Frequent Visitor

Hi all - John Liu posted a great work around utilizing SharePoint's versioning feature.

 

I found his guide and illustrations extremely helpful - a big thank you to John, wherever he may be!

 

John Liu's - microsoft-flow-sharepoint-trigger-on-specific-fields-changed-via-sp-http-request

 

This involves the following actions

1) Send an HTTP Request to Sharepoint

  • to obtain the item version results on item change

2) Select Data Operation

  • to map results of item change to use in conditional comparison

3) Condition

  • to determine if column changed from last version

4) Create HTML Table

  • to help identify when the specified column is changed and what change was made
New Member

You realize that there is a template, "Send a push notification when a column is changed in a SharePoint list" already in Flow? I called support about this, but the person I was working with insists that it will not work on a column, only a whole item. I personally believe he is mistaken and that he has not taken the time to analyze the template - it's a pretty complex one that's beyond my capabilities, but I would think an "expert" would have a better understanding.


Advocate II

@PhilGold - Thank you for sharing that.  It would be amazing if microsoft could roll all this logic up into a single control. 

Frequent Visitor

Is there an update on this functionality?

Frequent Visitor

This single item has been requested and posted for more than 2 years and warrants more than a "review" from MS developers.  Clearly, there is a need if you review the multitude of workarounds.  Finally, MS has provided a really functional suite of services to help many business needs. 

Currently, due diligence should be performed to evaluate based on true need that comes from many varying industries.  What is happening now is that the influx of options is going to lead to a solution for purchase (lost revenue for MS) that business users will gladly purchase.  For me, if I have to purchase another product for functionality that could have been provided --- I have no true use for attempting to use advanced features.

 

Advocate I

I am wondering if we should request in Sharepoint User Voice.   I am not sure which development team would be implementing this.    Sharepoint or Flow.

 

 

Frequent Visitor

Definitely can't hurt.  I will see if it already exists in that space.  Thanks for the suggestion.

Advocate II

UserVoice is a black hole.