cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
CWilcox
Advocate I
Advocate I

SharePoint list item field updated

It would be good if we could set a 'Flow' to only work when the value of a field changes.

 

Example:

 

We have a 'column' with 3 possible options 1) Planning, 2) Promote, 3) Finished.

 

When a new item is created by default the column is set to 'Planning'.

 

Although many other changes may occur in other columns, we would only want the 'Flow' to start when this particular column is changed. But when other columns are changed no 'Flow' is triggered.

 

Hope this is something that could be implemented, as the current 'Flows' will run each time any column is updated.

1 ACCEPTED SOLUTION

Accepted Solutions
MWilliams86
Employee
Employee

If you use the Sharepoint Connector Trigger for When a Sharepoint item is created or modified and then a Switch case switchflow.PNG

You can accomplish this already. This will run everytime something is added or changed but it won't take any actions unless you define it to. 

View solution in original post

41 REPLIES 41
PLN
Advocate I
Advocate I

Today a trigger is generated if any field in a list is updated. This is not enough to generate effective workflows on sharepoint list. The sugegstion is to give the option of specify the Field of the list on to be considered to generate the trigger ...

Thanks

 

stevenhibble
Advocate I
Advocate I

When trying to build a workflow around a particular field in a SharePoint list, we have to use the "When an existing item is modified" condition and a check against a hidden "previous value" column. If the column and the previous value column differ, then do action. This gets more and more cumbersome with each additional column/flow. Instead, I'd like a condition that checks for a specific field being updated.

For example:

If I want to do a different event depending on the new value of the Status column, I have to write a flow like:

CONDITION: When an existing item is modified >
CONDITION: If Status does not equal Status (previous) >

CONDITION: If Status equals "Pending"

    ACTION: Email Approvers

    ELSE CONDITION: If Status equals "Approved"

        ACTION: Email Submitters

        ELSE CONDITION: If Status equals "Rejected"

            ACTION: Email Submitters

ACTION: Update Status (previous), set to Status

 

 

What I'd prefer is:

 

If I want to do a different event depending on the new value of the Status column, I have to write a flow like:

CONDITION: When a specific field is modified >

CONDITION: If Status equals "Pending"

    ACTION: Email Approvers

    ELSE CONDITION: If Status equals "Approved"

        ACTION: Email Submitters

        ELSE CONDITION: If Status equals "Rejected"

            ACTION: Email Submitters

Anonymous
Not applicable

I agree with this. It should be easy to add an IF statement for the flow to only look for changes in a specific column. For example, I only need to receive an email when an item in an Open Issues List has been changed from open to close. Simple!!

MWilliams86
Employee
Employee

If you use the Sharepoint Connector Trigger for When a Sharepoint item is created or modified and then a Switch case switchflow.PNG

You can accomplish this already. This will run everytime something is added or changed but it won't take any actions unless you define it to. 

CWilcox
Advocate I
Advocate I

 Hi MWilliams86,

 

Thanks for that, that sounds brilliant.

 

Thank you for the assistance.

Anonymous
Not applicable

@MWilliams86 indeed, but it does cost you extra runs...

hilary_stoupa
Kudo Kingpin
Kudo Kingpin

The suggested solution is great if you know the possible values for a field - but what if you want to do something only if the text in a field has changed, for example? Right now the only work around I've seen suggested is to store the "original" value in its own column so you can compare the old vs. the new value and take action, and then update the tracking column with the new value so they match again..... Feels awfully clunky.

Pandra
Advocate II
Advocate II

MWilliams86, thanks for the above suggestion. 

 

Interesting approach indeed. My case is a little different and this would not work:

 

I have an Onboarding list, and need to notifiy the next department when the current department updates the record. All departments indicate their completion by checking a separate Y/N box for their department - that's the trigger I need, simply when a value changes on a specific field. All of my "complete" fields are Y/N, so the Switch Case example would not work here, because all of the values I'm looking for are "Y" or "Yes"

 

Flow Team - we do need a new trigger based soley on when a value changes. That would make a lot of people very productive with this, and very happy. It's already part of the ..."when created or updated" trigger - a modified version of that would be great. Make it so! 🙂

 

 

 

 

 

MWilliams86
Employee
Employee

Hey Pandara,

 

You can accomplish your sceanario with a serires of nested Condition steps. 

 

When an item is created or modified -> Condition: IF department 1 checkfield IsBlank() -> Yes condition send email to department 1 for approval -> No condition: New Condition: IF department 1 checkfield = "y" or "yes" AND department 2 checkfield IsBlank(), ....

 

And keeping nesting for however meany departments you need with each department having its own checkfield for the Condition IF statements to check for. 

 

At least that's how I'd approach that scenario until different functionality is created in Flow. Smiley Happy

Pandra
Advocate II
Advocate II

 

 

 

 

mab17
Frequent Visitor

I'm creating a flow for a QC process that involves 5 different employees in our office.  As an item in a Sharepoint list gets modified, and when a Yes/No column in my list is changed from "no" to "yes", I've set up a condition for my flow to send an email to the next employee needing to work the QC process.  Unfortunately, the flow keeps dupicating emails to the first member of the QC process.  I'm struggling to figure out how to modify the flow so repeating emails are no longer generated to the initial first members of the QC process. Any suggestions would be greatly appreciated!

