559 attributed reviews in the last 3 years
Refreshingly small course sizes
Outstandingly good courseware
Whizzy online classrooms
Wise Owls only (no freelancers)
Almost no cancellations
We have genuine integrity
We invoice after training
Review 30+ years of Wise Owl
View our top 100 clients
This exercise is provided to allow potential course delegates to choose the correct Wise Owl Microsoft training course, and may not be reproduced in whole or in part in any format without the prior written consent of Wise Owl.
The aim of this exercise is to create a flow allowing users to add items to a to-do list, reporting any problems which occur.
You may well find this exercise easier to do using the classic Power Automate flow designer. There seem to be several things to do with Scope actions which are harder to accomplish using the new designer.
Start by creating a new list in SharePoint based on an Excel table:
Choose this option, then choose to base your list on the Excel table called TodoList (it's the only one) in the above folder.
Choose to edit the Priority column:
First choose this option to edit the column .
Tell SharePoint that all your tasks must have different priorities:
Here we've also enforced a maximum value for the priority. For some reason SharePoint will still now let a flow add a task with priority higher than 5, but not one with a duplicate value of an existing priority.
Create a new Power Automate flow called Exercise NN - add to do item, and add these 3 inputs to the Manually trigger a flow trigger at the top of it:
Create three inputs: two string ones, plus an integer one for the priority.
Add an action to create an item in your SharePoint list:
Pass the input values as parameters to the Create item action.
Run your flow twice, with these input values:
The first run should work, but the second should show an error because there's already a task in the list with priority 7. Time to add some error-checking!
Add two Scope actions to your flow, rename them and drag the Create item action into the first scope to set up an error-handling template:
You don't have to set up error-handling like this, but it's good practice to.
Configure the Catch scope to run after the Try one has failed:
The Catch clause will run only if one of the actions in the Try clause fails.
Deep breath! Add actions to your Catch scope to get the results of the Try scope, filter these to show only ones with status Failed, then show the error details:
If you need help, the expressions are shown below - if you're feeling brave you could try doing this without help!
Here are the expressions for the Select action:
Add a task to turn this information into an HTML table, then send this information to yourself as an email:
You could always add CSS to tidy up this output ...
If you still have the time and energy, you could use the expression in the text file in the folder shown at the start of this exercise to add a link back to your flow!
Check that your flow works correctly when you type in a valid (ie unique) or invalid (ie duplicate) prioriity, then - with some relief - return to the Power Automate home page.
You can find other training resources for the subject of this exercise here:
25 Aytoun Street