Forum Discussion
How to create multiple “task” items using PowerApps
- Yes that is possible, but I sorry when you said multiple stores I thought you might be using multiple destination lists. The command you want in the forecast is patch.
The "big brother" of flow is Logic Apps, you can set Logic Apps to do something when a list item is created, and that thing would be to create list items in all the other lists.
The process could be:
1. Add a task to a sharepoint list using PowerApps.
2. LogicApps watches that list and starts when an item is created
3. LogicApps has a step for each other list to add a copy of this item
An alternative which would require PowerShell code would be to create a Automation Runbook to do the same steps as the logic app above using something like the SharePointSDK module. To kick this off SharePoint would need to activate a webhook in Azure Automation.
And a third option would involve the most code and that would be to create a C# function in Azure functions / app services to do the same sort of this, this however could be registered as a custom API in PowerApps and you can trigger that based on a click rather then on the creation of a item in a sharepoint list.
Sleep eludes me so here is what I am thinking. Using third party products and coding may be what I resort too, but I want to challenge what PA can do here.
Say I have 3 data connections to SharePoint:
1/ the task input list - used to create a task that will be distributed to stores
2/ a list of stores
3/ the task list (another custom list)
Now the process:
1/ In PowerApps an Input Task item is created and saved.
2/ A button runs a ForAll function for each item in the Store List. It creates a table (collection?) with the Store Number plus the field from the input task list.
3/ this populated table is displayed in a gallery control, which functions as a preview and where we can change a task or due date here and there if there are any exception stores.
4/ another button kicks off another ForAll that will create an item for each table row/record in the third data connection, which is the actual task list.
I could use PA for that third list to ensure the only field a store can edit is the Status field. Probably graphs/reports can be made in PA to track progress of completion and flow can send reminders.
Seems doable from what I see PA can do.
Thoughts?
- Yes that is possible, but I sorry when you said multiple stores I thought you might be using multiple destination lists. The command you want in the forecast is patch.