Read our blogs, tips and tutorials
Try our exercises or test your skills
Watch our tutorial videos
Catch up on one of our webinars
Take a self-paced course
Read our recent newsletters
License our courseware
Book expert consultancy
Buy our publications
Get help in using our site
382 attributed reviews in the last 3 years
Refreshingly small course sizes
Outstandingly good courseware
Whizzy online classrooms
Wise Owl trainers 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
Search our website
We also send out useful tips in a monthly email newsletter ...
You can find other training resources for the subject of this exercise here:
You can also book hourly online consultancy for your time zone with one of our 7 expert trainers!
| Software ==> | Power Automate (29 exercises) |
| Topic ==> | Approvals (2 exercises) |
| Level ==> | Relatively easy |
| Subject ==> | Power Automate training |
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.
It's 2050. Your company is becoming increasingly autocratic, and you now have to request to do anything by adding an item to a SharePoint list:

The 3 requests submitted since the new system was introduced.
Start by creating a new SharePoint list from the Excel workbook in the above folder:

Choose these options to create a list based on the Excel workbook in the above folder.
Create a new flow called Exercise NN - handle requests to send out an approval request whenever someone adds a new task to your SharePoint list. Begin with the trigger:

Your flow will run when someone adds an item to the Requests list you've just created.
Add an approval request task:

See if you can create this without reference to the above diagram.
When someone approves or rejects a request this will create an array of comments (even though we know that only one person gets to approve or reject the request). To avoid this, initialise a variable to hold the only comment you know you will get:

By creating a variable after the approval task it avoids you having to reference the comments once in the approval path and once in the rejection one.
Set the value of this variable to something like this:

Take the first comment in the array (knowing full well that the array can only have a single value anyway).
Add actions to update your SharePoint list appropriately according to whether the action is approved or rejected (and to send an email to the idea's proposer letting them know if their suggestion has been accepted or rejected).

What will happen if the Outcome is Approve (left path) or not (right path).
. Here's what your list might look like after one approval and one rejection, for example:

Mia's idea was accepted, but Bob's wasn't.
If you've got this all working, give yourself a pat on the back!
You can find other training resources for the subject of this exercise here:
You can also book hourly online consultancy for your time zone with one of our 7 expert trainers!
Kingsmoor House
Railway Street
GLOSSOP
SK13 2AA
Elementa Workspace
6 Bevis Marks
LONDON
EC3A 7BA
c/o Holiday Inn
25 Aytoun Street
MANCHESTER
M1 3AE
© Wise Owl Business Solutions Ltd 2026. All Rights Reserved.