►
Description
SharePoint PnP Community - SPFx & JS SIG call on October 7. Demos on Creating a new Team using Viva Connections ACEs components from the Dashboard, Building a Microsoft Teams data dashboard with SharePoint Framework, and SPFx Design Patterns – Asynchronous Rendering. Released PnPjs Client-Side Libraries v3.0.0 early preview, and CLI for Microsoft 365 v4.0.0 GA with breaking changes. 1 extension, 6 web part and 6 ACE samples were delivered in the last 2 weeks! Wowmazing! Create samples, enter them in Hacktoberfest 2021. The host of this call is Patrick Rodgers (Microsoft) | @mediocrebowler. Q&A takes place as always 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
A
welcome
to
the
call
I'm
your
host
patrick
rogers,
and
we
have
a
great
agenda
for
you,
as
always,
we'll
run
through
patterns
and
practices
program
updates,
new
community
samples,
we'll
do
our
fun
picture
time
and
then
we'll
get
into
three
demos
from
divin,
hello
and
hugo,
so
very
excited
to
see
and
get
to
those,
but
first
a
few
quick
updates
opportunities
to
participate
in
patterns
and
practices.
We
always,
of
course,
encourage
and
welcome
you
to
do
demos
on
these
calls.
A
So
if
you
have
for
this
call,
we
try
and
focus
on
sharepoint
framework
or
javascript
related
client-side
script
related
or
at
pnp
program
related
things
so
reach
out,
of
course,
to
us
we'll
get
you
scheduled
on
a
call.
It
might
not
necessarily
be
the
next
call,
sometimes
we're
booked
out
a
little
bit.
We
will
get
you
on
a
call.
We
love
love,
love
the
demos
I
want
to
thank
everybody.
A
That's
done
them
and
encourage
you
to
share
some
of
the
work
you're
doing
for
your
companies
and
your
customers
as
appropriate
love
to
have
those
demos.
I
think
it's
the
best
part
of
the
call.
I
always
learn
something
new
from
the
way
folks
are
tackling
problems.
We
always
also
encourage
you
to
contribute
on
github.
You
can
report
issues,
submit
pull
requests
and,
of
course,
help
others
with
any
issues
or
questions
they
might
have
and
then
as
well
feedback.
We
really
appreciate
the
feedback.
Folks
give
us
how
things
are
going.
A
How
can
we
improve
the
calls?
Our
new
call
schedule
that
we
kind
of
started
after
the
summer
here
is
a
direct
result
of
some
of
the
feedback
we
got
over
the
last
year
about
how
the
number
of
calls
were
a
bit
much
or
a
bit
confusing.
So
we've
tried
to
simplify
that.
So
we
really
appreciate
the
feedback.
It's
sometimes
it
takes
a
bit
of
time,
but
we
do
try
and
act
on
it
and,
of
course,
positive
feedback
is
okay
too.
A
You
can
always
let
us
know
if
we're
doing
something
well,
and
perhaps
we
could
do
a
little
bit
more
of
it.
Now
we
got
our
slider
links,
so
we've
got
developer
videos
on
youtube.
These
are
topic,
focused
videos
that
will
bring
you
information
on
performing
different
tasks,
so
perhaps
making
a
new
web
part
doing
authentication,
there's
videos
around
provisioning
lots
of
great
content
there,
so
those
developer
focused
videos
as
well.
We
have
the
community
videos,
those
are
going
to
be
the
recordings
of
some
of
our
events.
A
Our
calls
such
as
this
one,
as
well
as
other
things
that
might
get
recorded
and
posted
up
there
from
the
community.
So
that's
a
great
way
to
catch
up.
If
you're
not
able
to
attend
any
of
the
calls
live,
they'll
all
make
it
up
there
on
youtube,
so
you
can
catch
up
with
them
at
your
leisure
as
well.
We
have
a
bunch
of
open
source
organization,
sharepoint
pnp
office,
dev
and
microsoft.
Graph
are
all
available
to
you
for
various
things:
sdks
learning
resources,
places
to
report
issues
and
as
well.
A
All
of
those
places
are
looking
for
your
contributions
as
well.
If
you're
interested
in
working
on
the
microsoft
graph,
they
would
love
to
have
folks
helping
out,
with
their
sdks
and
code
generation,
they're
doing
a
lot
of
really
cool
work
there
now
towards
the
v4
stuff
they're
working
on.
It's
really
neat
to
see.
So,
if
you're
into
that
certainly
check
that
out
and
as
well,
the
other
repos
all
are
interested
in
your
participation
too.
A
If
you
have
interest
sample
galleries,
we
have
a
tons
of
samples
for
teams,
spfx
power
platform,
spf
x,
extensions
as
well
as
list
formatting.
Those
are
great
places
to
learn,
and
it's
often
where
I
go
to
check
out
how
others
have
solved
problems
when
I'm
getting
started
thinking
about
something
so
encourage
you
to
do
the
same.
It's
really
a
fantastic
resource
for
the
community
built
by
the
community,
and
so
thank
you
to
all
of
you
and
I
encourage
you
to
check
it
out.
That's
a
lot
of
links
so
do
check
out
ak
dot.
A
Msl,
pnp
that'll
actually
get
you
to
all
of
those
links
and
all
the
content
from
the
patterns
and
practices
program
so
encourage
you
to
check
that
out.
Next
up
is
some
info
about
our
ongoing
tuesday
calls.
So
this
is
microsoft.
365
platform
calls.
This
is
latest
news
from
microsoft,
engineering,
as
well
as
demos.
Next
week,
the
12th
of
october,
that's
tuesday
at
8,
am
pacific,
we'll
have
andre
and
bob
doing
two
demos
on
progressive
web
apps
and
beyond,
and
bob
will
be
doing
hands-on
with
microsoft,
graph
file,
uploads
and
downloads.
A
So
two
great
demos,
as
well
as
lots
of
great
news
and
updates
around
microsoft,
365.
so
check
those
out.
You
can
download
the
invite
there
at
that
link
and
it's
another
great
call
for
the
community,
and
I
hope
you
can
check
that
out
as
well
we're
supporting
hacktoberfest
across
the
patterns
of
practices
organization.
This
is
something
put
on,
I
believe
it's
put
on
by
digitalocean
since
that's
their
link
there,
I
think
they're,
the
sort
of
overriding
organizer
but
register
today.
So
it
runs
for
the
month
of
october.
A
Pull
requests
are
submitted
to
any
pnp
github
repository
labeled,
with
hacktoberfest,
submit
four
pull
requests
in
the
month
of
october
and
you'll
get
a
shirt
for
the
first
55
000
people
that
do
that
and
look
for.
You
know
certain
things
are
tagged
in
the
repos
good
first
issue.
Help
wanted
is
a
great
way
to
find
stuff
to
work
on
and
as
well.
If
you're
unsure
how
to
get
started,
we
do
encourage
you
check
out.
The
sharing
is
caring
sessions.
They
have
first-time
contributor
sessions.
A
B
Awesome
thanks,
patrick
and
as
he
mentioned,
these
are
sessions
that
are
going
to
walk
you
through
hands-on.
Getting
involved
in
the
community.
Getting
involved
could
mean
utilizing
the
resources
available,
like
those
spfx
samples,
seeing
how
you
can
use
them
in
your
organization
to
learn
from
them.
Getting
involved
could
be
contributing
back
if
you
want
to
update
those
samples
or
you'd
like
to
get
more
involved
in
giving
back
to
the
community,
but
you're
not
sure
where
to
get
started
or
the
how
to
overcome
the
hurdles
that
may
be
preventing
you
like
how
to
use
github.
B
These
sessions
will
walk
you
through
in
a
safe
space,
inclusive
opportunity
all
hands
on
all
free
of
charge,
they're
not
recorded,
and
we're
going
to
do
all
of
that
together.
Our
newest
session
power
platform
samples
first
time
contributor,
is
coming
up
later.
This
month
we
have
the
ever
popular
amas
with
pnp
powershell
scheduled
for
october
26th,
and
we've
got
some
announcements
today
around
pnpjs
that
we
will
also
be
scheduling
an
ama
to
go
over
in
the
near
future
as
well
as
patrick
mentioned
these
sessions
that
are
inclusive
of
github.
B
Like
first
time,
contributors
like
community
docs
like
power
platform
samples,
they
do
count
towards
the
hacktoberfest
so
get
registered
and
register
for
any
of
these
aka.
Ms
forward,
slash
sharing
is
caring.
Now,
as
we
move
to
the
next
slide,
once
you
do
contribute
back,
we
love
to
celebrate
the
amazing
work
that
you're
doing,
and
so
the
recognition
program
is
here
to
do
just
that
we
have
partnered
with
credly,
which
is
the
same
credly
that
does
all
of
the
badging
for
certifications.
B
So
your
badges
and
the
recognition
program
will
sit
right
next
to
those
we've
got
a
lot
of
badges
in
progress,
we're
working
on
one
for
hacktoberfest,
the
power
platform,
independent
publishers,
connectors
we've
got
the
authors,
so
many
coming
soon
lots
of
fun
campaigns
get
involved.
We
do
need
you
to
opt
in
aka
dot.
Ms
forward
slash,
m365
pnp
dash
recognition,
patrick
back
to
you.
A
Awesome
great
updates,
thank
you
david.
As
always,
and
thank
you
to
everybody.
That's
participated
in
pnp
as
well
as
the
sharing
is
caring
sessions.
It's
a
really
wonderful
resource
for
folks
looking
to
learn
or
get
some
additional
guidance,
and,
with
this
we'll
hand,
things
over
to
vasa
for
sharepoint
framework
updates.
C
Excellent,
so
quick
update
on
sharepoint
framework
1.13
intended
to
go
live,
I
would
say
still
in
upcoming
weeks,
we
are
close
to
saying
upcoming
days,
but
will
not
be
next
week.
It's
okay!
So
it's
happening
relatively
soon.
It's
going
to
be
a
tuesday
so
relatively
soon
anyway.
One
of
the
keyboards.
Some
of
the
key
changes
here
is
that
there
will
not
be
any
more
a
local
workbench.
C
We
deprecated
that
in
1.2
1.13
1.12
there's
going
to
be
updates
on
the
on
the
supportability
of
typescript
teams.js
and
all
that
stuff
and
there's
going
to
be
a
cool,
really
image,
rendering
apis
updates
as
well,
which
are
optimizing
always
to
use
the
cd
empaths
for
your
images
as
well.
If
that's
possible,
so
there's
a
lot
of
a
lot
of
cool
stuff
over
there
primary
thing
being
the
viva
connections,
extensibility
support,
so
ac
is
going
to
be
there
available.
One
of
the
cool
things
in
in
this
release
will
be
also
this
one.
C
So
we've
got
a
lot
of
feedback
related
on
the
lack
of
microsoft
teams
or
development
for
localhost,
and
it's
it's
been
hard
to
do.
Development
of
microsoft
teams
extensibility
with
sharepoint
framework
because
of
the
lack
of
local
host
loading
easily.
So
I
spawned
at
1.13,
there's
going
to
be
an
initial
version
of
this.
It
will
not
be
necessarily
super
polished,
but
you
can
already
basically
host
and
do
development
inside
of
microsoft
themes
from
a
local
host,
so
you're
going
to
do
f.
Well,
you
can
do
debucking
and
all
of
that
stuff
super
easily.
C
As
thought
of
this
now
set,
the
first
experience
will
be
a
bit
rough,
we're
gonna
document
the
whole
thing
and
we're
gonna
make
it
easier
and
easier
in
the
future.
We're
working
with,
for
example,
with
the
team's
toolkit
v2
people
to
make
this
integrated
in
their
stuff.
Sooner
or
later.
Then,
what
happens
after
the
1.13
and
there's
going
to
be
performance
improvements
across
the
app
so
dive
in
runtime,
basically
meaning
the
runtime?
Well,
we
modify
things
and
optimize
a
lot
of
the
stuff
on
the
server
side
as
well.
C
Team
storage,
support
for
partnership,
performance,
sharepoint
framework
solutions,
so
you
can
target
the
team
store
in
the
app
source,
even
though
your
solution
is
using
japan's
framework
widely
requested
capability.
There's
a
new
app
catalog
experience
in
plans,
so
we're
modernizing
all
of
that
new
yeoman
templates
spirit
solution,
metadata
and
then
enable
service
principle.
C
Registration
is
something
new
also,
which
I
can
briefly
do
a
preview
and
explain
a
preview
which
basically
means
that
if
you
have
a
spfx
solution
which
is
dependent
on
an
api
which
is
hosted
in
azure,
currently
there's
no
easy
way
of
automating
that
consent,
as
you
are
updating
the
solution
in
into
app
catalog,
so
we're
looking
into
making
that
as
a
super
polished
experience.
So
you
can
actually
point
the
url
in
the
solution
file
so
that
the
end
user
administrator
will
be
redirected
there
to
consent
api.
C
And
after
that,
you
can
easily
call
the
api
within
your
solution.
So
really
streamlining
that
experience
as
well,
but
that's
a
brief,
quick
preview
on
what's
coming
on
the
spfx
in
the
future,
much
more
stuff,
obviously
in
the
pipeline,
which
we
can't
yet
talk
about,
but
cool
stuff.
Let's
move
forward.
A
D
You
can
see
we
have
a
change
to
the
slide,
because
we
have
a
big
announcement
today.
We,
as
of
today,
you
can
try
out
our
version.
Three
early
preview,
we
have
started
creating
nightly,
builds,
and
so
you
can
install
our
nightly
build
using
the
command
you
find
there
on
the
screen
and
if
you
check
out
that
pinned
issue
1636,
which
we've
been
referencing
all
along,
we
have
documented
some
getting
started
instructions
for
adding
it
to
the
sharepoint
framework
or
for
using
it
in
node.
D
There
are
some
bits
of
work
that
you
need
to
do
to
make
it
work
because
we
have
upgraded
our
code
base
significantly
so
definitely
check
out
those
instructions.
A
bunch
of
us
have
run
through
it
and
everything
seems
to
be
working
great,
but
certainly
submit
an
issue.
If
you
have
any
problems
in
and
or
find
any
significant
bugs,
it
is
pretty
rough,
but
it
so
it's
definitely
not
production
ready,
but
absolutely
please
check
it
out
and
give
us
your
feedback
and
also
all
the
changes.
D
The
major
changes
for
v3
from
v2
are
in
the
v3
branches
changelog
and
yes,
my
I'm
wearing
the
sort
of
ugly
build
sweater.
We've
been
announcing
that
all
along
and
julie
just
figured
that
out
yesterday,
because
I
don't
read
the
slides
so
anyway
direct
all
your
feedback
to
the
issues
list
as
normal,
and
please
follow
us
on
m365pmpjs
on
twitter
to
keep
up
to
date
with
what's
happening.
Thank
you
back
to
you,
patrick
great
stuff,.
A
I'm
very
excited
about
this
julie
has
done
a
ton
of
great
work
with
the
team
on
creating
this
v3
version,
so
I
hope
everybody
could
try
it
out
and
let
us
know
your
feedback,
I'm
just
watching
the
rabbit
video
which
gets
more
and
more
involved
each
week.
But
thank
you
to
julie,
thank
you
to
everybody.
That's
helped
out
with
v3,
I'm
very
excited
for
everybody
to
try
it
out.
I
think,
there's
a
lot
of
great
stuff.
A
E
No,
it's
gonna
be
albert
okay,
so
we
we
released
v4
today,
which
is
really
a
really
big
milestone
for
us,
really
really
cool
some
breaking
changes
in
v4
we
changed
a
bunch
of
commands.
We
changed
the
way
we
processed
group
members.
We
changed
quite
a
lot
of
commands
where
the
default
output
is
now
set
to
json.
We
removed
some
stuff
in
there,
so
the
value
wrappers
changed
in
some
of
the
commands
that
we
had.
We
had
some
duplication
that
we
fixed.
E
A
That's
not
it's
an
amazing
new
version
so
encouraging
everybody
to
try
that
out
really
fantastic
to
see
the
cli
continue
to
grow.
The
community
has
really
supported
this
and
helped
build
this
lots
and
lots
of
contributors
to
this.
It's
fantastic
to
see
this
get
to
v4,
so
great
work
to
the
team.
Try
it
out!
Let
them
know
what
you
think,
just
wonderful
stuff
here,
so
congrats
on
the
v4
release,
really
really
good
stuff.
So
thank
you.
Thank
you.
A
Thank
you
to
everybody
there
and
poor
gary
had
to
move
houses
just
to
just
to
manage
all
the
awesome.
That's
in
the
cli
now
moving
on
then
to
the
reusable
controls,
not
a
lot
of
announcements
here,
other
to
other
than
to
note
that
these
are
going
to
be
the
last
major
releases
of
the
v2
branch
for
the
controls.
So
two
nine
zero
and
two
seven
zero
moving
forward.
The
the
guidance
would
be
to
update,
then
your
solutions
to
spfx
1.12.1
or
above
and
the
v3
branch
of
the
controls.
A
F
Thank
you,
patrick,
so
I
don't
know
if
I've
mentioned
this
before,
but
we
have
sample
repositories
for
web
parts
and
extensions
and
we've
got
more
stuff
coming
up
soon,
but
I'll.
Let
david
talk
to
about
that
later.
So,
if
you're
looking
for
samples
with
web
parts,
if
you
want
to
just
learn
a
a
minor
pattern
or
you
want
to
see
almost
a
full-fledged
solution,
you
can
leverage
you
can
go
to
ak.ms
spfx-web
parts
or
aka.ms
spfx-extensions.
F
So
here's
some
of
the
updates
that
we've
received
over
the
last
two
weeks,
there's
actually
more,
but
I
wasn't
able
to
process
them
in
time.
I
will
be
processing
them
and
you
will
get
credit
for
the
next
call,
so
my
flows
list
by
adam
that
actually
allows
you
to
see
your
the
status
of
your
ongoing
flows
against
the
list,
which
is
an
awesome
extension.
I
recommend
you
you
go
play
with
that.
We
also
have
updates
to
the
sharepoint
crud
operations
web
part
where
it's
been
updated
to
spfx1121.
F
We
have
the
new
graph
group
viewer
by
zach
roberts
and
it
actually
allows
you
to
search
for
groups
in
your
tenant
and
allows
you
to
view
the
details
of
the
groups
and
as
well
as
the
group
members
and
export
the
list
to
a
csv
and
like
all
web
parts,
that
zach
does
it's.
It
really
looks
professional
and
it's
fully
featured
then
deep,
nachon
updated
the
questionnaire
teams
meeting
app.
F
If
you
haven't
tried
meetings
app
in
teams,
it's
a
great
way
to
add
extensive,
like
extensive
functionality
inside
of
a
meeting
in
teams,
and
it's
all
built
in
spfx.
We
have
the
updated
accordion
plugin
web
part
by
frederick.
He
added
the
sorting
fix
and
mohammed
ammar
actually
allows
you.
It's
an
improved
year
view
and
highlights
today's
style,
and
then
we
have
the
multi-screen
web
part
by
ari
gunawan
that
I
forgot
to
put
a
description
for
it,
but
it's
a
cool
web
part.
A
F
B
Back
to
you,
thank
you,
gentlemen.
All
right.
Well,
this
is
one
of
the
newest
repositories
for
us
in
the
pnp
umbrella
is
super
exciting,
a
viva
adaptive
card,
extensions
repository
or,
as
we
know
them
to
be
aces,
and
so
we've
already
started
getting
some
new
samples
put
in
here.
There's
a
couple
that
are
put
in
by
dipping
shaw,
create
teams
and
manage
team.
B
We're
going
to
see
one
of
those
demo
today,
actually
there's
another
one:
very
cool
around
planner
tasks
by
ejaz
hussein,
very,
very
slick
and
anup
tati
has
been
busy
busy
busy
three
tenet
service
health
articles
at
a
glance,
london,
transport
service
status
and
we've
got
a
couple
more
in
the
pipeline,
we're
processing,
one
of
which
was
by
zach
another
amazing
contributor.
Thank
you
all
really
great
stuff.
Keep
them
coming
really
excited
about
this
new
repository
reach
out.
B
A
C
G
C
C
Of
course,
I
think
that's
pretty
much
yeah
now
it's
maxed
out.
Let's
do
something:
everybody
thanks
everybody
for
being
part
of
this
community
and
please
keep
the
feedback
coming.
This
is
absolutely
brilliant.
Let
us
know
if
we
can
improve.
If
you
have
good
ideas
and
let
us
know
excellent
excellent
and
hopefully
you
will
be
in
las
vegas
dusseldorf
later
this
year.
Those
are
the
two
in
person
conferences
which
are
happening
later
this
year,
but
let's
jump
back
on
the
demos.
A
H
Thank
you
so
much.
Let
me
share
my
screen
good
morning
good
evening,
good
afternoon,
respectively,
I'm
defensive
working
at
a
rapid
circle
as
a
cloud
consultant
and
working
on
the
vs
technology
in
microsoft,
365
umbrella.
I
am
the
shop
corner,
mvp,
blogger
and
pnp
contributor
in
the
cli
microsoft
365
cli
commands
you
can
reach
me
out
at
the
twitter
linkedin
facebook,
github
repository
and
my
personal
email
address
today.
H
So
what
we
are
going
to
present
over
here
today
overview
of
ses,
cardview,
quickview
graph,
api
integration
with
acs
and
cardview
quickview
methods
to
handle
clicks.
So
what
are
what
is
the
meaning
of
the
adaptive
card
extension?
So
it's
a
framework
to
handle
the
custom
development
to
viva
dashboard
for
employee
experience
in
any
devices
like
laptop
mobile,
android
ios.
Whatever
the
card
view
is
the
one
component
where
a
user
land
first
and
from
the
card
view
he
goes
and
travels,
the
other
other
portion
of
that
component
or
adaptive
card.
H
The
quick
view
is
the
basic
ui
functionality,
where
user
can
put
our
business
business
logic
and
put
access
over
there.
How
we
do
graph
api
integration
into
the
ses
will
show
in
the
code
and
the
how
we
handle
the
multiple
clicks
on
the
card
view
and
quick
view,
I
will
show
you
in
the
code.
So
let's
go
with
the
code
walkthrough
when
we
start
with
the
spfx
adaptive
card
extensions
code.
H
The
code
structure
looks
like
something
this
here
is
the
one
queue
folder
the
card
view
folder
and
the
main
file
is
the
adaptive
card
extension.ts
file
so
into
the
adaptive
card
extension
ts
file,
the
main
main
engine
of
the
adaptive
card
is
the
navigator,
the
card
view
navigator
and
the
quickview
navigator.
So
whatever
and
number
of
the
quickview
and
cardview
we
want
to
use
in
our
solution,
then
we
we
would.
We
must
register
it
to
the
particular
navigator
engine
and
it
has
a
unique
id
over
there
here.
H
H
H
Yeah
so
team
creation
request
is
the
my
card
view
adaptive
card
extensions
and
into
that.
I
use
the
basic
card
view
over
here.
When
user
click
on
over
there,
then
one
form
is
popped
up.
So
it's
the
quick
view
and
inside
the
quick
view
I
write
down
certain
jsons
formula
over
there
and
inside
the
jsons.
I
put
my
controls,
where
user
will
enter
the
values
to
create
the
team
so
for
an
example
demo
to
pnp.
H
So
it's
the
first
quick
view
when
I
click
on
the
send
request.
The
second
quick
view
quick
card
over
here
and
it
requests
for
the
team.
The
graph
api
call
from
the
quick
view
and
once
the
team
is
created
successfully,
it
gives
me
the
success
message
over
there.
So
the
success
view
is
the
different
card
peak
view.
H
Let
me
go
to
the
code,
so
I
have
created
a
four
quick
view
over
here,
one
for
the
success.
Second,
for
the
quick
view
which
is
rendered
the
team
creation
form.
The
third
one
is
the
loading
view.
So
it's
the
continuous
process,
indication
that
the
team
is
going
creating
in
the
progress
and
the
one
is
the
error
view
in
somehow
the
an
internet
connectivity
issue
or
permission
issue.
H
So
we
render
the
error
view
in
and
when
the
responses
come
from
the
graph
api
inside
the
card
view,
I
have
used
the
single
button
over
here
and
on
the
button.
Click
event.
I
call
the
quick
view
register
id.
So
what
is
the
quickview
register
id?
It
is
we
register
on
the
adaptive
card
extension.ts
file
over
here
with
the
navigator
and
yeah
so
from
the
card
view
selection
when
user
click
on
the
card.
H
My
quick
view
is
called
and
it
render
the
quick
view
component
so
quickview.ts
file
over
here,
and
here
I
am
calling
that
json
formula,
so
how
my
form
looked
like
when
user
want
to
create
a
theme
so
inside
the
template,
I
created
a
template.json
file
and
this
is
the
json
payload,
which
is
responsible
for
hold
the
scenario
here.
I
have
declared
the
text
box
for
the
new
team
request,
input
text
for
the
display,
name,
input
text
for
the
description
and
the
choice
set
inside
the
choice
set.
H
H
The
owners
email
address
the
member's
email
address
so
based
on
the
requirement,
we
can
extend
these
adaptive
card
extensions
on
your
for
your
organization
and
so
inside
the
quick
view
when
user
click
on
the
on
action
on
the
submit
button,
then
on
action
method
is
called
and
it
checks
that
which
id
is
action
actionable
or
which
id
is
clicked.
So
if
it's
a
submit,
then
I
quick
navigator
push
to
the
loading
view
register
id.
H
So
loading
view
is
my
the
particular
image
where
user
know
that
yeah
the
process
is
going
start
and
I
need
to
wait
for
certain
moments
so
one
once
the
loading
view.
Is
there,
then,
in
the
background
process,
what
I
am
taking
the
values
from
the
fields
into
the
teams
property,
which
I
have
created
interface
for
that,
and
I
call
the
graph
api
over
here
and
it
responds
the
particular
true
or
false
value.
H
If
the
team
is
created
successfully,
then
it
gives
me
a
true
and
if
request
is
team
is
not
going
to
create
successfully,
then
it
gives
me
a
false
so
based
on
the
response,
I
change
the
quick
view
again.
So
if
the
successfully
trim
creation,
I
call
the
success
view
register
and
if
the
team
creation
is
failed,
then
I
call
the
adderview
register
id
so
inside
the
successful
register.
It's
it's
the
different,
quick
view.
H
Success
view
dot,
ts
and
inside
that
I
am
passing
the
another
json
over
there.
So
for
the
success
I
created
something
like
this
text
box,
subtitle
action
submit
close
close
and
the
description
and
for
the
error
view
same
thing
is
there,
but
the
values
should
be
different,
so
we'll
get
the
value
from
the
data
method
when
the
quick
view
is
rendered
on
the
particular
card.
H
So
when
success
error
is
occurred,
then
into
the
title,
user
plus
subtitle
will
be
error
record
while
creating
a
team
and
the
description.
So
what
should
be
the
reason
why
the
team
creation
process
is
failed,
so
the
particular
method
that
we
can
update
dynamically
inside
the
loading
view
template
it's
a
very
basic
json
template
where
I
just
put
the
image
tag
over
here
and
the
default
image
I
put
from
this
location.
H
Yeah,
so
how
I
come
to
know
that
I
need
to
create
this
type
of
the
extension
for
the
viva
dashboard
so
many
times
in
the
future.
Microsoft
is
promoting
the
viva
connection
very
briefly,
and
some
people
need
to
create
the
teams
from
the
mobile
so
how
they
can
create
how
why
should
they
go
to
the
particular
iit
team
and
request
that
please
create
a
team
for
me,
and
this
is-
are
the
display
name,
and
these
are
the
descriptions
so
to
avoid
those
communication.
We
can
start
with
this
type
of
adaptive
card.
H
Extensions
and
manager
can
directly
create
teams
from
the
dashboard
from
the
dashboard,
and,
yes,
we
can.
We
can
restrict
the
particular
adaptive
cards
by
applying
the
user
target
target
audience
feature
of
the
of
the
adaptive
card
extensions.
So
yeah,
that's
from
my
side,
if
you
have
any
query
or
questions
reach
out
to
me.
Thank
you.
So
much.
A
Awesome
stuff,
thank
you
so
much
for
that
demo.
Again,
it's
really
exciting
to
see
folks
start
to
get
into
these
aces
and
and
doing
some
samples
and
and
development
and
learning
around
that.
So
thank
you
for
sharing
that
with
us
and
with
that
we're
gonna
move
on
to
paulo
who's,
going
to
walk
us
through
building
microsoft
teams,
data
dashboards
with
sharepoint
framework.
G
Thank
you,
patrick.
Thank
you.
Yes,
today,
we're
going
to
talk
about
a
sample
that
we
just
released
and
which
is
a
sample
about
how
to
create,
with
sharepoint
framework,
a
dashboard
using
tools,
libraries
and
techniques
that
we
have
available
when
developing
micro365
solutions
and
the
overall
idea
of
this
sample
is
to
provide
developers
a
solution
that
they
take
inspiration
from.
If
they
want
to
create
something
like
that.
So
what's
inside
the
sample,
I'm
going
to
show
you
there
is
a
teams,
personal
app,
which
is
configurable
on
a
per
user
basis.
G
We
have
a
multiple
tabs
in
the
personal
app
it
can
be
also
used
as
a
client-side
web
part
in
sharepoint
online.
The
ui
is
fully
integrated
with
microsoft
teams,
and
we
also
have
an
example
of
automated
provisioning
of
artifacts
like
fields
and
lists
and
content
in
through
microsoft,
graph
in
the
microsoft
365
workloads,
in
order
to
do
the
setup
of
a
set
of
demo
items
and
demo
content
to
show
the
output
and
the
ui
of
the
sample.
G
As
well
as
the
capability
to
handle
the
configuration
of
the
team,
personal
apps,
the
support
for
multiple
tabs,
we
need
to
see
how
you
can
do
that
whenever
you
want
to
create
a
sharepoint
framework
solution
and
how
to
make
it
configurable.
Also
in
sharepoint
online,
and
only
from
the
ui
of
microsoft
teams.
And,
of
course,
the
provisioning
of
the
content
and
the
technical
solutions
that
we
put
in
place
to
achieve.
These
goals
are,
of
course,
the
sharepoint
framework.
G
We
use
micrograph
under
the
cover
of
the
sample,
as
well
as
why
not
the
graph
toolkit
to
render
the
ui
and
to
use
some
custom
template
for
a
better
rendering
of
the
ui
of
this
sample
dashboard,
as
well
as
the
pnp
react
controls
together
with
graph
toolkit
and,
of
course,
the
pmpjs
as
the
main
library
to
do
the
code
based
provisioning
inside
this
solution
to
supplement
multiple
tabs.
We
had
to
create
a
manual
manifest
for
teams
and
in
order
to
support
the
custom
configuration
on
a
per-user
basis.
G
We
are
relying
on
the
application,
personal
folder
capability
that
we
have
through
microsoft
graph.
So
this
is
just
to
give
you
an
idea
of
what
we
are
going
to
briefly
see
in
the
upcoming
demo
and
that's
why
I'm
now
moving
to
the
actual
demo
environment,
to
show
you
the
the
sample
in
action
and
then
to
play
with
the
code
base.
So,
first
of
all,
this
is
the
url
of
the
sample
on
under
the
hp
devfx
web
parts
repository
under
samples
and
react
teams.
G
Lead
dashboard
is
the
name
of
the
new
sample
in
themes.
This
is
how
the
sample
looks
like.
So
you
see
it's
a
dashboard
based
on
a
set
of
charts,
but
with
some
content,
which
is
personal
for
the
user.
In
fact,
this
is
a
personal
app
in
teams.
You
can
see
your
calendar,
you
can
see
your
tasking
to
do.
G
You
can
see
documents
or
items
which
are
interesting
for
you,
as
well
as
you
can
have
an
additional
tab
for
providing
settings
in
order
to
configure
just
for
the
sake
of
having
some
demo
data
in
order
to
configure
lists
items
and
fields
in
sharepoint
online,
as
well
as
eventually
demo
items
in
your
calendar
or
in
a
to-do
list.
Just
for
the
sake
of
having
close
to
real
content,
rendering
in
the
ui
of
this
component
or
string
teams
component
that
of
course,
can
be
hosted
also
as
a
web
part
in
sharepoint
online.
G
As
we
all
know,
and
if
you
want
to
configure
this
one
in
sharepoint
online.
Of
course,
you
can
just
edit
the
page
and
use
the
property
pane
of
sharepoint
online,
but
in
the
property
pane
of
the
sharepoint
framework
web
part
in
sharepoint
online.
We
basically
have
the
same
functionalities
that
we
have
in
the
settings
tab
inside
our
sample
solution.
So
how
did
we
build
this
solution?
G
G
This
is
really
useful
and
the
overall
result
will
be
that
from
a
one
drive
point
of
view
in
the
apps
folder
of
every
user,
there
will
be
a
subfolder
representing
the
app
and
that's
interesting,
because
we
are
in
sharepoint
framework
and
most
likely.
We
know
that
from
a
sharepoint
framework
point
of
view.
G
Unless
we
use
the
domain
isolated
model,
every
single
application
will
be
under
the
same
app
and
in
fact
we
have
a
sharepoint
online
client
accessibility,
web
application
principle,
which
is
the
name
of
the
azure
active
directory
up
under
the
cover
of
every
sharepoint
framework
solution,
at
least
by
default,
and
in
there
we
have
our
json
file
with
all
of
our
settings.
Of
course,
if
you
want
to
have
your
own
folder,
you
can
create
an
isolated
domain
web
part
and
that
will
have
a
dedicated
application.
So
that's
one
of
the
interesting
part
of
the
story.
G
Moreover,
when
we
render
the
application,
of
course,
we
use
mgt,
so
we
register
provider
of
ngt
from
authentication
point
of
view,
which
is
the
sharepoint
provider
in
order
to
use
the
contents
of
spfx,
and
we
also
configure
pmpjs,
because
we
use
that
one
as
well
in
the
rendering.
We
just
rely
on
a
react
component,
which
is
this
one
and
in
this
component,
at
the
very
end,
aside
from
loading
through
a
data
service,
all
of
the
content
that
we
want
to
render
and
the
data
service.
G
We
rely
on
pmpjs
and
graph
to
read
all
of
the
data
that
we
need,
but
in
the
component,
when
we
do
the
actual
rendering
we
simply
render
a
dashboard
control
of
pnp
controls
and
in
that
one
we
configured
all
of
the
widgets.
So
all
of
the
sections
of
the
dashboard
in
order
to
have
the
chart
control
of
pmp
controls,
for
example.
So
this
method
will
simply
give
us
back
a
chart.
Control
of
pnp
controls
as
well
as
we
can
eventually
use.
G
If
I
go
back,
we
can
eventually
use
the
mgt
components
like
in
this
widget,
where
we
say
get
my
data
and
this
one
will
give
you
back
the
agenda.
Mgt
component,
the
micrograph
toolkit
component
with
a
set
of
custom
templates
that
we
defined
right
here
in
this
file
in
order
to
have
a
custom
rendering
for
all
the
items
that
we
want
to
see
in
the
rendering
of
the
agenda,
and
the
same
applies
for
the
to-do
list.
G
So
this
is
to
give
you
an
idea
of
what
you
can
do
when
you
want
to
create
a
solution
with
a
nice
ui,
fully
integrated
with
teams
based
on
all
of
the
components
that
we
have.
But
there
is
more
we
want
to
have.
We
wanted
to
have
two
tabs
in
our
personal
app
and
that's
why,
in
the
teams?
Folder
of
our
solution,
we
manually
created
a
manifest
and
in
there
we
configured
two
different
static
tabs.
G
One
targeting
delete
access
dashboard
that
we
just
saw
and
another
one
targeting
the
settings
with
part,
which
is
the
one
providing
the
buttons
to
configure
and
to
set
up
the
solution
and
in
order
to
do
that
in
spf
x,
so
you
simply
need
to
manually
create
a
manifest.
You
have
to
zip
the
manifest
and
the
icons
into
a
file
called
teamspfxapp.zip,
which
is
well
documented
on
docsmix.com.
G
So
this
is
yet
another
interesting
functionality
that
we
have
in
sharepoint
framework.
Whenever
we
want
to
create
a
more
complex
solutions
which
do
not
rely
on
a
single
web
part
but
rely
on
multiple
web
parts,
which
will
become
marked
multiple
tabs
in
your
solution
again
and
furthermore,
talking
about
what
we
did,
we
are
using
mpt.
So
in
the
package.json
file,
we
are
referencing.
G
The
ngt
react
in
dngt
spfx
packages,
because
we
want
to
have
a
full
integration
of
inside
sharepoint
framework,
and
that's
why
we
can
then
say
in
the
web
part
that
we
register
the
provider
the
sharepoint
provider
as
the
global
provider
for
mgt.
So
this
is
just
to
give
you
an
idea
of
what
is
quite
easily
doable
using
all
the
rich
components
and
controls
that
we
have
available
through
pnp
and
through
microsoft,
in
order
to
easily
create
a
real
or
a
close
to
real
solution
hosted
in
teams
and
sharepoint
online.
G
You
also
have
some
references
on
the
slide
deck
which
I'm
going
to
share,
also
in
the
chat,
if
I
can
talk
and
copy
and
paste
at
the
same
time,
let
me
see
if
I
can
do
that.
Yes
looks
like
I
can
so
here
is
a
list
of
useful
links
that
you
can
keep
into
account.
If
you
want
to
dig
into
the
topics
that
we
saw.
G
For
example,
the
idea
of
using
the
custom
settings
stored
in
the
uproot
folder
comes
from
a
blog
post
by
valdec,
which
shared
this
brilliant
idea
of
using
this
functionality
for
storing
settings
as
well
as
you
can
find
links
to
all
the
other
libraries
and
tools
that
we
are
using
in
this
solution,
and
I
think
that's
all
for
me,
patrick
so
back
to
you.
Thank
you.
A
Fantastic
paolo,
that's
a
really
fully
realized
sample
demo.
There
lots
of
stuff
for
folks
to
learn
in
that
code
certainly
encourage
everybody
to
check
that
out.
Try
that
out
just
great
stuff.
So
thank
you,
paulo
for
sharing
that
with
us
and
last
but
not
least,
we're
on
to
hugo
for
spfx
design
patterns
asynchronous
rendering.
F
Hi,
everyone,
I'm
hugo,
and
what
we
thought
we'd
start
doing
is
we
start
doing.
We
thought
we'd
start
doing
some
regular
sessions
called
spfx
design
pattern
sessions
on
these
calls,
and
the
goal
here
is
that
we're
constantly
innovating
and
improving
the
sharepoint
framework,
and
we
want
to
make
sure
that
everyone
is
is
familiar
with
some
of
the
best
practices
some
of
the
design
patterns,
so
sometimes
we're
going
to
cover
some
materials
that
you
may
already
be
familiar
with,
but
we
want
to
make
sure
that
everybody
is
kind
of
brought
to
the
same
level.
F
What
I
would
love
is
your
feedback
at
the
end
of
this
session.
My
my
twitter
account
is
here
and
also
my
blog
for
some
reason
so
feel
free
to
to
tweet
at
me
to
let
me
know
what
kind
of
sessions
you'd
like
to
see
and,
of
course
I
appreciate
the
the
heart
signs
and
the
the
applaud
signs
and
things
I
just
so
we
understand
hey.
Are
we
doing
the
right
thing
today
we're
going
to
be
talking
about
asynchronous
rendering
it's
one
of
my
favorite
topics
and
here's?
Why?
Right?
There
is
a
play.
F
That's
affecting
millions
of
users
every
day
right,
it
costs
organizations,
lots
of
money
just
due
to
loss
of
productivity
and
it
reduces
user
engagement.
It
makes
people
feel
that
their
system
is
buggy
and
slow,
and
you
know
that's
right.
We're
talking
about
slow
web
parts
and
not
only
just
slow
web
parts.
We're
also
talking
about
slow
web
part
pages,
slow
ace,
you
know
aces
slow
teams,
applications
and
people
will
often
blame.
You
know
the
the
system
when
it's
really
probably
just
a
matter
of
how
we're
rendering
the
web
part.
F
You
can
actually
put
some
dynamic
stuff
in
there
like,
for
example,
if
you
want
to
look
at
some
of
the
properties
that
have
been
set
on
the
web
part
instead
of
passing
a
hard-coded
string
here,
you
could
do
that
now.
The
problem
is
what,
if
I'm
trying
to
do
synchronous
rendering,
but
with
data
right,
so
I'm
calling
data
and
I
don't
have
control
over
how
long
it
will
take.
F
So,
let's
take
the
same
example
here
and
I'm
just
going
to
use
the
same
render
method,
but
this
time
I'm
going
to
be
calling
some
kind
of
fancy
method
out
there
that
returns
results.
Maybe
it's
calling
an
api.
Maybe
it's
calling
a
website
or
something
like
that,
but
the
problem
is:
this
is
synchronous.
So,
while
you're
doing
this,
the
web
part
is
going
all
right,
I'm
going
to
wait
for
you
before.
F
I
can
render
anything
and
then
once
it
gets
the
results,
then
it
will
render
the
html-
and
you
know
you
inject
it
to
the
page
like
you
would
normally
do
now.
Let's
look
at
what
that
does
on
a
page,
so
here
I
have
a
web
part.
Well,
this
is
just
an
out
of
the
box
web
part,
but
if
I
just
show
you
if
I
refresh
the
page
here-
and
I
hope
that
yeah
give
me
a
second-
my
my
gulp
serve-
has
actually
died.
F
So
that
means
that
the
web
part
itself
is
going
to
wait
before
it
returns
results
we're
almost
there.
Of
course
it
decided
to
stop.
As
I
was
about
to
present
all
right,
I
should
be
ready
to
reload
now.
Okay,
so
if
I
start
this
again,
I
take
the
just
the
out
of
the
box
web
part.
All
right,
you
see,
the
the
picture
web
part
is
actually
pretty
fast.
Now,
if
I
add
my
synchronous
web
part,
one
of
the
things
that
you'll
notice
is
that
well
the
first
time
I
added
it,
it
seems
like.
F
Is
this
broken?
You
know
I
mean
I
wouldn't
be
surprised
if
it
was
because
it's
code
that
I
wrote,
but
this
is
not
good.
This
is
not
an
issue
with
the
code
that
I
wrote.
This
is
an
issue
with
how
long
it's
taking
to
retrieve
the
results,
and
if
I
refresh
the
page,
let's
just
do
this
now
with
the
web
part-
is
added.
F
It's
actually
going
to
do
something
like
this,
where
it's
like.
Okay,
the
web
part,
is
stopping
pretty
much
the
whole
page
from
rendering
in
time
and,
of
course,
I'm
exaggerating
the
results
here,
but
this
is
actually
what
it
does
in
tiny
little
increments
throughout
your
throughout
your
your
sites,
throughout
your
your
teams,
you're
injecting
web
parts
that
could
potentially
sew
down
your
application.
F
We
can
actually
use
something
called
asynchronous
rendering
so
asynchronous
rendering
the
only
thing
that
you
need
to
do
really
is
you
need
to
actually
go
in
and
say,
okay,
so
this
method
is
asynchronous
and
asynchronous.
If
you,
if
you're,
not
familiar
with
the
term
right,
it
means
that
we're
not
trying
to
keep
things
in
sync
we're
just
kind
of
we're
going
to
launch
something
and
we're
not
going
to
wait
for
it
to
come
back
we'll
just
handle
later
when
it
comes
back
we'll
handle
it
separately.
F
That
way,
everything
else
can
continue
moving
forward
and
everything
seems
to
be
more
performant,
so
the
web
part
needs
to
return
a
promise.
In
this
case.
It's
a
void.
Promise
like
many
people
that
I
know
and
then
one
one
things
that
I'm
gonna
do
here
is
I'm
going
to
render
just
this
little
spinny
thing
just
to
show
you
kind
of
hey
we're
busy
right
now,
we'll
get
our
data
and
that's
the
part
that
takes
long
but
we're
you'll
notice
that
we
make
a
wait
statement.
So
we're
saying
this
is
asynchronous.
F
Wait
for
this
to
come
back
and
then
give
me
the
results
and
then
just
like
before
we'll
just
render
the
results.
Now
the
problem
is
in
the
documentation.
One
of
the
things
that
it
says
is
the
web
part
will
wait
an
indeterminate
amount
of
time
before
it
renders
now
what
I
think
that
means
behind
the
scenes.
F
F
If
you
go,
look
at
the
documentation
on
docs.microsoft.com
you'll
see
that
the
web,
the
base
webpart
class
has
an
is
render
async
method
and
it's
a
property.
So
you
just
return
true
or
false,
and
it
says
you
know
when
now
there
is
something
that
you
need
to
do,
though,
if
you
do
say
isrender
is
sync
is
true:
sharepoint
is
not
going
to
wait
for
like
it's
just
going
to
continue
and
it's
expecting
you
to
call
a
method
called
render
completed.
I
think,
but
we'll
see
it
on
the
next
slide.
F
F
I
in
this
case
I
had
the
little
spinny
thing
because
I
was
getting
fancy.
I
render
the
web
part
and
then
once
I'm
done,
I
actually
tell
sharepoint
render
is
completed
and
that
will
kind
of
force
it
to
kind
of
realize.
Oh
okay,
I'll
you
know,
that
means
I
should
be
faster
now.
Let
me
take
the
exact
same
web
part
that
we
had
before
and
it's
going
to
be
slow
and
we'll
we'll
talk
about
that
in
a
second.
F
But
because
again
I
was
trying
to
be
obnoxiously
slow
in
terms
of
how
to
render
this
webpart.
So,
let's
refresh
the
page
without
the
web
part.
Let's
add
the
same
web
part
as
before,
except
this
time
it's
going
to
be
asynchronous,
rendering
you'll
notice
that
right
away
the
web
park
starts
doing
stuff,
but
it's
just
not
rendering
data
right
and
that's
fine,
like
we'll
talk
in
a
separate
session
how
to
handle.
You
know
weights
and
things
like
that.
F
So
it's
just
one
of
those
things
that
either
people
are
not
aware
of-
or
it's
not
documented
properly
but
and
the
thing
is
progress.
Indicators
make
slow
systems
feel
less
insufferable
right.
So
if
I
have
a
web
part
that
does
nothing
and
I'm
not
telling
people
hey
I'm
about
to
render,
then
people
will
think
the
system
is
slow.
Sharepoint
is
slow,
it's
buggy,
you
know,
teams
is
slow
and
so
using
progress
indicators
and
showing
the
users
that
there's
something
happening
has
a
lot
of
advantages.
F
F
It
also
offers
users
a
reason
to
wait
for
the
system
to
finish,
because
it
says:
hey,
I'm
doing
something,
I'm
going
to
be
giving
you
results
soon
enough,
and
it
can
actually
reduce
the
user's
perception
of
time
and
it
actually,
users
actually
devote
some
cognitive
resources
to
like
to
the
feedback
itself
and
they
pay
less
attention
to
the
weight.
And
if
you
haven't
attended
the
session
that
david
and
I
do
at
a
lot
of
conferences,
it's
I
can't
remember
what
it's
called,
but
the
microanimation
session.
F
F
Now
the
human
eye
can
detect
or
the
human
brain
can
detect
delays
as
short
as
one
tenth
of
a
second,
so
anything
that
takes
longer
than
that
doesn't
feel
instant.
So
the
rule
here
is
anything,
that's
a
second
or
more
is
enough
to
actually
interrupt
the
person's
conscious
thought
process.
So
what
do
you
do?
F
F
But
you
know
you
want
people
to
understand
that
hey
we're,
I'm
not
just
hung
here,
I'm
not
just
frozen,
I'm
actually
making
progress
and
one
of
the
rules
that
I
would
say
is
please
don't
ever
put
a
button
that
says
you
know
our
message.
That
says,
don't
push
this
button
again,
we
got
you
covered,
that's
probably
the
worst
thing
to
do
so.
F
One
of
the
things
that
we'll
talk
about
here
is-
and
I
know
I'm
running
out
of
time,
but
the
the
fluent
ui
user
interface
has
something
called
the
shimmer
interface
we're
not
going
to
cover
it
today,
but
investigate
this,
because
the
shimmer
interface
allows
you
to
actually
render
a
temporary
user
interface.
That's
that
makes
the
user
think
okay,
this
is
almost
there.
It's
almost.
F
The
data
is
almost
loaded,
it's
you
know,
and
in
a
lot
of
case
users,
don't
even
notice
that
you
actually
are
rendering
a
shimmer,
so
it
makes
the
system
feel
faster,
even
though
it's
not
necessarily
faster
all
right.
Let
me
wrap
this
up.
We
have
a
couple
samples
out
there.
If
you
want
to
see
good
examples
of
how
to
use
the
render
async,
you
have
the
microsoft
graph
people
search
web
part
and
we
have
the
hdm,
not
html
htm
templating
web
part
out
there
in
the
spfx
webpart
repository.
F
A
All
right,
thank
you
so
much
for
that.
Wonderful
demo
performance
is
a
very
important
thing
in
every
application,
so
step.
One
is
improving
that
performance
and
step
two
is
providing
a
good
experience
when
loads
are
a
little
bit
longer,
so
fantastic
summary
there
and
some
great
patterns
for
folks
to
follow
in
their
solutions.
A
Thank
you.
Everybody
for
joining
the
call
recording
will
be
available
about
24
hours
on
our
community
video
channel.
You
can
follow
us
at
those
addresses
there
on
twitter.
Our
next
spfx
call
will
be
in
two
thursdays
on
october
21st
at
7
a.m.
Pacific
and
the
next
general
dev
call
be
next
thursday
october
14th
at
7
a.m.
Pacific
all
the
community
calls
are,
of
course
available
at
that
link.
We
talked
about
earlier
ak
dot,
msl
m365
pnp.
A
Thank
you,
everybody
for
joining
us
there's
some
other
calls.
You
can
always
attend
if
you
are
interested
and
as
well,
you
can
catch
up
on
the
recordings
if
you
can't
make
them
live.
Thank
you
to
everybody
for
joining
the
call
today,
thank
you
to
all
our
presenters
and
that's
dippin,
paolo
and
hugo.
As
a
reminder,
and
just
thank
you
to
everybody
and
we'll
talk
soon,
have
a
great
rest
of
your
week.
Bye,
bye,
bye,
bye.