►
From YouTube: SharePoint Framework Community call – 20th of May 2021
Description
SharePoint PnP Community - SPFx & JS SIG call on May 20. Demos: 1) Using Microsoft Graph Toolkit to easily access files in Sites and in OneDrive, 2) Building Microsoft Teams user bulk membership update tool with SPFx and Microsoft Graph, and 3) Building Microsoft Graph get client web part with latest Graph Client SDK. Latest PnP project releases – PnPjs Client-Side Libraries v2.5.0 GA and CLI for Microsoft 365 v3.10.0 preview released this month. Four new/updated PnP SPFx web part samples delivered in last 2 weeks. The host of this call is Patrick Rodgers (Microsoft) @mediocrebowler. Q&A takes place in chat throughout the call.
Learn more:
• See the full blog post for this call at: https://aka.ms/m365pnp/community/blog
• Download invite for bi-weekly SharePoint Framework call at: https://aka.ms/spdev-spfx-call
• 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
Hello
and
welcome
to
the
sharepoint
framework
and
javascript
special
interest
group
bi-weekly
sync
is
may
20th
2021.,
I
am
patrick
rogers.
We
have
another
great
call
for
you
today.
We'll
have
latest
updates
on
sharepoint
framework.
Our
patterns
and
practices
program
updates
new
community
samples,
our
optional
picture
time
with
together
mode,
and
we
got
three
great
demos
from
andre,
nick
and
sebastian,
covering
using
microsoft,
graph
toolkit
building,
microsoft,
teams,
bulk
membership
updates
and
then
building
microsoft.
A
Graphs,
get
client
web
parts
so
excited
to
see
all
of
that
moving
forward,
all
right
so
moving
right
into
it,
so
opportunities
participate.
We've
got
always
encourage
you
to
demo
your
code,
so
anything
around
client,
side,
development,
anything
around
the
patterns
and
practices,
program,
offerings
or
combination
of
any
of
those
things.
Love
love,
love
to
see
those
demos,
so
please
reach
out
to
myself
or
visa,
we'll
get
you
booked
on
an
upcoming
call.
A
Demos
are
my
favorite
part
of
these
calls
and
I
think
it's
wonderful
to
see
all
the
great
things
everybody
out
there.
The
community
is
doing
for
their
companies
and
customers.
Contributing
on
github,
of
course,
is
always
welcome
across
all
of
our
projects
and
the
contributing
takes
the
form
of
reporting
issues,
so
many
pull
requests
and,
of
course,
helping
with
issues
and
questions.
Finally,
I
always
appreciate
folks
providing
feedback
on
everything
we're
doing.
So.
How
are
the
calls
how's
your
documentation
updates?
Where
else
can
we
help?
A
But
of
course,
positive
feedback
is
okay
too,
if
you
really
really
like
something
we're
doing,
I
always
welcome
you
to
let
us
know,
and
perhaps
we
could
do
a
little
bit
more
of
that
in
the
future,
so
moving
right
along
to
our
giant
wallow
links.
So
we
have
access
to
all
of
our
developer
videos
community
videos
to
the
links
there
so
developer.
A
Videos
are
going
to
be
topic,
focused
videos
how
to
do
certain
things:
authentication,
microsoft,
graph,
spfx,
work,
various
other
topics,
everything
you
can
imagine
those
videos,
the
community
videos
are
going
to
be
recordings
of
all
of
the
various
community
calls.
So
this
call
the
monthly
community
call
the
other
sig
call
that's
on
the
opposing
thursdays
so
check
out
all
of
those.
A
If
you
miss
a
call
when
we
get
caught
up
as
well,
we
got
a
bunch
of
open
source
organizations
on
github,
sharepoint,
pnp
office,
dev
and
microsoft,
graph,
all
of
whom
have
great
resources
and
as
well
welcome
your
contributions
and
thoughts
to
all
of
those
places
so
encourage
you
to
check
out
any
of
all
of
those.
You
might
be
interested
in
tons
of
great
stuff
across
the
entire,
offering
there
and
as
well.
A
That's
a
lot
of
links
to
remember
so
you
can
always
just
remember
ak
dot.
Ms
m365
pnp.
That's
going
to
take
you
back
to
the
pnp
landing
page
which
is
going
to
get
you
details
on
the
entire
program
as
well
as
links
back
to
all
of
these
other
areas,
so
much
easier
to
find
ak
dot.
Ms
m365
pnp
and
next
up
is
the
extensibility
lookbook
gallery
so
encourage
you
to
check
this
out.
A
It's
really
interesting
use
of
kind
of
remote
provisioning
and
a
lot
of
other
capabilities,
but
giving
you
ideas
as
well
on
how
to
enhance
the
various
microsoft
365
surfaces,
so
teams
sharepoint
onedrive
office
and
the
power
automate
and
power
apps
the
power
family,
the
power
group
power
fam,
let's,
let's
say
that
and
ak
dot.
Ms
slash
m365,
slash
extensibility,
so
encourage
you
to
check.
A
B
With
david
thanks,
patrick
well
as
patrick
had
mentioned,
we
have
a
plethora
of
resources
and
opportunities
for
everyone
to
contribute
back
into
those
resources
and
make
them
better,
but
we
also
understand
that
the
road
to
that
path
might
be
a
little
confusing
a
little
intimidating
some
hurdles
along
the
way
like
what
is
github.
How
do
you
submit
a
pull
request?
How
do
you
get
more
involved?
So
sharing
is
caring,
is
here
to
provide
you
hands-on
guidance
through
a
series
of
session
topics
such
as
first-time
contributor,
first-time
presenter,
all
kinds
you
can
see.
B
The
spectrum
is
wide.
We
have
more
session
topics
coming
soon
on
spfx
sample
contributions,
cli
power
platform.
All
these
sessions
are
live,
they're,
hands-on,
we're
going
to
walk
you
through
together.
How
to
accomplish
any
and
all
of
these
tasks.
There's
safe
space
opportunities,
we're
not
recording
the
sessions
so
feel
free
to
ask
any
and
all
questions
you'd
like
and
they're,
absolutely
free,
great
way
to
get
involved
collaborate
with
more
in
the
community
and
start
working
with
everyone
all
across
the
globe,
so
invite
you
to
join
any
of
these
sessions
may
and
june
is
available.
B
A
Thanks
for
that
update
david
and
do
encourage
folks
to
check
these
out,
these
are
great
sessions,
great
way
to
learn
great
way
to
get
started.
A
lot
of
folks
have
come
out
of
these
and
done
their
first
pull,
requests
or
or
helped
out
in
other
ways
for
the
first
time,
and
that's
really
awesome
to
see
so,
if
you're
interested
in
getting
started,
I
encourage
you
to
check
those
out,
and
next
up
is
vasa
to
talk
through
the
modern
work.
Digital
brochure.
C
Yes,
so
the
microsoft
built
is
happening
next
week
on
25th
to
27th
and
basically
the
modern
world
digital
project
pressure.
I
can't
pronounce
that
properly
is
a
pdf
file
behind
of
the
https
akms
modern
work
build
sessions
which
basically
lists
all
of
the
relevant
keynotes
breakouts
on
demand
sessions,
roundtables
and
one-to-one
consultations
around
microsoft,
365.,
so
topics
related
on
craft
themes,
sharepoint
windows.
C
What
else
belongs
here?
Identity,
viva
top
aviva
connections?
Is
there
as
well
and
so
on.
The
interesting
thing
here
also
to
notice
is
that
we
have
round
tables,
so
we
have
multiple
ones
during
those
three
days
around
different
topics,
and
we
would
love
you
to
join
on
those
roundtables
to
give
us
feedback
on
what
you
need
around
the
different
products
as
there's
separate
ones
for
teams,
craft
viva,
con
viewer
connections,
even
our
community
one
has
a
roundtable
and
then
there's
one
to
one
consultation
option
which
is
pretty
cool
as
well.
C
So
if
you
are
building
something
you
can
actually
set
up
a
30-minute
call
with
some
of
the
product
group
representatives.
You
do
not
know
who
you
are.
You
are
kidding
but,
for
example,
some
of
those
are
falling
into
my
calendar.
So
who
knows?
We
will
maybe
have
a
one-to-one
consultation
next
week,
but
check
it
out
from
the
akms
address,
and
that's
really
really
cool
sort
of
content
for
next
week,
and
I
think
they
actually
would
go
to
the
spfx
next.
Aren't
we,
I
suppose
so?
Yes,
yes,
we
are.
C
It
might
easily
delay
until
july,
we'll
see
how
that
goes,
but
we're
looking
into
doing
a
public
preview
like
we
promised
that
we'll
start
doing
starting
from
1.12,
so
that
there
will
not
be
any
technical
surprises
related
on
this
releases
and
that
will
increase
the
quality
of
the
release
as
well.
In
general.
The
viva
connections
is
the
key
one
of
the
key
focus
areas
for
spfx.
C
We'll
talk
about
that
one
more
next
week
in
the
build
there's
going
to
be
a
quick,
quick
note
in
jeff
deeper's
keynote
on
that
one
we're
going
to
talk
about
it
in
spf
session
and
so
on,
and
then
of
course,
microsoft
teams
is
a
big
focus
area,
but
then
at
the
same
time,
not
forgetting
about
the
extensions
and
portals
which
is
where
the
spfx
is
currently
being
widely
used.
So,
of
course,
we'll
keep
on
investing
there
and
next
week
we're
going
to
say
openly
in
the
sessions
as
well.
C
Teaser
are
we
gonna,
show
live
well,
some
live
code
and
some
live
capabilities
next
week
in
built,
but
we
will
actually
talk
about
upcoming
preview
around
the
vivo
connections.
Experiences
of
your
connection,
especially
the
mobile
side
of
viva
connections.
In
build
and
starting,
like
I
said,
it's
going
to
be
a
public
preview
starting
from
build
next
week
and
you
can
sign
up
for
that
preview
and
you
will
get
access
on
early
bits
to
that
mobile
experiences
and
you
can
start
building
stuff.
D
D
Okay,
we
have
dancing
bunnies
now
that's
excellent
and
there
was
lots
of
docs
fixes
from
a
lot
of
different
people.
So
back
to
the
sharing
is
caring.
I
want
to
just
point
out
that
that
is
an
excellent
way
to
assist
is
by
updating
docs
when
you're.
If
you
happen
to
use
the
pnpjs
library,
don't
feel
like
you
can
contribute
to
the
library
itself,
but
could
contribute
samples
or
update
docs
in
some
way
to
help
make
it
easier
for
the
next
person
that
comes
along.
We
would
highly
encourage
that.
D
So
I
just
wanted
to
to
point
out
that
these
docs
updates
that
we
get
are
really
helpful
and
useful,
and
you
should
definitely
feel
open
to
trying
to
submit
some
of
those
if
you
have
them
also
want
to
just
reiterate
that
v3
development
is
underway.
We
have
that
pinned
issue
1636
that
it
gives
an
overview
of
our
v3
plans.
D
There
is
also
a
v3
branch,
that's
available.
It
has
some
working
code
in
it,
but
it
is
a
work
in
progress.
So
it's
not
something
that
you
can
even
use
in
a
beta
state
yet,
but
we
will
be
announcing
more
as
we
get
further
along
in
that.
Just
to
reiterate
also,
we
do
have
a
new
github
action
that
is
locking
closed
issues.
We
do
encourage
you
if
you
have
an
issue,
that's
related
to
one
that
you
found.
D
That
is
closed,
that
you
open
a
new
issue
and
reference
using
the
pound
sign
and
the
number
of
the
issue
that
is
related
to
yours
and
then
fill
out
our
issue
template
as
completely
as
possible.
So
we
can
help
you
as
quickly
as
possible
and
then,
as
always,
follow
us
on
m365
pmpjs
on
twitter.
Back
to
you,
patrick.
A
So
these
are
scripts,
are
sort
of
multiple
commands,
obviously
put
together,
but
you've
got
a
bunch
of
sample
scripts
so
showing
you
how
to
orchestrate
these
so
replacing
sharepoint
site
collection,
admin,
adding
multiple
folders
and
libraries
with
this
from
a
csv
file
and
monitoring
site
collection,
storage,
usage.
So
those
are
great
sample
scripts.
You
can
take
and
adapt
to
your
needs
as
well.
You
can
always
install
the
latest
preview
from
npm
install
dash
g
at
p,
p,
cli,
dash
microsoft
65
at
next,
and
the
ak
dot.
A
Msl
cli-m365
for
all
your
documentation
and
update,
needs
be
sure
to
check
out
the
cli
great
tool
for
managing
your
deployments
and
managing
your
dev
experiences.
Next
up
are
the
reusable
controls.
We
have
two
sets
of
controls.
There's
the
react
controls
the
2.x
branch
or
version
set
is
for
spfx
1.11
and
below,
and
then
the
3.x
branch
is
for
spfx
1.12
and
likely
above
so
team,
picker
team,
channel
picker
by
team
site,
picker
drag
and
drop
files.
Various
fixes
enhancements
all
new
stuff,
all
great
stuff.
A
You
can
see
the
latest
version
numbers
up
there,
2.7
and
3.1
those
are
available.
Now
those
are
the
react
controls
which
are
designed
to
be
used
in
the
body
of
your
web
parts
or
application
customizers,
and
then
you've
got
the
react.
Property
controls
which
are
designed
to
be
used
in
the
edit
pane
of
your
sharepoint
framework
web
parts
and
those
versions
are
2.6
and
3.1
and
then
that
those
releases
are
various
fixes,
just
some
small
updates
to
those
and
again
I
want
to
thank
everybody
who's
helping
out
here
with
the
controls.
A
A
lot
of
great
contributions
going
on
in
the
control
space.
Next
up
is
p
p,
modern
search,
ak,
dot,
m,
slash,
p,
p,
dash
search
for
all
of
the
related
all
the
latest
updates
there.
This
is
a
set
of
web
parts
designed
to
allow
you
to
build
a
search
experience
for
your
users,
so
think
of
the
sort
of
search
portal
idea.
So
you
can
compose
these
web
parts
together
and
create
a
great
looking
and
great
usage
for
your
search.
A
Experiences
for
your
users,
the
newest
stuff,
4.1
or
4.x
branch
4.1
being
released
on
march
20th
is
the
active
branch
that's
being
worked
on
and
lots
of
great
releases
there.
So,
if
you're
still
on
the
3.x
branch,
it
would
encourage
you
to
upgrade
as
time
per
upgrade
as
time
permits
and
the
april
release
was
skipped
due
to
resourcing
aiming
for
a
may
update
there.
So
again,
pnp
modern
search
is
a
great
place
if
you're
looking
for
somewhere
to
contribute
and
want
to
help
out.
E
Awesome,
thank
you.
So,
if
you're,
the
kind
of
person
who
learns
better
by
example,
then,
instead
of
reading
extensive
documentation,
you'll,
probably
like
dspfx
webparts
samples
and
the
spfx
extension
sample
repositories,
there's
hundreds
of
curated
spfx
samples
built
by
the
community,
and
they
should
be
the
first
place
to
look
when
you
get
started
with
a
new
spfx
development
task.
These
are
the
updates
for
the
last
two
weeks.
E
So,
on
the
spfx
extension
side,
we
have
nothing
new
yet,
but
on
the
spfx
web
part,
we
have
a
new
web
part
from
joao
mendes,
which
is
a
2019
version
of
his
awesome
list.
Item
menu,
which
we
demoed
earlier
on
a
previous
call,
and
we
have
a
new
news
banner
by
joao,
because
joao
apparently
feels
that
doing
one
sample
every
two
weeks
is
not
enough,
so
he
does
too
now.
E
So
this
new
web
part
actually
shows
information
news
information
as
a
banner
and
the
information
comes
from
a
list
and
it
works
on
sharepoint
2019
in
sharepoint
online.
The
good
old
list
form
web
part
continues
to
evolve.
There
was
an
issue
that,
when
we
submitted
the
attachments
on
a
form
were
not
cleared
so
arigunawan
updated
that
for
us,
thank
you
and
we
have
an
update
to
the
calendar.
E
Elie
shea
updated
the
the
web
part
to
use
the
local
storage
for
caching,
so
we're
not
calling
the
api
as
often
as
possible
and
there's
a
new
issue
template
which,
which
you
can
see
now
on
on
top
of
the
screen.
We
we
use
a
new
feature,
that's
available
in
github.
That
allows
us
to
actually
create
forms
for
te
for
issues
and
soon
for
pull
requests
and
we're
doing
this,
not
because
we
want
to
make
it
more
difficult
for
you
to
submit
issues.
E
We
absolutely
welcome
issues,
but
what
we
found
is
the
majority
of
the
time
that
we
spent
with
issues
was
going
back
and
forth
saying
what
version
of
the
form
are
you
using
what
version
of
spfx
you
know?
What's
on
your
which
operating
system
are
you
using
and
then
the
actual
fixing
of
the
issue
was
was
like
a
20
of
the
total
effort
so
by
asking
people
to
make
sure
that
they
fill
in
the
information
we
need,
including
who's?
The
author?
E
What's
the
sample,
you
know,
what's
your
version
of
spfx
and
so
on,
we'll
make
sure
that
we
can
respond
to
you
a
lot
quickly
and
we've
got
automated
processes
now
that
will
automatically
close
the
issue.
If
you
don't
bother
with
filling
the
information
again,
it's
just
to
make
sure
that
we're
delivering
you.
You
know
the
help
that
you
deserve
in
the
time
as
fast
as
possible.
A
C
This
absolutely
let
me
share
my
screen
and
put
the
screen
again
on
the
right
location.
So,
let's
see
if
we
can
actually
how
do
we
do
this,
so
I'm
sharing
that
and
then
we'll
do
this
and
I'm
already
recording.
Let's
wait
for
the
full
50
seats,
filling
up
situation,
I'm
not
going
to
enable
my
video,
because
I
think
oh
bob-
you
have
a
nice
hat,
so
yes
wow,
so
nothing
against
wearing
hats.
C
Hats
are
cool,
so
I
think
we're
filling
up
with
50,
oh
still
april,
on
the
middle
yeah
yeah
leading
the
back
really
good,
there's
allison!
Is
it
yeah
yeah
see
recognizing
excellent
awesome.
Let's
do
some
hand,
saving
everybody
thanks,
everybody
for
joining,
it
is
like
said
so
many
times.
It's
awesome
to
see
the
real
faces
behind
of
the
names,
hopefully
by
end
of
this
year,
we'll
get
to
see
some
of
your
face-to-face
and
some
conferences
thanks
everybody
we'll
crack
animation
out
of
that
and
cool.
F
First
of
all,
thank
you
for
framing
for
the
investigation
to
make
this
presentation
itself.
So
my
name
is
andre
lash.
I
work
in
switzerland
for
a
company
called
data
links
and
I
create
one
sample
that
that
is
called
onedrive
finder.
That's
used
to
microsoft,
graph
toolkit
to
retrieve
the
information.
When
I
pick
it
was
on
a
better
version,
but
the
last
hours
have
been
some
developments
itself
so
before
I
just
want
to
give
a
small
context.
F
Then
I
went
to
the
samples
into
the
web
parts
samples
to
the
second
community,
and
I
wanted
to
create
the
first
web
part
and
I
thought
in
internet
on
twitter
sharing
that
there
is
a
new
mic,
there's
a
microsoft
graph
to
keep
control
that
is
called
file
list
that
that
was
a
better
version.
I
say:
okay,
it's
you!
I'm
going
to
pick
and
based
on
that,
I
picked
this
better
version
of
the
of
the
microsoft
graph
toolkit
that
is,
that
is
they
have
two
different
components
that
is
called
the
microsoft
file.
F
This
and
microsoft
file.
Both
they
are
working
together
itself
and
for
this
I
create
this
sample.
Where
I
make
a
multiple
graph
queries
regarding
one
drive
and
site,
and
these
these
two
controls
they
are,
they
go
to
using
the
graph
they
accept
to
the
content
from
from
one
drive
and
also
the
onedrive
shared
drives.
That
means
one
drive
on
the
sides
and
I'm
able
to
display
it
using
the
the
microsoft
graph
toolkit
itself.
F
The
example
has
a
graph
queries,
breadcrumbs
search
on
drives
page
size
x,
filter
on
file
extension
team
for
qualification
in
cash
too
many
things
I
will
try
to
resume
it
as
soon
as
possible,
so
visualization.
What
is
what
I
want
to
represent
is
I
have
four
separate
queries
that
I
make
it
to
the
call.
So
the
first
thing
is
to
call
the
host
name
and
based
on
that
host
name.
It
will
need
the
site
where
there
are
drives
and
there
with
the
site
id
of
the
drive.
I
try
to
know.
F
Where
is
the
root
side
of
the
onedrive
or
the
site
that
I
want
to
visualize
and
it
will
display
the
the
files
and
the
folders
that
I
want
to
visualize
here.
I
have
the
control
the
tool
the
microsoft
toolkit
basically
make
questions
to
graph.
Where
are
you?
Where
is
this
information?
What
is
your
face
id
and
it
might
be
the
demo
itself,
so
I'm
just
going
to
jump.
I
create
a
viva
connection
with
a
graph
here
and
then
I
make
a
preloading
of
all
my
sites
that
I'm
collecting
to
save
the
id
itself.
F
F
I
can
also
include
some
folder
filtering
itself
and
at
any
moment,
another
option
that
I
described
is
the
ability
to
make
a
navigation
between
the
the
folders.
I
can
go
back
and
go
fast,
as
you
can
see
after
the
clicking
the
first
time,
everything
is
loaded
on
cache
and
this
will
become
faster
than
the
next
time.
I
click
it.
So
there
is
a
you
can
we
can
make
a
simulation
of
the
darkness
that
we
can
visualize
at
any
moment.
F
F
We
have
a
default
one,
a
dark
one
and
I'm
going
to
use
the
another
option
and
I'm
going
to
click
include
my
custom
script
and
one
thing
that
you
can
see
here
and
if
I
just
also
change,
I
changed.
The
localization
of
the
files
here
was
modify
and
here
is
a
load
more
and
I
changed
the
localization
to
have
the
different
customization.
F
If
I
return
back,
I
have
the
default
capability
search
at
any
moment,
I'm
able
to
make
some
typos,
like
I'm
able
to
make
some
search
drives
using
the
current
operators
itself,
and
this
will
give
me
the
the
naming
of
the
files
on
that
specific
drive.
If
I
click
on
the
file,
I'm
able
to
see-
and
as
you
can
see,
the
team
is
also
aggregated
directly
from
there
and
it
can
always
return
back
and
all
this
is
basically
the
main
operation.
I
have
one
last
demo,
but
I
will
call
it
tc3
lighted
with
with
cache.
F
F
There
is
a
new
version
where
I
already
included
these
two
new
controls,
the
file
list
and
the
file,
if
you
want
to
start
to
dig
in
and
to
make
some
investigation
and
work,
and
because
I'm
going
also
to
update
my
control
on
the
web
part
samples
I'm
going
to
update
already
with
the
new
version
that
is
already
there
and
with
all
these
features
that
I'm
describing
itself
so
how
fast.
So,
how
is
this
this
made?
F
I
know
that
in
the
context
that
will
be
loaded
by
the
sharepoint
provider
as
a
previous
work,
I
have
a
connector
where
I
make
the
the
calls
to
the
to
the
host
name
plus
the
site,
where
else
that
I'm
going
to
use
it
for
the
filtering
of
my
quantity
itself,
so
how
to
retrieve
the
site
id.
The
first
thing
I
did.
I
just
retrieved
the
host
name,
the
host
name
and
then,
depending
on
the
host
name.
F
I
make
it
a
normal
search
on
the
using
the
site,
the
site
graph,
and
I
use
the
operator
search
to
retrieve
me
all
the
all
the
sites
that
I
want
to
use
it
for
my
drive
and
then
I
pick
the
id.
The
id
will
be
the
site
id
that
I'll
use
it
for
the
filtering
of
the
content
for
the
site
or
for
the
onedrive
itself.
F
So
this
information
is
stored
will
be
listed
here
and
then
we
go
for
the
second
step.
So
the
moment
we
need
we
loaded
this
content,
we're
also
going
to
load.
Also,
we
will
need
also
the
id
to
identify
where
what
is
the
information
that
we
want
to
display?
Normally
the
steps
that
I
do
is
I
pick
the
site
and
I
list
all
the
content
from
the
root
folder
itself.
Here
are
a
bunch
of
other
queries
that
can
be.
F
They
are
supported
with
the
file
list
and
also
with
the
file
itself
and
also
some
attributes
that
I
use
it.
For
this
example.
I
use
three
multiple
ones
because
the
ones
regarding
the
one
drive
I
use
the
site
id
and
emit
for
the
breadcrumb
and
also
to
display
the
content
from
from
the
from
the
drive
and
the
file
list.
F
Query
for
the
search
capability
that
I
showed
before
all
these
information
are
also
shared,
and
there
was
also
included
today-
and
you
can
also
give
access
to
to
these
links
and
create
on
the
microsoft
documents
where
they
can
explain
better
and
have
a
way
more
detail
than
me.
Let's
say
like
this:
okay,
I
have
my
id,
but
now
I
need
to
get
the
the
root
id,
and
this
is
the
only
queries,
filter,
queries
or
string
queries
that
I
make
all
the
other
ones
that
will
be
managed
by
microsoft,
graph
toolkit.
F
So
I
using
the
graph
component,
I
retrieve
the
root
id
where
he
treats
me
or
gives
me
the
id.
So
I
have
the
site
id
and
item
id,
and
this
will
give
me
the
first
layer
of
documents
itself
and
now,
how
can
I
go
deeper
on
the
breadcrumb
itself,
if
you
click
there's
an
event
that
is
called
item?
Click,
if
you
click
on
the
event,
he'll
give
you
some
key
information
that
you
can
reuse
it.
F
Where
are
you
where
you
want
to
have
it,
for
example,
the
document
information
or
we
wanted
to
have
it
as
a
breadcrumb
and
then
when
we
are
creating
the
breakthrough,
since
we
have
the
site
id,
we
create
the
position
where
we
were,
because
the
file
list
control
will
retrieve
all
the
children
where
are
located
so
every
time.
I,
if
I
click
in
the
folder,
he
goes
to
the
next
one,
and
I
save
this
mit,
and
this
will
do
this
will
be
used
if
we
need
to
go
back
and
forth
based
on
the
different
locations.
F
F
Second,
one
is
the
the
search
capabilities.
What
I
have
done
exactly
the
same
process,
I
type
in
a
text
box
what
I
want
to
search.
I
build
the
query
based
on
if
it
is
on
the
on
the
site
id
or
on
the
onedrive
site,
and
then
I
make
I
use
the
operator
search
to
retrieve
the
information
I
want.
I
load
it
on
the
property
and
the
output
will
display
it
correctly.
So
I
look
for
sharepoint
2013
and
the
document
will
appear
correctly
like
this.
F
Next
next
option
is
the
ability
to
make
the
the
file
extensions
filtering
the
same
concept.
We
have
an
array
of
extensions,
I
select
multiple
ones
and
he
will
make
the
filtering
based
on
do
on
that
information.
The
same
I
use
it
for
the
page
size.
The
effect
check
the
number
that
you
expect
and
this
will
go
by
batch,
the
amount
of
content
that
is
needed
so
for
the
teaming.
There
is
also
these
different
capabilities,
so
we
have
the
default.
F
We
have
the
dark
and
you
can
create
your
custom,
look
and
feel
where
you
can
have
so
you're
rounded.
You
have
some
backgrounds
and
some
other
colors
that
you
can
customize
it
itself
now
at
least
cash.
What,
while
I
say
it
is
extremely
important.
We
are
using
documents
and
we
and
this
can
be
easily
and
very
instantly
used
and
accessible.
So
it's
very
critical
that
we
need
to
use
very
clearly
the
the
cache
itself.
So
what
that
means?
We
have
the
the
files
and
the
file
names
correctly.
F
So
we
are
these
two
options,
or
there
are
multiple
options
of
managing
this
type
of
caching.
We
can
deactivate
or
deactivate
the
caching,
because
imagine
we
have
a
vr
visualization
some
files
and
they
are
some
renaming
of
the
files
they're
based
on
the.
There
are
some
flaws
on
the
background
that
renames
the
file.
If
the
cache
is
activated,
this
can
create
some
issues
itself.
F
So
this
is
something
that
is
very
important
that
you
define
when,
before
you
start
to
create
this
solution
itself
two
days
ago
was
also
introduced
a
new
feature,
and
it
is
one
that
could
also
be
solved
a
lot
of
the
also
this
feature
of
the
caching
itself,
that,
after
talking
with
the
with
the
teams
and
also
present
my
caterer,
they
were
they
actually
they.
They
also
use
it
for
other
controls.
F
They
allow
that
they
have
in
react,
will
use
it
and
also
there
was
created
a
new
method
that
is
called
reload
and
the
reload
will
have
a
parameter
true
or
false
if
it
is
true,
he'll,
clear,
the
cache
and
he'll
not
go
into
the
cache
and
he'll
not
get
us,
for
example,
information.
Incorrect
information
from
the
file
names
because
could
have
some
type
of
information.
Here
I
have
a
very
simple
example:
I
called
the
f
I
used
to
have
on
the
file
list
and
then,
when
we
reload
the
control,
we
have
it
refreshed.
F
A
very
simple
example.
I
have,
for
example,
on
my
root
side.
I
have
this
example,
and
I
go
here
I'll
rename
it.
I
will
keep
it
one
and-
and
I
will
I'm
going
to
delete
the
this
example
if
I
want
to
site-
or
if
I
change
it,
for
example,
to
another
one,
and
I
try
to
go
to
the
home,
and
I
will
give
it
in
other
words,
so
nothing
happened
here.
What
so?
What
should
be
the
next
step?
We
create
this
event
that
was
talking
and
basically
what
he
does.
F
He
will
going
to
refresh
this
content
here,
plus
is
going
to
freeze,
he's
going
to
release
the
cache
to
have
it
a
clean
content,
and
now
we
have
the
example,
one
plus
we
don't
have
the
other
file
itself.
That's
why
it's
very
important
if
you
are,
if
you
are
working
in
the
environment,
that
there's
a
lot
of
flaws
and
renaming
this
is
critical
itself.
F
Next
one
is
so
the
next
one
is
just
the
the
amount
of
feature
that
was
that
was
created,
and
I
was
not
able
to
use
or
display
everything
here.
So
on
the
first
layer,
it's
only
the
amount
of
features
they
they
are
used
for
this
one.
For
this
example,
and
they
are
all
the
ones
like
you
can,
you
can
use
the
files
and
set
the
values
to
have
your
own
files.
You
can
use
templating
and
you
can
also
use
the
insights
with
trending
and
sharing.
F
F
They
have
it
there
and
also
help
them,
identify
the
back
and
the
feature
that
could
be
configured
as
a
value.
This
is
not
a
forum,
so,
like
said
also,
google,
there
is
a
template
that
needs
to
be
very
clear
with
the
business
requirements.
Why
is
that?
Where
is
happening
there
and
how
you
can
contribute
with
a
very
good
business
case?
And
another
thing
please
follow
the
manuals
and
trainings
regarding
the
graph,
because
I
didn't
do
in
some
points
and
the
cache
was
one
of
them
and
after
I
reviewed
the
documentation,
I
fully
get
it.
F
What
was
done
and
the
last
one
is
really
to
have
fun
with
it.
With
this
bunch
of
clues,
they
were
shared
by
the
microsoft
toolkit
and
also
to
also
to
the
community
itself,
because
I
only
picked
this
this
type
of
development
and
controls
and
working
with
the
community
who
was
literally
two
two
months
ago
and
and
I
was
able
to
make
this
a
full
transition.
F
A
Wow
fantastic
demo,
andre
great
great
stuff
and
love
to
see
the
use
of
the
graph
toolkit
there
in
in
really
a
clever
way
so
awesome
stuff.
There
might
be
some
questions
there
in
the
comments
for
you,
but
we're
going
to
go
ahead
and
move
on
to
nick.
If
nick
you
want
to
take
over
the
presentation
and
launch
up
your
demo
on
building
a
microsoft
teams,
user
bulk
membership,
update
tool.
G
Hi
everybody
I'm
nick
from
cardiff
university,
and
I'm
going
to
be
talking
to
you
today
about
the
team's
membership
update.
It's
a
web
part
that
I
created
to
update
the
membership
of
a
team
in
teams
at
the
moment,
we're
still
in
the
early
phases
of
rolling
out
actually
being
able
to
do
this
in
a
in
the
proper
way,
actually
using
school
data.
Sync
and
everything
else.
So
a
bit
about
me.
G
I've
been,
I
may
look
very
young,
but
I've
been
in
the
web
development
business
now
for
I've
got
nearly
14
15
years
so,
but
I've
only
been
doing
sharepoint
for
the
last
three
years
since
I
joined
cardiff
university
and
we'll
get
into
the
demo
straight
away.
So
this
was
built
out
of
a
need
for
our
staff
to
actually
update
the
membership
of
their
teams
based
on
membership
information
from
our
student
management
system.
We're
still
working
on
having
this
in
a
proper
automated
way.
G
So
it's
a
sharepoint
web
part
that
you
can
attach
onto
any
web
page
when
it
first
loads.
It
pulls
down
a
list
using
the
graph
calls
a
list
of
teams
that
you
are
a
member
of,
and
it
goes
through
that
looking
to
see
if
you
are
an
owner
of
that
team
and
then
shows
you
a
list
when
you
select
a
team
you
just
so
there
checks
the
ownership
again
just
to
make
sure
and
then
it
you
move
on
to
the
next
step,
which
is
selecting
a
csv
file.
G
This
has
been
updated
since
the
original
version.
My
original
vision
wasn't
using
the
file
picker
from
the
lovely
guys.
The
lovely
pnp
react
controls.
So
now
you
can
pick
from
a
one
drive
location
or
from
or
you
can
upload
a
file
individually.
So
I
will
select
this
form.
What
you'll
then
do
is
it
will
use
a
component
called
react
per
pass
to
just
pass
that
csv
file
and
produce
json
objects
for
each
of
the
files
which
I
can
then
plug
into
one
of
the
standard
fluent
ui
framework
table
modules.
G
So
you
can
see
here
it
gives
me
the
various
information
from
the
csv
file.
We
then
have
the
option
to
choose
the
column
that
contains
the
email
addresses.
We
actually
store.
Multiple
email
addresses
in
our
system
because
we're
university
people
tend
to
have
separate
email
accounts,
but
we're
only
after
the
university
one
which
matches
their
upn.
G
We've
then
got
the
option
then
to
remove
all
from
members.
This
is
where
it
will
go
through
the
csv
file
and
if
you
are
not
an
owner-
and
you
are
not
a
use-
a
member
of
the
in
the
csv
file,
it
will
remove
you
from
the
team
by
default
turn
this
on.
But
people
may
want
to
have
this
off
it's
again,
it's
there
for
making
sure
that
the
team
is
always
up
to
date
and
doesn't
have
people
that
shouldn't
be
there
and
when
you
hit
update,
I'm
not
going
to
do
this
now.
G
G
If
you
have
a
look
on
the
entry
for
this
part
on
the
sharepoint
framework
site,
you
can
actually
see
that
there's
a
little
animation
of
actually
being
used
in
teams,
so
I'm
going
to
head
over
to
code
now
so
again,
we've
got
the
api.
Permissions
say
that
you
do
need
the
couple
of
little
things
that
you
will
need
around
additional
controls.
Hopefully
this
is
size.
G
So
in
the
main
section
I'm
not
doing
much
here
apart
from
defining
the
log
list
and
allowing
users
to
select
it
again,
I'm
using
the
react
property
controls,
so
you
can
actually
select
the
list
control
and
I'm
just
I've
just
put
a
description
here.
That's
defined
inside
the
strings
file
of
what
the
log
list
needs
to
contain
and
then,
if
we
actually
have
a
look
at
the
code
itself,
so
there's
not
a
huge
amount.
G
That's
going
on
here,
I'm
certain
various
bits
of
initial
states
say
that
initially
it's
going
to
be
loading,
the
teams
and
we're
going
to
head
down
to
the
first
section,
which
should
be
the
component,
did
mount
section
so
on
on
the
did
mount
call.
What
I'm
doing
is
I'm
using
the
batch
function,
so
I'm
creating
a
batch.
That's
basically
going
to
go
away.
It's
going
to
grab
the
me,
so
basically
the
information
about
the
user
themselves
and
it's
going
to
get
the
teams
that
the
user
has
joined
again.
G
G
If
there's
any
errors
in
that,
it
will
just
put
them
into
the
logs
entry
as
errors,
so
the
users
can
see
it
that
way,
most
of
the
time
nine
times
out
of
ten
it's
because
the
permissions
haven't
been
assigned
or
sharepoint
has
taken
some
time
to
actually
assign
the
permissions
and
what
I'm
doing
is
just
going
through
the
graph,
I'm
just
adding
all
of
those
then
into
the
state
so
that
we
can
render
that
and
the
rendering
that's
this
drop
down.
That
appears
here.
G
So
when
you
select
something,
then
we
scroll
back
up
here
again.
This
is
one
of
my
first
ever
sharepoint
framework
parts,
so
things
are
a
bit
all
over
the
shop
compared
to
my
later
ones.
So
when
the
drop
down
is
changed,
what
we're
doing
then,
is
we're,
calling
the
owners
function
in
graph
just
to
see
just
to
get
who
the
owners
are
and
we're
going
through
then
and
making
sure
that
the
user-
that's
selecting.
G
That's
using
this
is
actually
an
owner
of
that
team.
If
you're,
not
an
owner,
you'll
get
an
error
saying
you
know.
No,
no,
please!
You
can't
update
the
membership
of
this
team.
What
the
system
also
does,
then
is:
it
adds
the
owners
to
a
separate
list
so
that
we
can
keep
track
of
it
because
you
don't
want
to
be
removing
owners
that
don't
necessarily
exist
in
the
csv
file.
G
G
So
the
first
thing
we're
going
to
be
doing
is
loading
the
members.
So
I
use
an
enum
here
just
to
say
what
the
state
of
things
are.
So
we're
loading
the
members
and
what
we're
going
to
be
doing
is
calling
the
graph
api
to
find
the
members
of
that
team.
I've
updated
this
since
the
initial
release
to
add
the
ability
to
reiterate
through
if
graph
has
paged
the
return
that
you
initially
get
wasn't
doing
that
initially
and
it
was
larger
teams,
larger
classes
that
was
actually
causing
an
error.
G
So
there's
some
log
entries
that
go
into
here,
just
to
say:
what's
going
on,
so
the
user
gets
some
feedback
of
what's
going
on
and
yeah.
What
it
will
do
is
then
go
through
the
comparing
the
members
with
the
csv
file
and
looking
to
see
if
they
exist
in
the
csv
file,
or
they
are
an
owner
of
the
team
and
then
it
will
decide
right.
I
need
to
delete
these
users
or
I
need
to
add
so.
G
The
first
bit
I
do
is
delete
the
unnecessary
users
if
the
user
has
chosen
to
orphan
the
members-
and
I'm
doing
this
via
again
graph
calls,
but
I'm
doing
this
in
a
slightly
different
way
in
the
fact
that
I'm
using
the
graph
batch
functions
and
I'm
using
something.
I've
made
an
interface
called
irequest
that
just
takes
any
any
element
as
the
request
item-
and
this
is
just
building
up
graph-
calls
to
delete
the
users.
I've
chosen
the
truncalizer
20,
because
I've
found
that
that's
the
best
one
to
use
for
graph.
G
All
this
looping
here
is
doing
is
split
in
the
people
that
need
to
be
deleted
into
chunks
of
20,
so
that
when
you
call
the
graph
you're
not
putting
too
many
requests
into
the
batch,
and
you
can
find
the
limits
on
the
batch
sizes
in
the
graph
rest,
api
information
on
docs.microsoft.com
and
then
what
we're
doing
once
all
that's
come
back
and
it's
happy
we
go
through
and
create
who
needs
to
be
added
and
then
we're
going
to
actually
do
the
call-in.
So
this
is
where
the
system
will
go
away
and
start
firing
off.
G
G
I
do
this
in
a
separate
function
just
for
just
so
I
can
iteratively
go
through
this
and
reef
and
it
can
just
call
itself
basically
so
again
same
as
I
was
doing
with
the
delete
functions,
I'm
creating
the
graph
batches
that
need
to
be
done.
So
this
is
where
you
actually
do.
Extra
bits,
because
in
graph
you
use
the
ref
function,
so
you
actually
need
the
object
id
of
the
user,
not
the
email
address.
So
you
actually
have
to
do
two
calls.
G
You
have
to
go
away
and
call
the
graph
to
find
the
object
id,
and
then
you
have
to
once
you've
done
that
you
have
to
build
another
batch
to
call
to
send
off
to
graph
with
the
actual
delete
function
so
yeah
and
that's
what
we're
doing
down
here.
So
we're
just
batching
that
all
up
I've
got
various
debug
bits
of
information
in
here
just
so.
G
A
Much
awesome
stuff
there.
Thank
you
very
much
for
that
demo,
nick
great
to
see
that
really
exciting,
thorough
demo
and
thorough
bit
of
coding,
so
that'll
be
a
great
sample
for
folks
to
reference
as
well
and
last
but
not
least,
we've
got
sebastian
leverett
with
a
microsoft
graph,
get
client
web
part
if
you're
ready
to
go
and
it
looks
like
you're
take
it
away.
H
I
am
ready,
hey
everybody
how's.
It
going
really
really
happy
to
be
able
to
go
through
it's
interesting.
Today's
call
was
a
lot
about
microsoft
graph
and
I'm
happy
to
see
that,
and
today
it's
kind
of
how
you
can
really
improve
your
shareprint
framework
solutions,
utilizing
the
latest
microsoft
graph,
client
in
sharepoint
framework.
So
a
little
bit
about
me,
I'm
a
sharepoint.
I
I'm
a
recovering
sharepoint
dev
been
a
long
time.
H
First,
amazing
that
the
sharepoint
framework
has
been
supporting
the
microsoft
graph
since
2018.
So
since
in
one
of
the
early
versions
of
sharepoint
framework,
I
cannot
remember
exactly
which
one,
maybe
someone
in
the
chat
could
add
it
right.
There,
sharepoint
framework
has
been
supporting
the
graph
with
the
graph
client.
H
Why
would
you
want
to
use
the
latest
well
first,
and
I
think
that's
the
most
important
one
is
to
basically
leverage
its
built-in
middleware
architecture.
What
does
it
mean?
It
means
that,
right
now
in
the
current
version
of
the
sdk,
that
is
in
spfx,
you
don't
have
retry
handlers.
You
cannot
create
chaos
in
your
apps
and
make
sure
that
they're
always
well
behaving
under
certain
circumstances,
especially
when
you're
about
to
hit
some
throttling
limits.
So
something
really
really
interesting
here
automatically
handle
throttling
with
the
latest
version
of
the
graph.
H
Also
you're
gonna
get
the
latest
types
if
you're
more
around
building
types
and
not
just
using
javascript
object
or
json,
you
can
use
the
types
directly
from
there.
You
can
get
raw
responses
and
not
just
type
responses,
there's
a
bunch
of
content
types
that
are
really
in
place
for
you,
instead
of
you
putting
all
of
them
so
really
useful
when
you're
a
developer
and
kind
of
a
lazy
dev
like
I
am
I'm
a
lazy
dev
and
I
want
to
like
use
the
most
out
of
what
an
sdk
can
offer.
H
So
how
we'll
accomplish
this?
But
you
know
what
let's
close
the
slides
now
and
let's
go
through
the
actual
code.
First
of
all,
we're
gonna
have
to
upgrade,
depending
on
which
version
of
your
rush
compiler,
you,
your
your
hat,
to
leverage
some
some
of
the
latest
typescript
capabilities
that
are
required
because
we
are
going
to
use
for
a
second
time
today.
Mgt
the
microsoft
graph
toolkit
microsoft,
graph
toolkit
will
be
what
will
be
providing
the
capabilities
of
having
access
to
that
latest
version
of
the
sdk.
H
So
let's
start,
let's
start
with
the
first
code
here.
So
basically,
the
first
thing
we're
going
to
do
is
when
our
web
part
will
get
initiated
or
initialized.
We
will
want
to
make
sure
that
we
set
that
our
global
provider-
this
is
provided
by
the
microsoft
graph
toolkit.
It
is
how
you
can
assign
kind
of
a
provider.
It
can
be
an
msl
provider
if
you're
working
in
regular
react
app,
but
when
you're
doing
sharepoint
stuff,
you
need
to
set
it
to
the
sharepoint
provider
in
by
passing
in
the
current
web
part
context.
H
Mgt
will
do
a
bunch
of
different
magic
right
there,
including
adding
the
right
version
of
the
sdk
making
sure
it's
all
authenticated
for
you,
so
you
don't
have
to
go
through
any
of
the
hoops
of
getting
an
access
token
to
microsoft.
Graph,
it's
going
to
respect
all
the
scopes
that
are
available
in
your
sharepoint
online
administration
portal,
where
you
can
see
all
the
different
api
access
that
are
being
used
or
through
the
web
parts
that
you
want
to
deploy.
H
Then
afterwards.
I
have
a
super
simple
graph,
client
here.
It's
that's
my
component.
It
there's
literally
nothing
in
there
a
simple
state,
a
component,
a
component
here
that
has
one
text
field:
that
is
the
query
or
the
api
request.
You
want
to
do
a
text
field
of
the
number
of
requests
you
want
to
emit
to
graph.
Here
it's
going
to
be
to
emulate
throttling
and
here
a
button
that
then
will
automatically
start
a
query.
So,
let's
start
with
this,
this
here
is
the
default
graph.
H
Client,
that's
how
the
calls
have
been
made
to
graph
historically,
so
you
get
the
graph
client,
you
get
the
client
and
once
you
get
it,
you
can
call
the
api
and
set
the
state.
So
let's
go
here
and
let's
go
see
what
it's
in
here.
So
let
me
reload
that
that
guy
just
to
make
sure
we
have
everything,
I'm
going
to
do
a
and
here
you're,
going
to
see
on
the
right.
It's
going
to
showcase
the
different
events.
So,
basically,
I
just
filter
on
event
with
status
quo
equals
200,
so
the
ones
that
are
completing.
H
H
Let
me
I'm
just
going
to
copy
paste
some
code
from
a
magic
notepad
that
I
have
on
the
other
screen
this
here
this
here,
what
it's
going
to
do
it's
going
to
iterate
the
number
of
time
that
I
have
in
my
number
of
requests
and
we'll
emit
these
calls
to
microsoft
graph
using
the
graph
client.
So,
what's
going
to
happen,
let
me
save
that
I'm
just
going
to
make
sure
that
my
webpack
has
been
working
excellent.
So
now
it's
reloaded
now.
H
If
I
come
here
and
I
hit
reload
on
this
screen,
I'm
going
to
do
exactly
this
call,
but
I'm
going
to
do
it
a
thousand
times
graph,
especially
on
the
on
on
some
areas
of
graph,
especially
here
on
the
mailbox,
has
some
throttling
limits.
You
cannot
call
graph
a
thousand
times
a
second
expecting
to
receive
results.
What
you're
going
to
receive
is
a
what
we
call
a
429
or
we're
going
to
tell
you
you're,
calling
graph
a
little
bit
too
much.
H
Can
you
back
off
just
a
little
bit
and
come
back
to
graph
in
a
couple
of
seconds?
So
now,
if
I
emit
this
call
a
thousand
times
to
graph
you're
gonna
see
a
bunch
of
calls
being
emitted
and
they're
gonna
be
emitted
in
in
one
after
the
other,
and
this
is
doing
that
in
parallel,
because
I'm
using
a
map
function
here.
H
This
is
going
actually
to
run
all
of
these
in
parallel,
not
sequentially.
So
we're
not
I'm
not
waiting
for
the
previous
call
to
complete.
What's
going
to
happen
here
is
you're
going
to
start
to
see
quite
soon
a
series
of
429
happening
here,
and
these
429s
will
not
resume
you're
going
to
get
the
request
you're
going
to
get
the
errors,
but
the
graph.
The
way
that
the
current
sdk
that
is
built
into
spf
x
is
built
you're
not
going
to
get
the
retry
that
exists
in
the
sdk.
H
So
let
me
just
change
that
up
and
do
exactly
the
same
thing
that
I'm
doing
and
doing
this
and
now
what
I'm
doing
instead
of
calling
the
the
previous
graph
client
I'm
just
going
to
bring
in
the
last
here.
Instead
of
using
this
ms
graph
client
factory
get
client,
I
am
going
to
use
the
global
provider
that
I
set
earlier
dot
graph
that
api,
and
here
I
will
be
able
to
pass
in
the
the
url.
H
H
I
can,
through
the
api
here
I
can
add
some
middleware
options,
so
it
says
here.
I
want
you
to
wait
five
seconds
and
retry
up
to
10
times
for
each
queries
that
will
be
in
there.
So
it
means
that
you
can
even
instruct
some
customized
version
of
that
retry
handling.
Now,
if
I
hit
save
I'm
going
to
do
a
small
reload
here
and
now
yes,
we
will
be
having
429s.
I
will
still
be
getting
a
couple
of
for
29.
H
That's
what
graph
is
all
about,
so
that's
what
we
want,
but
in
the
end
all
the
1
000
queries
that
we're
going
to
do
on
graph
will
indeed
complete.
So
if
we're
looking
here-
and
we
look
at
the
number
of
queries
here
when
it's
going
to
end,
we
will
be
at
1
000
out
of
x
number
of
requests
compared
to
what
we
had
earlier,
which
is
just
potentially
700
or
750..
H
So,
if
you're
doing
craft
work
with
spfx,
I
really
recommend
to
use
that
approach.
That
way,
you
don't
have
to
manage
the
429s
yourself.
You
can
leave
that
to
the
sdk
without
really
changing
any
type
of
code
in
your
stuff,
as
it's
basically
all
there,
for
you
really
really
simple
using
the
microsoft
graph
toolkit.
So
that's
what
I
wanted
to
share
with
you
all
today.
A
So,
thank
you,
andre
nick
and
sebastian
for
those
great
demos
today
really
appreciate
all
that
awesome
samples,
awesome
examples
of
stuff
you
can
do
across
microsoft.
365..
Thank
you
to
everybody
for
joining
the
call.
Today
this
recording
will
be
available
at
about
24
hours
on
our
youtube
channel.
You
can
follow
us
on
twitter
there.
Our
next
spfx
call
will
be
in
two
weeks
on
june
3rd
same
time,
and
our
next
general
dev
call
will
be
next
thursday
may
27th.
A
At
same
time,
all
the
community
calls
are
available.
There
aka
ms
m365
pnp
great,
to
see
everybody
today.
Thank
you
all
for
joining
us
again.
We've
got
a
ton
of
great
developer
community
calls
across
the
spectrum
of
the
platform,
and
we
do
as
well
we're
gonna
take
a
short
break
this
summer
and
sort
of
reconfigure
a
bit.
These
calls
to
make
it
all
a
little
bit
more
coherent
and
a
little
bit
easier
for
folks
to
attend
these
calls.