Hi I am new to MS Flow but very enthusiastic. I have created two custom lists in office 365 SharePoint almost exact copies of each other. The first list contains high level problem statements the second list is an action tracker. What I would like to happen is when the "Status" field is changed from "New Item" to "Reviewed", the second list will be auto populated with the Id and Short Description fields. Sounds simple but only when you are in the know.
Any help would be much appreciated.
Solved! Go to Solution.
Hi Billy,
You just set a condition on your original list and on the yes of the condition you add a create Item task
Hope this helps,
Joe
@Anonymous:
I agree with @jaylou but would like to add that you might want to set some type of a flag in the source list to indicate that the task list has already been populated. Otherwise, you could end up with multiple entries in the task list if the source list is updated before the status is changed again.
By a flag, I mean a column that you set to indicate that the task has been created - usually a yes/no column. For example, at the top of your Flow, check the value of your flag. If it is set to yes (default is no), exit the Flow. Otherwise, continue. When you create the task, set the value of the flag to yes.
If you need an example, let me know.
Scott
Hello, @Anonymous!
Thank you for posting on the Flow Community Forum! Have you had an opportunity to apply @ScottShearer‘s recommendation to adapt your Flow? If yes, and you find that solution to be satisfactory, please go ahead and click “Accept as Solution” so that this thread will be marked for other users to easily identify!
Thank you for being an active member of the Flow Community!
-Gabriel
Flow Community Manager
Hi Billy,
You just set a condition on your original list and on the yes of the condition you add a create Item task
Hope this helps,
Joe
@Anonymous:
I agree with @jaylou but would like to add that you might want to set some type of a flag in the source list to indicate that the task list has already been populated. Otherwise, you could end up with multiple entries in the task list if the source list is updated before the status is changed again.
By a flag, I mean a column that you set to indicate that the task has been created - usually a yes/no column. For example, at the top of your Flow, check the value of your flag. If it is set to yes (default is no), exit the Flow. Otherwise, continue. When you create the task, set the value of the flag to yes.
If you need an example, let me know.
Scott
Hello, @Anonymous!
Thank you for posting on the Flow Community Forum! Have you had an opportunity to apply @ScottShearer‘s recommendation to adapt your Flow? If yes, and you find that solution to be satisfactory, please go ahead and click “Accept as Solution” so that this thread will be marked for other users to easily identify!
Thank you for being an active member of the Flow Community!
-Gabriel
Flow Community Manager
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
User | Count |
---|---|
13 | |
12 | |
10 | |
9 | |
6 |
User | Count |
---|---|
27 | |
20 | |
13 | |
12 | |
10 |