Flow issue.PNG

Anonymous
Not applicable

@mab17you could create an array (via compose action) where you store all the names of the persons already received an e-mail, and check this array before sending the next e-mails in line.

 

At least that's how I could tackle this one 😉

mab17
Frequent Visitor

@Anonymous Thanks for your reply.  I like your idea, however I'm still a little confused as to how to create an array.  I've searched for info but am new enough to FLOW not all instructions are helpful.  Any further direction would be greatly appreciated.

 

Anonymous
Not applicable

You will probably need the compose action to accomplish this.

See post below for some more information: https://powerusers.microsoft.com/t5/Building-Flows/create-array-in-apply-each/td-p/62719

nssystem
Advocate I
Advocate I

Further to this, by triggering on every change, we consume our allowance in a couple days. Need to be able to create an environment where the flow only coumnts when it actually does something. I set hidden fields, but flow still fires and counts against quote. Worse is that if the flow changes a column then it fires again so I pay for two flows every time I update a filed.... be awesome to run only when a specific field changes.    Use Nintex as a role model on this where they add a conditional section before th flow starts....   like start if this field ahances AND ... so we can create complex rules to determine if the flow even runs.      

I don't understand how this is marked as complete. I tried the solution and it obviously does not do what the original question wants.

 

If I want to do something when the status changes from A to B, if it so happens that the original status is A, and they make a modification to B, then the flow runs. Then, if someone changes another field, but the status is still B, then the flow runs again. That's not right. It should only run when the status is updated, not when "anything" is modified and the status remains B.

grahampasmurf
Advocate III
Advocate III

I searched and found a blog post that solves this issue using a combination of List Versioning and an HTTP Request.

 

SharePoint Trigger on specific fields changed via SP HTTP Request

 

http://johnliu.net/blog/2018/5/microsoft-flow-sharepoint-trigger-on-specific-fields-changed-via-sp-h...

 

I had to enable Item Version History in the list settings.  Then I added an action "SharePoint - Send an HTTP Request to SharePoint" and have it GET this Uri on my SharePoint site -

_api/web/lists/getbytitle('ListName')/items(10)/versions?$top=2

 

Last, I added a Select action to filter the output into an array -

body('SPREST-Versions')?['value']

and used a Condition to test if the new value is equal to the old value,

first(body('SelectVersions'))?['Title'] is equal to last(body('SelectVersions'))?['Title']

Read blog post for details.

Lexnnn
Helper II
Helper II

I have an approval process for list items and I wanted to send an approval email only when the status of the item changed from "Ordered" to "Ready".

 

The change of the status "Ordered" to "Ready" is an automized process so I though I would just put a "Wait until" or "Wait" function but this was not possible as the wait time is not always the same. I wanted to send an approval email from the moment it's ready so I have searched for a solution where there would be a check on a specific field. 

 

I tried using switch case or condition but there was a problem when other fields were updated and the condition was already fulfilled, it would send again an approval email:
eg item changed - Status is not "Ready" = Terminate (that's OK)
item changed - Status is "Ready" = send approval email (that's correct) but now item is changed again, other field is updated and the status is still "Ready" = approval email resent (that's not correct as it does not check what was updated" 

 

I did not want to use nested conditions or switch cases.

The solution link provided by @grahampasmurf with version checking did the trick!! http://johnliu.net/blog/2018/5/microsoft-flow-sharepoint-trigger-on-specific-fields-changed-via-sp-h...

 

Thank you for that!

 

It did require some adaptation but it works!

 

flowemail1.PNGflowemail2.PNG

- ID can be found in "See more" Dynamic content

- SPREST-Versions is just renamed "Send HTTP request to Sharepoint"

- In the Url, if you use space or other special chars, you need to pay attention to how it's written eg space = %20

- Value is the expression from the linked website Body('SPREST-Versions')?['value']

- Orderstatus = valuefield "ValoTeamwork" is not found via Dynamic content but via Output from "Select" When I used the Dynamic content value it did not work as "Valo Teamwork" contained the actual value and was passing it throung to "GroupSiteUrl" from Dynamic content which remaind always the same.

- HTML table is not needed but usefull to debug and make sure it works correctly

- Conditions can again be found on the linked website: first(body('Select'))?['Orderstatus'] - last(body('Select'))?['Orderstatus']

 

More about approval flow

https://powerusers.microsoft.com/t5/Using-Flows/Flow-and-SharePoint-List-Status/m-p/132299#M3532

 

 

Hope this helps!

 

sarah5
Advocate I
Advocate I

This is insane! There needs to be an easier solution for a highly requested feature. Not all of us who use microsoft flow know how to create complex coding like the solution offered here (which seems great so thank you, it helped) - http://johnliu.net/blog/2018/5/microsoft-flow-sharepoint-trigger-on-specific-fields-changed-via-sp-h...

 

There needs to be an automatic trigger where we can select via the dynamic content list to identify fields we want to be notified of any changes! 

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (3,730)