In my model driven app there are numerous (and growing) occasions when the value of a choice field should trigger the creation of a/some task/s. The number of different kinds of tasks is also growing at a high rate. For example,
I have this pattern happening not only in the risk assessment form, but also in many other unrelated forms. The "beat it to death" solution is to build a new flow for every field that requires monitoring and trigger the flow when that field changes. But since all those flows would be creating Task objects with different field settings (Subject, Regarding, To, Description, etc.), this strikes me as inefficient and difficult to maintain.
What I'd like to do is create a Task Template table. The fields might be something like:
And then create one flow that monitored my entities according to the content of the Task Template table, triggering and creating Tasks as required.
Questions
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
User | Count |
---|---|
23 | |
5 | |
4 | |
4 | |
3 |
User | Count |
---|---|
26 | |
10 | |
9 | |
8 | |
7 |