►
From YouTube: Microsoft Power Apps community call-November 2020
Description
This month's call covered some great community demos on topics including using Teams and Flow, creating components, advanced components, and Power Apps permissions. Todd and Chuck also shared news and community contributions.
Hosts: Charles Sterling, Todd Baginski
Speakers, Vivek Bavishi, Matthew Devaney, Dawid van Heerden, Daniel Christian
For more information, visit https://powerapps.microsoft.com
To attend the live, monthly community calls, download the series at
https://aka.ms/powerappscommunity call
Stay connected
Twitter https://twitter.com/microsoft365dev
YouTube https://aka.ms/M365DevYouTube
Blogs https://aka.ms/M365DevBlog
A
A
So
thanks
again
for
joining
us
today,
here's
all
the
folks
behind
the
scenes
who
bring
this
call
to
you
every
month
and
we'd
like
to
give
a
shout
out.
You
know
you
see
myself
todd
on
the
right
here.
That's
me,
todd
baginski.
I
co-host
this
call
with
chuck
sterling
charles.
How
are
you
today
I'm
doing
an
awesome
time,
awesome
and
so
chuck,
and
I
pulled
together
people
and
and
helped
make
this
call
happen,
but
we
couldn't
do
it
without
dana
andrew
heather
and
gabriel
behind
the
scenes.
A
A
So
thanks
again
to
all
you
who
do
that
every
month,
so
that's
going
to
bring
us
right
into
our
first
demo
of
the
day,
so
vivek
you've
got
a
little
demo
today,
showing
us
all
different
ways
to
integrate
teams
and
flow,
and
I'm
really
excited
to
see
how
you're
going
to
dial
this
in
so
without
further
ado,
I
am
going
to
let
you
take
the
screen
here
and
show
us
all
about
teams
and
flow
today.
Thanks
for
joining
us,
yeah.
B
B
B
You
should
be
able
to
find
it
from
your
teams
kind
of
this
three
dots
here,
search
for
power,
automate
or
flow,
and
you
should
be
able
to
get
that
app
and
once
you
get
it
just
right,
click
on
it
and
pin
it
so
that
you
can
use
it
as
much
as
you
want
and
it
stays
here
on
your
navigation
pane.
So
one
thing
that
I'm
going
to
try
to
do
today
is
I'm
not
going
to
go
to
the
browser
to
show
anything
about
a
flow
I'll
open
all
my
flows
right
from
here.
B
B
So
if
I
go
to
create
click
on
approval
on
the
categories,
you
have
more
different
categories
of
templates
here
and
then
I
have
a
start:
an
approval
for
new
documents
and
teams.
So
if
I
click
on
that,
it
gives
me
a
name
so
I'll
just
option
to
edit
the
name
so
I'll
just
say
demo,
and
it
has
all
the
connectors
already.
I've
created
the
connection,
so
I
don't
need
to
create
those.
I
can
just
click
on
continue
and,
as
you
can
see,
it
asks
me
all
these
things
right
over
here.
B
I
don't
have
to
open
the
floor
or
anything
I
I
just
choose
my
sharepoint
site,
the
library
name
which
I'll
choose
as
documents
I'll
just
keep
it
to
documents.
If
I
want
to
dig
into
a
folder
I
could
have,
but
I'm
not
going
to
do
that
here
and
then
I'll
just
choose
myself
here
to
assign
the
approval
to
so
once
I've
selected
these
three
or
four
inputs.
I
just
click
on,
create
flow
and
that's
it.
You
have
an
approval
flow
now
and
when
you
add
a
document
to
that
documents,
folder
it
will
run.
B
I
didn't
have
to
even
go
into
the
edit
mode
or
anything
it
just
runs
and
I'll
just
show
you
a
quick
example
here
yeah.
So
I've
been
doing
some
testing
here,
but
basically
this
is
the
one.
So
so
this
flow
ran
when
I
had
added
a
document
on
that
documents
folder.
So
if
I
want
to,
I
can
go
back
and
edit
it
in
advanced
mode,
but
otherwise
all
these
templates
that
you
see
here
that
are
around
50
optimized
templates
that
you
can
start
using
now.
B
B
Of
course,
if
you
need
to
add
some
more
custom
stuff,
you
can
always
go
into
the
advanced
editing
mode,
but
otherwise
you
need
to
create
something
simple.
It's
it's
super
easy
to
do
it
from
here.
So
going
ahead.
Let's
just
look
at
how
you
can
trigger
flows
from
so
this
is
one
way
I
mean
you
can
definitely
create
flows.
You
can
manage
flows
from
here,
but
what
are
the
other
ways
that
you
can
use
teams
and
power
automate
together?
B
B
B
Yeah,
that
was
one
of
the
input
fields
yep.
So
the
task
one
is
this
one
so
for
the
flow
getting
triggered
from
messages
here,
the
trigger
has
to
be
for
a
selected
message.
So
that's
that
is
this
one
on
that
you
have
an
option
to
edit
adapter
card.
So
this
is
really
cool.
You
can
click
on
an
edit
adapter
card
and
I
it
opens
up
the
adaptive
card
designer
for
me
and
if
you
have
not
used
this
yet
adaptive
cards,
I'll
definitely
recommend
you
to
check
this
out.
B
B
So
I
can
add
more
fields
here
I
can
edit
the
whole
adapter
card,
but
let
me
show
you
what
happens
next.
I
have
a
create
a
task
action
which
creates
an
outlook
task,
so
subject
is
from
that
adaptive
card.
So
it
gives
me
all
the
the
inputs
that
I
created
in
the
adaptive
card
to
use
in
the
subsequent
action.
So
I
can
see
all
those
things
here.
B
The
other
things
it
gives
me
is
the
link
to
message.
So
in
my
body
of
the
task,
I
have
added
a
link
to
message
which
will
basically,
if
I
click
on
that
task,
it
will
give
me
a
link
to
open
the
message
in
teams
so
that
I
have
a
reference
to
go
back
and
look
at
it.
I
can
also
include
the
message
content
itself.
B
Another
best
practice
would
be
to
add
another
adaptive
card
and
give
a
confirmation
to
the
user,
because
right
now,
when
I
create
submitted
it,
it
didn't
give
me
anything,
but
you
could
add
another
step
there
to
to
to
give
a
confirmation
to
the
user
that
the
adaptive
card
was
created.
So
I
know
I
have.
Maybe
how
am
I
doing
on
the
time
todd.
B
So
I'll
show
you
another
one.
Actually
I
wanted
to
so.
There
are
some
samples
in
here,
so
these
references
are
there
in
the
have
added
these
in
the
resources,
there
are
a
bunch
of
model
flows.
Adaptive
cards
for
like
candidate
feedback,
lead
collection,
all
those
kind
of
things.
So
you
can
use
these
as
well
in
your
flows.
If
you
wanted
to
either
start
from
a
message-
or
from
I
mean
you
could
have
any
trigger
here,
but
these
are
easy
to
use
adaptive
cards.
You
don't
have
to
create
the
whole
code
yourself.
B
B
B
So
every
time
a
new
account
is
added,
it
triggers
a
flow
to
find
the
lat
long
base
using
a
bingsmap
api.
If
the
confidence
is
low,
it
sends
me
a
notification
on
teams
like
this
one.
As
you
can
see,
it
shows
me
the
account
address
and
it
also
I've
added
an
option
to
to
show
the
google
map
kind
of
image
so
that
I
can
kind
of
confirm
if
the
location
is
right
or
not.
B
So
it
sends
in
a
notification
to
the
account
manager
on
that
account,
so
basically
the
owner
of
the
account,
and
they
can
confirm
that
okay
either
approve
it
or
reject
it.
They
can
also
open
the
account
in
crm.
So
it's
these
are
like
urls
to
open
the
account
in
the
model
driven
app.
So
this
is
another
use
case.
B
A
That
was
really
nice.
There's
a
lot
of
chat
about
actionable
cards
inside
of
there
in
the
chat.
I
expect
you
might
get
some
follow-up
questions
there
too.
I
think
it
opened
up
a
lot
of
eyes
on
how
you
can
extend
those
flows
and
using
those
cards
really
well
done,
thanks
again
for
showing
that
to
us.
Vivek
all
right
that
brings
up
next
is
matthew.
A
F
I'm
a
pretty
cool
cat,
daniel,
but
not
an
actual
cat,
so
yeah
so
yeah.
My
slides
will
be
in
my
powerapps
presentation
there,
but
just
a
little
bit
about
myself,
I'm
matthew,
devaney
and
you
know
recently
there
have
been
some
pretty
positive
changes
in
my
life
since
the
last
time
I've
been
on.
This
call
became
a
power-ups
mvp
in
biz
apps,
so
that
was
pretty
cool
got
this
awesome,
pretty
cool
power-ups
t-shirt
and
recently
I
started
a
brand
new
job
at
hitachi
solutions
as
a
power-ups,
developer
and
consultant.
F
F
Yeah,
so
I'm
going
to
put
the
slides
up
and
we
are
going
to
talk
about
components,
so
I
used
to
be
an
accountant
now,
a
developer
instead
of
asking
myself
each
and
every
day.
What
does
it
take
to
be
a
great
accountant,
I
ask
myself:
what
does
it
take
to
be
a
great
powerapps
developer
and
so
the
most
scarce
resource
in
any
job
is
time
right?
You
never
have
enough
time
to
do
anything,
so
you
have
to
learn
how
to
manage
your
time
effectively
and
be
pretty
efficient.
F
So
what
you
want
to
do
is
if
you've
gone
ahead
and
solved
the
problem.
You've
solved
the
problem
in
the
past.
You
want
to
remain
solved
in
the
future
and
hopefully
use
that
solution
again
and
again
and
again,
and
so
how
do
we
do
this
as
developers?
Well,
some
of
us
like
to
keep
a
onenote
on
the
side
with
you
know
a
few
code
snippets
to
kind
of
plug
in
here
there.
Some
of
us,
like
me,
have
a
huge
library
of
poc
apps
proof
of
concept
apps.
F
I
have
about
50
of
them,
which
you
can
just
kind
of
you
know,
take
code
out
of
in
any
given
time,
but
probably
the
best
way
to
go
about
this
is
to
build
components.
So
components
are
just
like
building
a
really
small
section
of
your
app
that
you
can
copy
and
paste
and
reuse
again
and
again
again
in
different
scenarios.
So
the
fastest
way
to
solve
a
problem
is
basically
just
to
do
what
you
did
in
the
past.
F
Here's
an
example
of
a
component.
I've
made
to
do
just
that,
so
in
pretty
much
every
app
that
I've
ever
made,
there's
been
some
type
of
approvals
process
to
it.
Vivik
just
actually
showed
us
an
approvals
process
too,
but
there's
no.
You
know
visualization
of
that
in
powerapps.
You
have
to
go
ahead
and
build
it
for
yourself,
and
you
know
to
do
that.
It
takes
about
you
know
two
or
three
hours,
two
hours
to
build
it,
one
to
kind
of
vet
it
out
and
perfect.
F
It
and
you
don't
want
to
do
that
again
and
again,
so
what
I've
done
is
I've
made
a
little
component
here
that
shows
you.
You
know
the
process
here
starts
with
a
guy
named
eric
erickson.
You
can
give
him
a
title
and
it
goes
on
to
sally
summers.
Think
of
this
as
an
approvals
process,
who's
a
supervisor
that
goes
to
me.
F
I
give
myself
the
title
of
manager
and
so
on
so
forth,
and
as
you
go
through
the
process,
you
can
get
a
little
check
or
a
little
x
to
show
if
something's
been
accepted
or
rejected,
and
the
current
person
in
the
process
has
a
little
orange
circle
around
them.
So
to
show
you
how
this
works,
I'm
just
going
to
go
to
the
next
screen
here.
F
So
this
is
an
it
requests
form
it's
nothing
more
than
a
you
know,
a
simple
form
of
powerapps
and
as
a
person
working
at
a
company,
you
can
go
ahead
and
request
a
desktop
pc
for
a
thousand
bucks
write
a
comment.
I
want
it
really
bad
and
when
I
click
the
submit
button
here,
you'll
see
that
I've
sent
it
forward
to
the
next
person.
Sarah
green
who's,
the
manager,
there's
a
little
check
box
here
and
now
I'm
acting
as
sarah
green.
Do
I
want
to
approve
or
reject
it?
F
I
click
approve
and,
as
david
johnson,
the
it
manager
I'm
going
to
reject
it
and
so
check
check
x,
so
that
would
have
taken
a
really
long
time
to
build
if
I'd
done
it
from
scratch,
but
just
implementing
a
component
it
took
about.
I
don't
know,
maybe
about
10-15
minutes,
to
get
this
functionality
in
there
and
for
those
who
want
to
download
this
component.
I
am
going
to
throw
a
little
link
in
the
chat.
That's
right,
you
guys
can
have
it
there
for
free
no
charge.
F
So
what
I'd
like
to
do
with
the
the
remaining
minutes
in
this
call
is
just
to
show
everybody
how
you
can
go
ahead
and
build
a
very
basic
component
for
yourself,
and
so
I
was
thinking
what
would
I
like
to
show
the
group
today?
What
should
we
do
here,
and
you
know,
one
of
the
things
I
really
feel
is
missing
from
powerapps
is
a
time
picker
component.
F
We
use
dates
all
the
time
and,
and
you
know,
time's
pretty
common
too.
We've
got
a
day
picker,
but
we
don't
got
a
time
picker,
so
how
this
particular
component
works
that
we're
going
to
build
today.
Is
you
know
you
click
on
this
little
text
input
right
here,
a
little
time.
Picker
shows
up,
you
can
go
up
down,
scroll
up
and
down
pick
a
particular
time
and
it
shows
up
in
the
text
box.
So
the
really
nice
thing
is
that
this
is
mobile
friendly
too
right.
F
F
F
So
all
I've
done
in
advance
for
this
presentation
was
I
clicked
on
this
little
new
component
button
to
put
a
new
component
that
started
on
the
screen,
and
then
I
made
a
label
inside
here
and
gave
it
a
nice
black
border
to
show
where
the
boundaries
of
our
component
are
so
I
just
thought
that
would
speed
things
up
a
little.
So
the
first
thing
we're
going
to
do
is
we're
going
to
put
the
hours
into
the
component
using
a
gallery.
F
F
The
next
thing
we
want
to
do
is
we
want
to
load
this
with
values
for
the
hours,
so
we're
going
to
write
a
little
sequence
function
here.
If
you
haven't
used
sequence
before
it's
awesome,
you
can
automatically
create
a
sequence
of
numbers,
just
programmatically
right
who
wants
to
type
out
1
through
12,
and
we
can
do
have
powerapps
do
that
for
us
and
we're
going
to
do
a
little
bit
of
formatting.
So
we
have
a
leading
zero.
F
Next,
we're
actually
going
to
show
this
inside
of
the
gallery.
Show
these
numbers
to
prove
that
the
sequence
function
worked,
so
I'll,
throw
a
label
in
there
and
hey.
What
do
you
know
it?
Pops
up
now,
we've
got
the
numbers,
one
through
twelve,
really
got
to
thank
the
powerapps
team
for
this
one,
like
I
absolutely
love
the
sequence
function
and
it
saved
me
so
much
time
so,
if
anyone's
on
the
call
who
helped
build
that
today.
Thank
you.
Thank
you.
Thank
you,
okay,
so
now
we
got
our
numbers
in
here.
F
So
let's
do
some
quick
styling.
If
we
want
this
to
be
reused
in
multiple
places,
we
ought
to
give
the
person
who's
putting
it
into
the
app.
You
know
a
way
to
control
that
right.
We
ought
to
give
them
properties
that
they
can
they
can
use.
So
we
can
build
their
own
custom
property
by
clicking
on
the
component
going
over
here
clicking
the
plus
button,
and
I
want
to
create
two
properties.
F
F
F
F
F
There
we
go
so
we've
got
the
basics
of
our
of
little
time.
Picker
right
here.
I
think
the
last
thing
I'm
going
to
do
is
hide
the
scroll
bar
because,
like
using
this
little
visual
design
principle
that
you
know
the
number
is
only
half
showing
the
user
is
going
to
be
able
to
know
they
should
scroll
up
and
down.
So
that
way
they
don't
have
to
think
about
using
the
scroll
bar.
F
F
F
Well,
I'm
going
to
pick
the
date
and
time
type
first,
and
I'm
just
going
to
call
it
value
right.
We
want
to
call
it
something:
the
user
is
used
to
and
they're
always
using
dot
value.
You
know
everywhere
in
powerapps,
for
this
section
I
want
to
set
the
time
when
the
user
clicks
on
something
right,
selects
a
new
value
and
yeah.
I
apologize,
but
I'm
going
to
copy
and
paste
some
code
in
here,
because
it's
a
little
bit
lengthy,
but
all
that
it
really
says.
F
Let's
just
make
sure
this
is
picking
stuff
up
gallery
time,
picker
hours
there
we
go,
because
I
had
that
funny,
looking
capital
I
so
all
it's
really
saying
here
is
put
the
time
in
a
variable
when
the
user
clicks
on
something
and
by
the
way
for
the
time,
so,
if
so,
with
the
so
what
we
do
here.
Finally,
is
we
had
that
value,
property
and
time
value
there
we
go.
We
had
a
variable,
there
called
veritime
value.
I
just
copied
it.
F
A
F
D
F
D
B
A
D
F
F
All
right
well
awesome!
Well,
hey
thanks
everybody
for
for
following
along
with
me
here.
I
just
want
to
say
yeah.
I
plan
to
put
this
time
picker
out
as
a
component
on
the
community
gallery
as
well
as
a
date
picker
as
well.
So
if
you
enjoy
it
just
make
sure
to
go.
Follow
me
on
twitter
and
sometime
next
week,
I'll
post.
It
thanks
for
helping
me
problem
solve
everybody
on
the
fly
and
thanks
for
having
me
once
again,
chuckadot.
A
Thanks
really
awesome
demo
there
I
love
how
you
coding
on
the
fly.
It
demonstrates
how
fast
you
really
can
build
up
a
component
awesome
thanks
again
for
showing
that
that's
going
to
lead
us
right
into
david's
demo
now
on
advanced
components,
so
we
are
coming
at
you
from
all
across
the
globe
today.
Now
we're
going
down
south
africa.
E
So,
just
as
it
is
about
time
for
a
time
picker
on
powerapps
a
couple
of
months
about
a
year
ago,
we
felt
that
it
was
really
time
for
a
model
dialogue
or
a
pop-up
or
whatever.
You
want
to
want
to
call
that.
So
we've
built
the
pop-up
component,
and
this
is
not
the
first
time
that
we've
had
it
on
the
show.
E
So
we've
we've
been
here
before,
but
today
we're
going
to
show
you
a
little
bit
more
about
how
it
works
in
the
back
end
and
to
show
you
how
to
how
to
typically
build
something
like
this.
So
for
those
of
you
who
haven't
seen
it,
you
can
go
and
grab
it
at
aka
dot.
Ms
forward
slash,
powerapps
dash,
pop-up
and
there's
a
whole
document
on
how
to
get
up
and
running
with
it,
and
it
explains
it
in
great
detail.
E
So
I'm
not
going
to
bore
you
with
those
those
installation
steps
today,
but
what
I'm
going
to
show?
You
is
just
on
a
very
high
level
what
it
is
that
it
what
it
does
and
typically,
if
you
don't
have
something
like
a
pop-up
component
every
time
you
want
to
have
interaction
with
the
user,
whether
it's
a
confirmation
or
just
a
simple
message
that
you
want
to
display
to
the
user.
You
typically
have
to
go
and
create
controls
on
the
screen.
You
have
to
group
them.
E
You
have
to
hide
them
based
on
certain
conditions
and
all
of
that
works
pretty
well
until
you
have
30
pop-ups
in
your
application
and
now
half
of
your
application
is
just
made
up
out
of
pop-up
components,
and
all
of
that
is
doable,
but
the
problem
is
at
the
end
of
the
project.
When
the
client
says
we
love
this
app,
but
can
you
change
something
in
the
pop-up?
So,
let's
change
a
color
for
an
example
which
means
you're
gonna
go
back
and
do
it
30
times
now.
E
I'm
just
way
too
lazy
for
that,
and
that's
that's
the
reason
for
this
pop-up
component.
So
what
it
is
that
I'm
on
about
is,
if
you
go,
and
have
a
look
at
this
app.
This
is
just
a
demo
app
that
displays
all
of
the
different
methods
that
you
can
interact
with
the
pop-up
and
you'll
see
that
this
is
version
15
draft
for
those
of
you
who
have
used
this.
The
latest
version
that's
published
is
version
14.,
so
this
one
includes
a
few
nicely
enhancements
which
I'll
show
to
you
enough
in
a
few
minutes
as
well.
E
First
of
all,
you'll,
if
you
click
on
the
ok
button
over
here,
it'll
just
give
you
a
very
basic
pop-up
it'll
tell
you
the
quick
brown
fox
jumps
over
the
lazy
dog
and
if
you
click
on
ok
you'll
see
that
it
actually
writes
that
feedback
back
into
the
application.
It's
very
important
to
understand
that
a
component
is
actually
outside
of
the
application,
so
you
have
to
manage
the
way
that
you
get
the
responses
back
into
it.
So,
similarly,
you
can
do
a
simple,
yes,
no
component,
so
this
is
good
for
confirmation.
E
So
are
you
sure
you
want
to
delete
this
record?
Yes,
no
and
the
same
you'll
see
that
it
writes
the
response
back
into
the
app.
Similarly,
you
can
have
a
yes,
no
cancel
and
in
this
app
we'd
also
do
pop-ups
with
a
little
bit
longer
messages
just
to
show,
and
we
also
use
this
to
test
the
pop-up
while
we
develop
on
it
so
text
input.
So
all
of
these
are
just
basic
pop-ups.
That
will
give
you
information.
E
The
next
ones
actually
require
you
to
gather
information
from
the
user,
so
they
will
see
a
text
input
and
they
it
says
we
are
looking
for
the
fox's
name.
So
let's
call
it
foxy
and
if
you
update
that
it
writes
it
back
into
the
app.
Similarly,
you
could
do
a
text
array,
so
you
can
actually
have
a
list
of
for
the
user
to
choose
from
so
they
can
go
and
choose
mickey
or
donald
and
then
click
on.
Ok,
you
could
also
do
office.
365
users
look
up
so
typically,
this
is
good
for
people
picker.
E
So
if
you
go
and
say
I'm
looking
for
myself,
if
you're
going
to
write
that
in
it'll
actually
stamp
that
data
back
into
the
into
the
app.
Similarly,
we
have
a
writing
control
a
slicer,
so
we
can
actually
get
some
slicing
going,
and
this
is
these
are
two
of
the
newer
inputs.
In
addition
to
the
family,
first
is
a
pen
input,
so
this
allows
you
to
just
write
on
the
the
screen.
E
E
And
we
can
attach
another
one
as
well,
so
let's
go
and
do
a
I
don't
know
an
excel
file
and
because
it
can't
preview,
the
file
it'll
just
give
you
an
excel
and
excel
icon.
So
this
is
my
file
and
then
it
allows
you
to
specify
categories,
and
all
of
these
you
can
pause
dynamically
to
the
pop-up
to
the
user.
And
if
you
click
on
ok,
it's
just
going
to
show
you
the
first
file
because
of
the
controller
we're
using
over
there.
E
But
this
is
the
the
functionality
that
we're
actually
busy
with
right
now
we're
busy
testing
it
making
sure
it
works
well
and
then
we'll
release
the
latest
version
to
the
community
all
right.
So
sorry,
there
is
one
thing:
more
is
the
the
load
spinner.
So
this
will
allow
you
to
just
call
a
load
spinner
from
with
anywhere
in
the
app
you
don't
have
to
every
time
go
and
create
those
controls
in
order
to
to
get
it
done.
So
if
you
go
and
set
a
variable,
you
can
get
the
load
spinner
going
right.
E
So
what
does
this
thing?
Look
like
in
the
background.
So
if
you're
going
to
look
at
all
of
these
buttons,
you'll
see
that
the
weather
we
call
them
we're
just
writing
a
basic
instruction
into
a
collection
and
then
the
component
reads
that
instruction
and
then
understands
what
it
is
that
you
expect
from
it.
E
So
you'll
see
it's
an
it's:
okay,
pop-up
there's
the
message
you
can
have
the
kind
of
icon
you
want
to
display,
as
well
as
the
icon,
color
and
then
also,
if
you
want
to
get
a
response
back
from
it,
you
can
go
and
give
it
a
a
logical
name
which
you
could
then
catch
with
a
toggle
in
which
and
and
then
actually
write
logic
to
go
and
fire
off
or
trigger
when
that
logical
name
is
received
back.
So
that's
for
a
normal
okay.
Let's
have
a
look
at
something
like
a
slider.
E
We
again
we're
just
passing
some
of
the
parameters
into
the
collection
and
this
time
we're
telling
it's
an
input
class
and
it's
a
slider
in
this
case
message
and
then
the
specific
configurations
relating
to
the
slider.
So
in
other
words,
what
is
the
default?
What
is
the
tool
tip
and
the
minimum
and
maximum
values,
and
that's
what
gives
you
the
functionality
now
what
happens
on
the
on
the
component
side?
E
If
I
go
into
the
component
screen
you'll
see
that
I'm
just
grouping
all
of
these
things
together,
so
the
real
good
stuff
is
is
in
the
component,
but
so
if
we
go
and
have
a
look
at
the
gallery,
you'll
see
that
the
gallery
is
simply
just
reading
the
first
item
in
that
collection.
This
is
a
flexible
height
gallery
and
and
that's
why
we
use
it.
It
makes
all
of
this
a
lot
easier.
E
So,
even
though
we're
only
showing
one
item
at
a
time,
it
still
makes
sense
to
you
to
use
the
the
gallery
for
that
and
then
inside
of
this
gallery,
we've
got
all
of
the
different
controls
and
you'll
see
that's
the
slider
as
an
example.
If
you're
going
to
click
on
the
slider,
you'll
see
that
that
now
reads
all
of
the
parameters
from
that
collection
and
then
it
knows
whether
it
should
be
visible.
E
What
size
it
should
be,
what
color
it
should
be,
and
and
so
on
and
so
forth,
and
then
this
entire
component
is
just
built
with
normal
canvas,
apps
components.
There's
no
development
done
here,
and
this
is
a
great
example
of
a
component
that
really
will
save
you
a
lot
of
time
instead
of
having
to
go
and
develop
this
every
time,
you're
looking
to
generate
a
pop-up
to
the
users.
E
C
E
Right
so
I've
posted
a
link
in
in
the
chat,
so
please
go
and
check
it
out,
there's
some
very
in-depth
instructions
on
how
to
get
up
and
running
with
it,
with
all
of
the
different
methods
that
you
can
use
in
order
to
call
it
there's
also
been
some
great
feedback
from
the
community
and
people
who
recommended
enhancements
to
it.
So
if
you
have
any
suggestions,
please
send
it
through
to
us
we'll
definitely
review
and
implement
that.
A
E
E
A
D
F
F
Okay,
so
the
the
problem
was
that
I
had
actually
set
this
value
here
to
an
input
property
and
so
the
reason
it
wasn't
finding
that
that
variable
when
we
went
ahead
and
clicked
these,
these
gallery
items
is
because
well
it's
an
input
property.
You
can't
find
something
inside
the
component
that
makes
absolutely
less
than
no
sense
right
chuck.
F
D
F
F
So
now,
if
I
go
back
to
my
screen
right
here-
and
I
were
to
add
this
custom
time,
picker
component,
you
know
I
could
then
build
another
text
box
and
link
to
it
using
the
value
property.
So
there
you
go
problem
solved
thanks
for
allowing
me
back
on
to
give
a
little
30
second
update
great
job
to
david
as
well.
Yeah.
D
A
A
C
C
C
These
gaps
of
permissions
need
to
be
filled
and
I
believe
all
those
gaps
are
going
to
be
filled
after
all
these
announcements
that
were
made
so
I
just
wanted.
I
don't
want
to
digress
too
much,
but
I
don't
want
to
call
that
out
all
right.
So
what
we're
going
to
talk
about
today
is
permissions
and
the
you
know
for
me,
people
call
me
as
unconsciously,
optimistic
I'm
also
the
kind
of
guy
who
says
security
first
performance
later.
That
is
all
true
about
me.
C
I
would
like
to
set
something
up
which
is
secure
right
from
the
get-go
and
then
after
that
I
don't
have
to
worry
about
it.
So
what
I'm
going
to
do
today
is
in
the
in
the
short
period
of
time,
I'm
actually
going
to
tell
you
how
I
can
handle
permissions
at
the
service
level,
which
is
the
power
platform
service,
powerapps
power
automate
at
the
environment
level
and
at
the
app
level
specifically
on
the
app,
is
inside
the
app
at
the
controls
and
at
the
app
outside
over
there
right.
C
So,
let's
jump
in
and
take
a
look
at
some
of
the
the
demos
I
already
have
for
you
now
here
is
an
app
and
it's
a
timesheet
app
one
of
the
ways
I've
set.
This
up
is
that
inside
the
app
normally
there
is
a
button
over
here
for
you
to
go
ahead
and
enter
your
timesheet,
but
I've
gone
ahead
in
that
control.
C
I've
set
up
some
functionalities
and
formulas
such
that,
if
you
are
a
person
working
which
this
is
your
start
time,
and
this
is
your
end
time
and
if
you
don't
show
up
at
that
time,
you
can't
open
up
this
app
and
put
in
a
you
know
your
your
start
time
and
your
end
time.
It's
actually
very
simple
how
I
was
able
to
accomplish
that.
So
let
me
just
show
you
what
was
some
of
the
tricks
to
it.
C
So
when
I
come
in
over
here,
normally
there
would
actually
be
a
button
and
then
that
button
over
here
it
would
actually
come
in,
and
would
you
know
this
button
would
say
this
is
your
start
time,
but
one
of
the
first
things
I've
done
is
right
at
the
app
loading
when
the
app
onstart
happens
over
here,
I've
got
a
simple
variables.
You
know
right
here
the
variables
which
is
go
ahead
and
get
me.
C
What
is
the
login
user
make
that
call
one
time
and
I've
already
got
the
login
users
over
there,
but
what
I'm
also
doing
is
the
user
who
has
logged
into
the
app
who's
using
the
app
I
am
going
and
taking
the
email,
which
is
a
very
unique
identifier
for
that
user.
I'm
grabbing
that
email
address
and
I'm
doing
a
check
against
a
list.
It
could
be
a
sharepoint
list,
it
could
be
a
cds
entity
oops.
I
said
entity
it's
cds
table
now.
It's
the
cds
table,
your
sql.
C
Whatever,
whatever
is
the
backend
you
have
over
there,
you
go
ahead
and
reference
it
over
there.
So
here's
what
I
did.
I
got
a
sharepoint
list
over
here,
quick
and
easy,
and
I've
got
a
list
running
which
is
basically
telling
me
the
employee
name
the
days
of
the
week
and
then
the
hours
of
the
start
and
end
time.
This
is
it.
This
is
my
table
in
the
back
end
over
here,
and
so
when
the
app
opens
up
again
on
the
app
on
start.
C
I
go
ahead
and
fetch
the
information
for
that
user
and
I
grab
the
data
over
there
now.
Based
on
that
date,
information
that
I
get
I've
gone
ahead
and
put
in
this
little
formula
to
say
that
hey,
if,
as
long
as
the
the
start
time
and
the
end
time
falls
between
like
an
hour
increment
because
you
got
to
be
practical
right,
somebody
may
actually
be
up
to
an
hour
late.
So
as
long
as
they
fall
into
that
hour
limitation
go
ahead
and
display
the
button
over
there.
C
But
if
that
hour
you
know,
time
span
has
has
elapsed,
then
go
ahead
and
hide
the
button.
So
it's
actually
a
very
simple
logic
to
go
ahead
and
put
in
this
visible
functionality
over
there,
and
you
know
running
it
against
over
there.
So
now
now
what
happens
is
well.
Obviously,
employees
change
their
routine
holiday
season
is
coming
up.
Whatever
very
simple:
you
don't
have
to
be
a
developer,
to
go,
make
any
changes.
The
everyday
manager
supervisor
can
come
over
here
and
say:
okay
yeah,
this
is
pretty
simple:
straightforward.
C
Daniel
is
going
to
be
working
overtime
during
the
holiday
season,
so
I
just
got
to
make
sure
that
he
is
yes
for
all
these
other
dates
as
well
and
he's
going
to
put
in
some
12-hour
shifts.
Let
me
go
ahead
and
change
that
from
8
to
17,
to
you
know
like
eight
to
what
is
eight,
whatever
you
know
the
12
hours
over
there
just
change
that
very
simple
place
to
go
ahead
and
do
that
stuff
over
here-
and
I
know
you
guys
who
are
on
this
call
are
finally
more
savvy
than
I
am.
C
You
might
even
find
a
way
to
just
take
this
data,
put
it
into
the
app
and
for
the
app
you
can
go
ahead
and
make
that
changes
over
there
kudos
to
you
guys,
that's
completely
possible
on
that
way
over
there.
So
I
want
to
switch
gears
now
because
we
talked
at
the
inside
of
the
app
level
right
at
the
control
level.
That's
the
first
level
of
permissions
that
we
can
handle.
Now,
let's
just
look
at
the
app
itself
now.
C
I
know
most
of
you
already
do
this,
but
I
still
want
to
talk
about
it
is
that
at
the
app
there's
several
ways
to
give
permissions
to
the
app
one
of
them
is,
I
can
actually
go
into
the
app
I
can
go
to
the
share
and
in
the
share
I
can
add
all
the
users
over
there
and
that
usually
works
great
from
a
small.
You
know
a
a
you
have
a
department
over
there.
You've
got
five
six
people
in
the
department.
That's
great!
You
go
ahead
and
put
that
in
you.
C
You
share
the
app
at
the
user
level,
it
all
works.
Obviously
you
need
to
make
sure
that
the
users
have
access
to
the
backend
database
over
there.
In
my
case,
I've
got
to
make
sure
that
the
users
also
have
access
to
the
the
sharepoint
list
over
there.
So
that's
you
know
one
of
the
backend
things
that
have
to
happen,
but
once
all
the
backend
databases
it's
taken
care
of,
you
can
go
ahead
and
actually
even
see
how
you
know
the
app
is
configured
goes
over
here
in
the
app
I've
used.
C
A
security
group
now,
first
tip
tip.
I
want
to
give
I'm
going
to
be
throwing
a
lot
of
tips
out
there.
I
personally,
when
I
set
up
a
security
group,
do
it
at
the
azure
80,
don't
go
and
do
it
at
the
microsoft
365
admin
over
there.
Azure
80
just
helps
to
do.
Take
look
at
a
lot
more
properties
over
here,
so
I
always
do
mine
at
the
azure
ada.
So
I
come
over
here
into
the
security
groups,
and
this
is
when
I
I
mean
I
go
into
the
azure
80.
C
I
go
into
the
groups
and
I
go
and
I
create
a
new
group.
I
go
ahead
and
create
a
security
group,
and
this
is
how
I
personally
do
my
naming
convention,
because
at
the
at
the
broader
entertain
tenant
level,
when
either
you
are
the
global
admin
or
you
are,
you
know
or
you're
putting
in
a
ticket
request
to
your
azure
team.
Tell
them
that
I'm
putting
in
the
request
for
powerapps,
but
you
are
the
one
responsible
for
putting
in
that
security
group
name.
C
So
when
it
comes
to
a8
app
say
it
is
an
app
and
this
is
why
I've
gone
ahead
and
done
that
I've
actually
gone
ahead
and
said
that
pa
for
powerapps
and
it
is
a
timesheet,
app
dash
sg.
Now
this
is
the
the
you
know,
the
syntax
I
use
you
can
put
the
sg
before
after
whatever
come
up
with
the
naming
convention.
That
makes
sense
to
you
and
that's
how
we
want
to
use
it
over.
C
There
see
I've
come
up
with
the
different
flavors
I've
done,
pa
I've
done
power,
apps,
whatever
works
for
you,
but
make
it
kind
of
very
user
friendly.
I
personally
use
the
kiss
technique
kisses.
Keep
it
simple
stupid!
That's
what
I
do.
It
just
works
for
me
now,
so
we
went
ahead
and
did
that
and
then
that
one
is
assigned
right
into
the
app
level
over
here
all
right
now,
let's
switch
gears
because
we
took
care
of
the
controls
inside
we
took
care
of
the
apps.
C
Now
I'm
going
to
go
and
take
it
to
the
next
level
is
at
the
environment
level.
So,
at
the
environment
level,
you've
got
to
be
the
power
platform
admin
over
there,
and
I
want
to
stop
and
talk
about
that,
because
many
people
think
that
they're
the
power
platform
admin
and
the
reason
they
think
that
is
because
they
say
well.
C
I
can
come
in
over
here
and
I
can
go
to
the
settings
gear
over
there
and
I
can
go
to
the
admin
center
and
I
am
the
power
platform
admin
remember
when
you
log
in
everybody
logs
in
as
the
maker.
But
if
you
are
not
the
admin
you're
not
going
to
see
a
lot
of
stuff
away,
you
might
only
see
access
to
your
things,
but
one
of
the
big
things
that
you
will
not
see
is
you
won't
see
the
default
one
over
there.
So
kind
of
keep
that
in
mind.
C
Make
sure
that
when
you're
starting
to
work
with
the
the
power
platform
and
sections
over
there
have
access
be
very
confident
that
you're
the
power
platform
admin
and
to
do
that
is
you
go
into
the
azure
80
you
go
and
look
at
the
security
roles
over
there
and
add
yourself
to
the
power
platform
admin.
I've
got
a
whole
bunch
of
videos
just
on
that
topic
all
right.
Coming
back
to
the
discussion
I
had
so
I'm
going
to
go
back
over
here
to
the
power
platform
admin.
C
My
app
was
in
this
environment
over
here,
so
I'm
going
to
click
on
that
and
now
at
the
environment
level,
I've
gone
ahead
and
added
a
security
group.
What
does
that
mean?
What
that
means
is
that
people
in
this
security
group
have
access,
have
access
not
only
to
the
environments,
but
those
are
the
people
who
can
be
also
the
makers
and
the
admins
to
that
environment.
C
Very
important
thing
for
you
to
know
that,
because
what
happens
is
many
times
if
you've
gone
ahead
and
created
an
environment
and
if
you
haven't
assigned
a
security
group,
then
everybody
has
access
to
that
environment.
Now
when
I
say
that
some
people
freak
out
about
it,
this
isn't.
What
do
you
mean?
Everybody
has
access
to
everything
in
the
environment?
No,
no!
No!
They
don't
have
access
to
everything.
C
What
they
do
is
they
have
access
to
get
into
the
environment
over
there
in
the
environment
level,
all
they
see
is
all
you've
given
them
access
to,
which
means
they
could
come
into
an
environment,
and
it
could
be
blank
or
they
would
just
see
those.
You
know
the
out
of
the
box
templates
apps
over
there,
but
they
would
not
be
able
to
see
your
app.
However,
they
have
the
door
to
walk
into
that
so
kind
of
keep
that
in
mind.
C
So
it's
a
very
important
feature
that
you
need
to
understand
is
that
users
don't
need
to
be
part
of
the
security
group.
Is
the
makers
and
the
admins
right,
so
we
covered
the
environment
level
now.
Finally,
let's
switch
over
and
look
at
the
entire
tenant
level.
Now
the
tenant
level,
I
can
go
back
into
the
azure
id
over
here
and
there's
a
couple
of
things
you
need
to
do.
Tenant
level
usually
boils
down
to
licenses
now
in
the
licenses.
C
There's
always
these
questions
that
come
up
to
me
is
that
daniel,
in
order
for
them
to
use
permissions,
and
things
like
that,
do
I
need
to
give
them.
You
know
this
level
of
access
like
if
they're
doing
any
e3s
or
you're
doing
e5s.
The
ball
boils
down
to
the
data
source.
What
are
the
connectors
that
you're,
using
and
based
on
that?
You
can
go
ahead
and
use
it.
C
There
is
something
called
as
self
service
sign
up
products
now
in
the
cell
service
final
products
by
default.
There
is
all
of
these
products
already
set
up
over
there.
Now,
if
you
have
a
scenario
where,
if
your
user
is
part
of
the
power
apps
and
now
that
you
just
want
to
make
sure
that
that
user
doesn't
have
a
part
of
any
of
the
power
apps
on
the
power
app
side
well,
actually
on
on
both
the
sites,
specifically
in
the
power
app
side.
C
Initially,
when
this
is
a
brand
new
user,
that
user
just
cannot
get
into
the
power
apps
if
no
license
is
assigned.
In
fact,
they
pop-up
comes
up
saying
you
can
go
and
have
a
trial,
and
if
you
subscribe
for
the
trial,
then
you
can
use
that
on
the
power
automate.
It
actually
automatically
assigns
to
you
a
trial
license
over
there.
If
you
want
to
completely
block
that
this
is
where
you
come
into
the
azure
80,
and
then
you
go
ahead
and
take
something
off
now,
a
very,
very
important
thing.
C
I
think
that
you
don't
listen
to
anything.
Listen
to
this
is
that
this
only
works
once
after
a
user
has
been
using
this
for
a
while,
and
you
go
take
this
off.
The
users
usually
still
have
access
to
at
least
the
default
environment,
even
if
you
take
all
of
these
off
now,
there's
other
ways
to
go
ahead
and
make
sure
that
you
know
even
block
that
one
of
them
is
just
disable
their
accounts
altogether.
The
employees
left
the
company,
but
this
is
basically
the
final
level
over
here.
C
Is
that
if
you
don't
want
users
to
have
self
service,
go
ahead
and
take
this
off,
but
if
a
user
has
been
using
it
for
a
while,
this
may
not
always
work
for
you
and
I'm
always
saying
it
may,
because
you
know
you
could
customize
your
permissions
at
that
level.
So
as
an
overview.
This
is
basically
all
that
we
accomplished
over
here.
We
went
ahead
and
talked
about
it
from
a
self-service
standpoint
right
at
the
service
level.
He
went
ahead
and
talked
about
it
at
the
environment
level,
at
the
environment
level.
C
I
was
said
that
you
know
you
all.
We
can
look
it
up
on
the
permissions
over
there
with
a
security
group
tied
to
the
environment
inside
the
environment.
I
had
an
app
on
the
app
itself.
I
use
the
security
group
and
then
even
inside
the
app
and
it
comes
to
controls.
I
can
use
it
based
on.
You
know
either
a
database
over
there,
which
whatever
is
the
database,
is
in
the
backend
or
you
could
even
use
securities
inside
the
app
over
there
and
I'm
going
to
leave
that
as
a
whole
separate
discussion
altogether.
C
A
Great
overview,
daniel,
that's
for
sure,
and
like
you
said,
that
is
a
total
overview
right
I
mean
when
you
really
start
digging
into
the
weeds
on
some
of
these
things,
there's
a
whole
lot
more
to
learn.
I
know
you
have
a
lot
of
videos
on
that.
I've
got
a
couple,
I'm
trying
to
think
who
else
does
I
think
reza
put
together
a
security
permission?
A
So
here
is
our
resources
slide
for
the
month.
I
know
that
more
links
have
been
hitting
chat.
People
been
putting
those
in
there
from
time
to
time.
If
you
guys
would
like
to
get
those
links
that
you've
been
sharing
in
the
chat
into
the
slide
deck
here
before
we
publish
it,
just
send
them
to
me
and
I'll
add
them
here.
So
these
are
the
links
related
to
what
vivek
showed
us
about
teams
and
powerapp
integration.
There,
real
quick
talking
about
the
recent
news
and
cool
things
that
have
happened
in
the
land
of
powerapps.
A
In
the
last
month,
obviously,
the
elephant
in
the
room
is
the
renaming
of
to
dataverse
for
teams
instead
of
project
oakdale
and
that
general
availability.
I
encourage
you
to
go,
read
all
about
that
ryan
cunningham
put
together
a
real
nice
blog
post
to
tell
you
all
that
this
next
one,
the
azure
api
management
connector.
This
is
a
really
big
game.
A
Changer,
in
my
opinion,
I
don't
know
if
you
all
work
a
lot
with
azure,
but
we
are
building
more
and
more
solutions
in
azure
every
day
and
with
the
api
management
connector,
you
can
now
write
your
own
apis
very
easily
in
azure
and
then
publish
them,
so
they
can
be
consumed
and
authenticated
with
out
of
the
box
connector
in
powerapps.
I
think
this
is
a
game
changer
in
making
it
easy
to
do
integrations
with
azure.
A
A
Editor
control
is
a
new
thing
that
you
can
now
use
in
a
model
driven
powerapp
and
I'm
sure
a
lot
of
people
are
really
happy
to
see
that
and
then
finally,
don't
forget
if
you've
got
anything
bookmarked
or
training
materials
or
whatever
the
case
may
be,
that
go
to
web.powerapps.com,
keep
in
mind
that's
going
away
and
that
article
will
tell
you
more
about
what
the
new
urls
are
and
what
they
will
be
used
for
chuck.
Did
you
have
anything
else
you'd
like
to
mention?
That's
no.
D
D
So
you
don't
have
to
go
out
and
do
that
crazy
math.
It
will
actually
go
out
and
adjust
all
of
your
controls
for
you,
I
put
that
post
in
the
iem
window
and
then
one
of
our
own
community
members,
jamie
willis
row,
is
actually
going
out
and
presenting
at
the
partner
conference,
and
I
actually
put
that
one
in
there
so
jamie.
Thank
you
for
actually
for
letting
us
know.
D
A
You
yeah
awesome,
shout
out
to
jamie
he's
here
every
single
month
and
always
interactive
in
the
chat
and
on
twitter
too.
No
doubt
very
good,
so
yeah
shout
out
to
the
community.
This
is
a
community
hashtag.
You
can
use
to
follow
everybody
who's,
doing
something
cool
on
powerapps
related
to
this
call.
So
thanks
to
all
these
folks
for
sharing
what
they
did
this
month,
if
you
check
it
out,
you
won't
be
disappointed
lots
of
neat
things
to
learn
there,
the
other
places
you
can
go
to
calls
very
similar
to
this.
A
The
first
one
is
the
power
attics
hangout.
This
happens
every
month.
Many
of
those
folks
who
run
that
caller
on
here
right
now.
I
know
vivek
himself
organizes
this
as
well,
so
you
can
get
more
information
about
powerapps
on
the
poweraddicts
hangout
and
you
can
also
learn
more
snacky
type
information
on
very
short
interviews
and
things,
maybe
kind
of
like
1
4
of
what
this
call
would
be
length.
A
Donna
and
sarah
have
a
less
code,
more
power
series
which
you
can
find
on
channel
9
and
on
youtube.
So
I
encourage
you
to
tune
in
for
that
too.
Finally,
we'd
like
to
say
thanks
to
everybody
who
came
to
share
their
time
here
today,
the
recording
will
soon
be
available
on
the
m365
developer,
youtube
in
its
entirety,
as
well
as
split
up
into
all
these
different
demos
you
saw
today.