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: Under Review

Hi all,

 

We understand the pain points expressed here, and we are currently investigating options in building granular flow triggers for item updates and column changes in SharePoint.

 

We respectfully ask for your continued patience on this topic for the remainder of this calendar year. We are committed to a viable solution for our customers worldwide, and will continue to post updates here as we solidify our plans (which will most likely be early next year). Again, thank you for your patience, and your feedback on Microsoft Flow integrations with SharePoint.

 

Thanks,

Chakkaradeep (Chaks)

Comments
Level: Powered On

Hello Microsft, 

 

Any update or are we going to keep adding to this thread for no reason?

At least let us know if this is something you guys are working on or not working on.

 

Thank you.

Level: Powered On

I was able to find a work around for this in the interim of a fix being deployed.  You can add a condition with "modified" as the trigger and "is equal to" as the conditional setting.  You do not have to enter in a value for the 3rd field.  Leaving it blank will cause it to fire any time an item is modified.  Below is an example of my flow:

 

10-17-2018 10-09-23 AM.jpg

 

Level: Powered On

I was surprised to find that this is not a feature. It would help greatly if there was a quick solution.

Level: Powered On

Thanks for the suggestion @RobMichaels. I came up with a simillar solution for this. My problem is that the flow still triggers anytime a change is made to any part of the Sharepoint list. That forces the flow to trigger unnecessarily again and again, which is a huge waste of flow resources. Especially given that you only get 2000 flows a month before you have to start paying for them.

I imagine this solution would work for a very small business, but for any mid to large business, this solution is not scalable.

Level: Powered On

It's a bit of a round about way, but this is a workaround for the trigger problem: