►
Description
In this 13-minute customer delivered - citizen developer focused demo, Theresa (Eller) Lubelski steps through a solution using Power Automate with SharePoint On-Prem List for secure Cross Bank Access Requests. Processes/Flows are defined in words and on an intake form. The creator then steps through how she accounts for missing information, changes in bank personnel, nested conditions, and more, after which the Flows are created and then methodically validated. This PnP Community demo is taken from the General Microsoft 365 Development Special Interest Group (SIG) - Bi-weekly sync call recorded on October 15, 2020.
Demo Presenter: Theresa (Eller) Lubelski (Iberabank) | @SharePointMadam
Supporting materials:
• Blog post - Flow when a SharePoint Column is updated | https://wonderlaura.com/2020/08/25/flow-when-a-sharepoint-column-is-updated/
Learn more:
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp-videos
A
My
name
is
teresa
lebowski.
I
am
the
sharepoint
team
lead
at
started
out
as
iberia
bank.
We
recently
merged
with
first
horizon,
and
so
then
there
are
applications
that
are
owned
by
each
bank
and
we
have
to
have
some
cross-bank
access,
so
we
have
some
pre-approved
applications
and
then
some
shared
drives
and
you
have
to
be
able
to
request
access
to
non-pre-approved
applications
as
well
as
laptops.
A
Actually
so
this
I
had
to
create
a
solution
for
the
cross
bank
access
request,
and
so
just
some
requirements
were
that
because
I'm
on
the
iberia
bank
side,
of
course,
I
wanted
to
put
it
in
our
sharepoint
and
we
couldn't
do
it
in
sharepoint
online
because
first
horizon,
only
a
limited
number
of
users
have
actual
m365
licenses,
and
so
also
because
I
had
to
use
sharepoint
because
of
that
I
had
to
use
sharepoint
on-prem.
I
happened
to
have
the
license
necessary
to
use
powerautomate
to
connect
to
on-prem
data.
A
So
this
is
also
exciting,
because
I
got
to
use
my
license
and
I
chose
power
automate
over
sharepoint
designer,
for
obvious
reasons
and
just
there's
a
link
in
here.
So
if
you
want
to
download
the
slides,
you
can
see
what
I'm
talking
about
with
those
licenses
and
so
then
we'll
get
straight
into
the
list
overview.
A
So
knowing
that
people
are
not
going
to
fill
out
the
list
correctly,
we
put
some
before
you
begin
information
like
just
on
the
page,
so
we
actually
created
a
page
had
the
before
you
begin,
then
we
had
the
instructions
and
then
we
had
the
actual
request
form,
and
so
some
of
what
we
had
to
do
was
like
title
fields
required
field,
but
we
weren't
really
using
it.
So
we
just
put
a
default
in
there
and
then
required
associates
requesting
information.
A
If
we
had
put
this
information,
which
is
the
description
as
the
description
for
associate
requiring
access,
it
went
at
the
bottom
and
they
didn't
like
that.
It
had
to
go
above.
So
I
had
to
create
a
field
and
just
put
a
default
value
and
description
so
that
it
would
be
above
then
we
had
to
have
fields
that
we
couldn't
hide
like
we
can
in
sharepoint
online.
A
So
I
had
to
put
a
stop
here
and
the
default
is
of
course
click
save
and
the
rest
are
I
use
only
which
actually,
that
seems
to
be
working
out
well
and
so
then
we
get
into
the
actual
flow
in
power
automate
and
I
decided
to
use
when
an
item
is
created
or
modified
thinking
that
hey
people
are
going
to
leave
out
missing
information,
so
they're
going
to
want
to
go
back
and
edit
their
form
and
then
save
it
again.
So
it
needs
to
run
through
the
flow
again.
A
So
this
got
me
kind
of
thinking
about
this
presentation
about
doing
pointing
out
some
of
the
differences
and
one
of
the
main
differences
actually
we'll
see
that
later.
But
you
can
see
that
there's
a
whole
bunch
of
things
that
you
know
we're
used
to
seeing
here.
We
also
saw
them
in
sharepoint
designer,
but
with
sharepoint
on-prem.
I
really
only
have
my
fields
that
are
text
values
and
then
because
I
there's
no
link
for
the
item
url
or
to
edit
the
item.
A
So
I've
made
variables
for
those-
and
you
can
see
here,
it
was
very
important
to
them
that
they
have
the
item
url,
that
they
could
click
the
link
and
go
straight
to
the
item
rather
than
going
to
the
just
the
list,
and
then
we
had
some
info.
You
know
when
we
like,
I
said
if
they
resubmit,
because
they
had
missing
information.
A
A
It
doesn't
need
to
go
through
everything
before
if
we're
just
going
to
end
up
terminating
and
so
you'll
notice.
I
did
name
everything
and
like
here
status
is
not
new
and
this
is
going
to
come
in
handy
at
the
end.
When
I
see
when
I
want
to
look
and
see
why
my
the
flow
was
cancelled,
you
might
be
wondering
why
I
didn't
use
get
changes
for
an
item
or
a
file.
This
did
not
exist
when
I
created
this.
If
you
want
more
information
about
this
action,
it's
it's
somewhat.
A
So
I
had
to
build
into
the
flow
how
to
check
for
those
and
what
to
do
if
there
those
were
missing
so
again.
If
it
something
is
missing,
then
it
emails,
the
requester
to
let
them
know,
and
then
that
email
has
the
link
using
that
variable
for
the
edit
item
and
then
it
terminates
because
there
are
missing
fields,
missing
information
and
I
didn't
know
how
many
nested
conditions
you
could
have.
A
This
is
like
an
overview
from
the
first
condition
in
the
main
part
of
the
flow
going
down.
So
you
can
see
that
I
actually
ended
up
with
four,
and
here
I'm
just
going
through
and
listing
all
of
the
different
conditions.
That's
not
really
anything
that
we
need
to
go
into
any
detail
about.
I
don't
think.
Hopefully
everyone
knows
what
a
condition
is
and
how
to
create
it.
A
A
There's
no
drop
downs
here,
whereas
if
you're
using
sharepoint
online
there
is-
and
the
other
thing
was
so
here-
that
kind
of
shows
you
that
just
shows
you
that
there
are
drop
downs
available
with
the
sharepoint
online.
Oh,
the
other
thing
was
that
it
created
an
infinite
loop.
So
I
had
to
take
out
the
update
item.
A
I
would
have
gone
back
and
tried
to
spend
more
time
figuring
out
how
to
not
create
an
infinite
loop,
but
they
were
anxious
to
get
this
going,
and
so
once
I
got
everything
running,
I
occasionally
will
go
into
the
flow
run
status
view
all
the
runs
see
what's
been
cancelled,
versus
failed
versus
succeeded.
Obviously
this
succeeded
ones.
I
don't
really.
B
A
Too
much
about
cancelled
it's
going
to
cancel
for
one
of
two
reasons:
either
there
was
required
information
missing
or
the
status
isn't
new,
and
that
could
be
where
someone's
gone
in
and
changed
the
status
from
new
to
in
progress.
Well,
that
will
actually
launch
the
workflow,
but
since
the
status
is
not
new,
it'll
cancel
pretty
quickly,
but
there's
also.
Sometimes
it
fails
when
I
had
to
add
a
fourth
email
address,
which
is
the
fourth
variable
to
the
email,
the
outgoing
email.
A
I
added
it,
but
the
system
didn't
automatically
put
a
semicolon
between
the
third
and
fourth
variables,
so
it
failed
because
it
ran
those
two
email
addresses
together
and
then
it
gives
me
pretty
good
information
in
this
message.
Letting
me
know
what
the
what
the
actual
error
was,
and
you
can
see
right
here.
It's
got
identity
management
and
then
com
immediately
follows
with
system
access.
So
I
looked
at
that
and
was
able
to
see.
Oh,
I
need
a
semicolon.
A
A
A
What
I
call
the
last
round
of
testing,
I
start
with
number
21
and
I
actually
got
down
to
number
100,
so
I
basically
ended
up
doing
80
tests
and
then
these
ended
up
all
being
the
same
as
something
I'd
already
tested.
So
that's
why
they're
not
green
the
gray
indicated
where
there
should
not
be
any
results,
and
I
think
the
yellow
was
something
that
I
ended
up
not
using,
but
I'm
just
letting
me
know
that
hey.
I
should
be
looking
for
results
here
yeah,
so
I.
A
B
That's
actually
a
good
good
suggestion
from
luis
for
power.
Automate
should
actually
give
this
kind
of
a
baseline
excel
file.
This
is
awesome
by
the
way,
teresa
just
an
example
on
how
you're
doing
testing
and
how
to
validate
that
the
workflow
is
moving,
because
that
wasn't
the
simple
workflow
so
really
making
sure
that
everything
is
moving,
because
this
one
was
used
by
your
company
for
business
processes
right.
So
it
really
is.
A
B
A
B
Yeah
yeah
absolutely,
but
getting
some
developer
involved
and
then
paying
for
that
one
would
cost
x
amount
of
money,
and
all
of
that,
so
that's
that's
kind
of
they're,
empowering
the
the
end
users
and
empowering
more
it's
and
and
let's
say,
power
users
like
you
teresa
on
on
being
successful
and-
and
that
is
absolutely
why
the
power
platform
is
so
cool
now,
so
normal
users
can
be
super
efficient
on
it
cool.
Thank
you
teresa
on
that.