I am trying to make a flow that will allow the initial user to request a list of materials. I need the second user (the person who makes orders) to be able to respond to the request with various suppliers and indicate which supplier is delivering which materials. Is there a way to make a list branch out like that?
Solved! Go to Solution.
You might want to do this as a Power App with a series of manually triggered flows to move things from one stage to the next instead of just an overall flow. Power Automate isn't very good at presenting a user interface for people to interact with. That's where Power Apps comes in. But Power Apps is much better at processing and approving things. So a combination of the two would be a good solution.
Hi @avan4
How you planning to get the data for request the list of materials and respond to the request? Microsoft Forms? Where you going to store this info?
Thanks
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogThe request will be submitted as part of a MS List, which is also where I would like the subsequent info to be stored
Hi @avan4
Believe thats SharePoint list? How you collecting the info? Using Microsoft Forms?
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogYes, it is a sharepoint based list, the info will be collected using the same list, not a form
Hi @avan4
Thanks for your quick reply.
How many lists you planning to have for this? The second person who make the orders will be collected in another list? Need to know bit more about your schema and process.
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogHi!
It will be one list, with multiple users inputing information at various different times. For instance, if someone wants certain materials to be ordered they will fill out the first few columns. The orderer will then be notified and place the order and fill out the next few columns, and then the receiver will do something similar.
You might want to do this as a Power App with a series of manually triggered flows to move things from one stage to the next instead of just an overall flow. Power Automate isn't very good at presenting a user interface for people to interact with. That's where Power Apps comes in. But Power Apps is much better at processing and approving things. So a combination of the two would be a good solution.
User | Count |
---|---|
89 | |
37 | |
26 | |
13 | |
13 |
User | Count |
---|---|
127 | |
54 | |
38 | |
24 | |
21 |