►
From YouTube: SharePoint Framework Community call – 15th of July 2021
Description
SharePoint PnP Community - SPFx & JS SIG call on July 15. Two demos delivered: Building COVID attestation solution for Microsoft Teams and Viva Connections with SPFx, and Building SharePoint Framework solutions with Microsoft Teams Toolkit v2. Nine PnP SPFx web part samples announced! Released PnPjs Client-side Libraries v2.7.0, CLI for Microsoft 365 v3.12.0 Preview, and PnP Modern Search v4.3.0 & v3.21.0. Update on SharePoint Framework v1.13.0 beta - target release end of July. Register for events on Sharing-is-caring. PnP Recognition Program announced. The host of this call is David Warner II (Catapult Systems) @DavidWarnerII. 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
We'd
like
to
warmly
welcome
and
thank
you
all
for
attending
the
microsoft
365
sharepoint
framework
and
javascript
special
interest
group
bi-weekly.
Sync
today
is
july
15
2021.
My
name
is
david
warner
with
catapult
systems
and
a
pnp
team
member,
and
I
will
be
acting
as
your
host
in
place
of
patrick
rogers.
A
Our
agenda
for
today
is
going
to
cover
the
latest
updates
on
sharepoint
framework,
we're
going
to
see
some
patterns
and
practices
updates
covering
pnpjs
cli
for
microsoft,
365,
reusable
pnp,
spf,
x,
controls
and
spfx
search
web
parts.
Then,
of
course,
we're
going
to
take
a
look
at
the
new
community
samples
and
everyone's
favorite
picture
time
with
together
mode.
A
The
first
is,
of
course,
doing
a
demo,
an
x
demo
on
this
call
or
the
other
pnp
call
you
can
host
and
show
a
web
part
an
application,
customizer
provisioning
anything
you
create.
We
would
like
to
see
we'd
love,
to
see
collaboration
in
the
community,
love
to
see
you
willing
to
share
with
the
community
all
of
the
creations
that
you
develop.
So
we
invite
you
to
apply
and
reach
out
to
anyone
on
the
pnp
team.
To
do
that,
you
could
also
cover
pmpjs.
As
you
see
cli
from
microsoft,
365,
reusable
controls,
yeoman
generator.
A
You
can
contribute
on
github
if
you'd
like
to
just
help
upgrade
a
sample
or
update
some
of
the
documentation.
You
can
report
issues
and
submit
pull
requests.
You
can
ask
questions
and
answer
questions
as
well.
We
are
inclusive
and
open
source
community,
so
we
invite
you
to
do
anything
and
everything
that
assists
with
others
in
the
community.
A
We
also
invite
feedback.
So
certainly,
as
patrick
says,
we
we
love
good
feedback,
but
we
want
to
hear
the
constructive
feedback
as
well.
Are
you
looking
for
something
specific
that
you
feel
would
help
the
community?
Any
documentation
needs
anything
that
you
feel
might
need
some
additional
assistance
and
we
certainly
want
to
hear
what
you'd
like
to
share
with
the
community.
How
do
you
get
involved?
A
Well,
we
have
a
plethora
of
links.
First
is
the
developer
videos
and
the
community
videos
you
can
access
those
by
going
to
the
ak
dot,
msm,
365,
dev,
youtube
or
aka
dot.
Ms
forward
slash,
m365
pnp
forward
slash
videos:
these
are
a
collection
of
videos
from
microsoft
and
the
community
that
are
going
to
assist
you
in
learning
more
about
all
of
the
microsoft
365
technologies
and
it's
a
little
more
fun
and
interactive
for
you
to
be
able
to
watch
it
by
video.
So
please
don't
hesitate
to
enjoy
those
videos.
A
We
also
have
a
number
of
open
source
repositories:
github.com
sharepoint,
github.compnp,
officedev,
microsoft
graph.
So
we
invite
everyone
to
visit
those
and
utilize
the
benefits
that
are
available
to
you.
If
you're
looking
to
learn
more
contribute
understand
how
certain
things
work
within
the
microsoft
365
ecosystem,
we
have
a
ton
of
sample
galleries,
team
samples,
spfx
samples,
power
platform,
samples,
xbfx
extensions
list,
formatting.
Oh
my
don't
hesitate
to
go
to
any
one
of
these
repos
and
sample
galleries.
A
They
are
there
for
you
to
utilize
within
your
organization.
Use
to
learn,
contribute
back
upgrade.
We
invite
any
and
all
poll
requests.
So
please
don't
hesitate
to
take
advantage
of
those
that
are
available
to
you.
Everything
rolls
up
to
the
open
source
initiative
and
samples
via
the
aka
dot.
Ms
forward
slash,
m365
pnp
link
so
visit
that
there
you
can
take
advantage
of
all
of
the
resources
and
tools
available
to
you
under
the
microsoft
365
patents
and
practices
community
umbrella.
A
We
love
our
community
calls,
but
of
course
we
know
that
at
this
time
is
good
as
a
summer
break
for
those
in
the
community.
So
for
the
rest
of
this
month
in
august,
we
will
be
taking
off
the
monthly
calls
during
that
process.
Those
calls
are
going
to
be
transferred
into
weekly
tuesday
calls
that's
it
did
you
want
to
communicate
to
this?
One
specifically,
I
know
this
is
typically
your
area
yeah.
B
So
so,
basically,
what
we're
doing
here
is
that,
like,
like
david
said,
we
want
to
cancel
the
community.
The
monthly
community
calls
are
now
on
a
summer
break
because
we
want
to
give
people
slightly
more
time
on
the
summer,
also
including
presenters,
and
not
just
to
attend
these
and
anyway,
the
attendance
is
clearly
is
lower
or
summertime,
and
then
what
we
wanted
to
do
is
get
a
holistic
microsoft.
Resistive
platform
call
so
rather
than
making
you
choose
between,
is
it
a
team
city
sharepoint?
Is
it
a
craft?
B
Call
we're
going
to
introduce
this
generic
call,
which
is
basically
for
all
of
those
things
together,
and
it's
split
between
the
demos
on
those
different
topics.
So,
basically,
after
the
summer,
we're
moving
to
this
mode,
starting
from
31st
of
august,
where
we
have
a
engineering
call
on
tuesdays
and
community
touring
call
on
thursdays.
So
that's
kind
of
how
we
are
thinking
this,
then
some
of
the
old
monthly
community
goals
will
still
remain
independent
because
they
choose
to
do
so,
at
least
for
now,
but
tuesday,
thursday,
consistently
every
single.
A
Week
all
right
excellent,
thank
you
visit
and
that
tuesday
call
is
available
as
a
download
ics
file
already.
So,
if
you
go
to
the
aka
dot,
ms4
m365
pnp
you'll
be
able
to
see
the
community
calls
that
tuesday
is
already
listed.
You
can
download
the
ics
and
get
it
on
your
calendar
so
that
you
can
make
sure
that
you're
able
to
join
us
each
and
every
week
as
an
open
source
community.
A
We
cover
topics
from
first
time
contributor,
community
docs,
using
spf
x
samples
being
a
first-time
presenter
maturity
model.
We
also
have
one
of
the
more
popular
sessions.
That's
been
taking
place.
Monthly
are
ask
me
anythings.
We
just
had
our
team's
development
earlier
this
week,
which
is
fantastic.
It
gives
you
a
personal
and
upfront
opportunity
to
ask
questions
of
the
experts
that
cover
these
these
initiatives
within
pnp
and
within
microsoft.
We've
got
coming
up
in
september,
a
power
platform
session
that
you
can
register
for
now.
A
A
A
So
when
you
register
for
this
program-
and
we
need
you
to
register
so
that
we
can
align-
who
you
are
with
your
contributions,
we
are
going
to
be
able
to
start
celebrating
you
in
a
more
formal
and
official
way
with
these
badges,
so
we're
excited
for
it
again
we're
starting
to
process
those
june
contributions.
Now
so
you're
going
to
start
seeing
some
some
of
those
come
out
via
email.
Please,
please,
please
aka
dot,
ms4
m365
pnp
dash
recognition.
A
We
could
not
be
more
excited,
there's
going
to
be
initiatives
and
campaigns
coming
up
limited
edition,
badges,
special
parker,
badges,
all
kinds
of
fun
for
us
to
get
more
involved
and
collaborate
together
in
the
community,
and
we
want
to
celebrate
and
recognize
all
the
hard
work
you
all
do,
because
it
is
fantastic.
So
please
don't
hesitate
to
register
for
that
all
right.
Let's
talk
about
the
sharepoint
framework
latest
from
sharepoint
engineering.
This,
I
believe
you
will
cover
this
yep.
B
Yeah
absolutely
so
one
thing
which
we
announced
yesterday
was
it
yesterday.
Today
is
thursday.
It
was
yesterday.
Yes,
it
was
west
today,
so
we
pump
past
the
blog
post
related
on
the
inspire
which
is
happening
this
week.
Inspire
is
our
global
partner
conference
and,
as
part
of
those
announcements,
we
announced
the
upcoming
viva
connections,
public
developer
preview.
So
in
build
2021
in
may,
we
announced
a
private
preview
where
you
needed
to
sign
up
for
getting
access
on
the
viva
connections,
developer
areas
and
and
functionalities,
as
that
was
insanely
insanely
popular.
B
So
we
had
more
than
600
people
signing
up
on
that
phone.
We
basically
are
forced
to
switch
to
this
public
developer
preview
model
so
that
we
can
actually
give
access
on
all
of
the
people,
these
goodies
and
and
capabilities
of
building
things.
The
developer
preview
will
be
part
of
a
sharepoint
framework,
1.13
data
release.
So
this
is
a
preview
which
is
basically
means
a
beta,
not
production,
radian
and
1.13
beta
is
coming
out
as
well.
So
it's
basically
bundled
on
the
same
thing,
and
this
is
going
to
be
happening
within.
B
B
I
think
that's
safe
to
say
and
other
areas
where
we
are
investing
is
that
microsoft
teams
development
improvements,
because
we
consider
the
baseline
of
sharepoint
framework
for
the
portals
and
pages
and
the
sharepoint
sign
should
be
pretty
well
covered,
so
we're
kind
of
investing
also
on
the
microsoft
team
site.
So
you
can
more
easily
reuse
the
same
skills
and
tooling,
not
only
in
sharepoint,
not
only
in
microsoft,
viva
connections,
but
also
in
microsoft
teams
and
then
we're
looking
into
doing
a
significant
revamp
on
the
supportability
model.
B
What
I
mean
with
that
one
is
that
have
much
more
active
engagement
with
the
community
and
forums
and
all
of
that
stuff
starting
this
autumn.
So
all
of
that
is
in
the
pipeline
and,
of
course
not
forgetting
about
the
store
modernization,
so
sharepoint
store
has
not
given
that
much
investments
within
the
past
years,
but
we're
going
to
do
a
full
modernization
of
the
store
pretty
soon.
B
Actually,
within
upcoming
weeks,
you
should
be
starting
to
see
an
updated
store
in
the
targeted
release,
tenants
and
then
gradually
we
will
roll
out
additional
store
functionality,
improvements
related
on
sharepoint
as
well.
All
of
this
is
basically
gradually
crawling
out
throughout
the
autumn
this
calendar
year.
So
a
lot
of
a
lot
of
investments,
a
lot
of
people
working
behind
the
scenes,
tens
and
dancing
of
people
making
things
now
better,
which
is
really
really
good,
and
also
please
remember,
to
keep
the
feedback
coming.
We
need
to
understand,
what's
needed,
to
make
your
life
successful.
A
C
C
We
have
been
focusing
mostly
on
v3,
so
we're
deep
in
the
reworking
of
some
of
those
new
features
for
v3.
If
you
are
interested
in
learning
more,
there
is
a
v3
branch,
I
it
still
says
but
ugly,
and
it
is
a
little
bit
ugly
still,
but
you
can
definitely
peek
in
and
see
what
work
we
have
going
on
going
and
sort
of
get
a
preview
of
what
might
be
coming.
C
If
you
want
to
know
the
list
of
objectives,
we
have
there's
a
pinned
issue
issued
1636
in
the
repo
that
has
a
listing
of
all
our
plans
with
links
to
discussion
areas
so
that
you
can
review
all
the
ideas
that
we
have
for
v3
and
also,
if
you
are
interested
in
helping
with
v3.
Let
us
know
we
are
getting
very
close
to
being
able
to
open
up
so
that
other
people
can
contribute
to
v3
to
to
get
it
across
the
finish
line,
and
hopefully
that
will
happen
soon.
C
I
just
want
to
reiterate
that
we
did
implement
a
new
github
action
to
lock
closed
issues.
The
idea
behind
that
is
that
if
you
have
a
related
issue,
we'd
love
to
see
you
open
a
new
issue
and
then
reference
that
closed
issue,
so
that
we
can
keep
them
unique
and
keep
all
the
issues
needing
feedback
right
up
at
the
top
of
the
list
and
also
don't
forget
to
follow
us
m365pmpjs
on
twitter
and,
like
I
said
it,
direct
all
your
feedback
to
that
issues
list.
C
A
A
Well,
there's
a
new
preview
3.12,
it's
coming
with
retrieving
onedrive
sites,
retrieving
planner
plans
and
buckets,
adding
planner
buckets
and
extended
retrieving
sites
with
info
about
groups.
You
can
always
try
the
latest
beta
using
the
npm
install
at
next
and
you
can
run
it
in
docker.
We've
seen
lately
that's
available
natively
in
the
azure
cloud,
shell
and
you
can
also
try
preview
v4.
So
this
gives
you
an
opportunity
to
prepare
for
new
versions
coming
soon.
It
gets
you
excited
and
involved
so
you're
ready
to
share
it
with
others
and
utilize
it
in
your
organization.
A
A
A
We've
seen
a
lot
of
that
lately,
that's
been
very
popular
people,
picker
list,
picker,
various
fixes
and
enhancements
and,
of
course,
the
property
controls,
the
the
sibling
of
that
for
our
property
controls,
2.7.0
covering
spfx1.11
and
3.2.0,
covering
spfx
1.12.1
with
fast
serve
support
again,
and
a
number
of
various
fixes
a
whole
lot
of
contributions
here
by
everyone.
That
is
contributing.
Thank
you
all.
We
appreciate
all
of
that.
Please
don't
hesitate
to
keep
contributing.
We
really
appreciate
all
of
that.
You
can
get
more
information
at
the
github
links
below
or
twitter
m365
pnp
controls.
A
Next
up
is
pnp
modern
search,
you're
able
to
build
modern
search
experiences
flexible
web
parts.
We
know
this
is
one
of
our
favorites
v4.3.0
is
a
july
release.
It's
got
dutch
translation,
a
proper
fix
for
custom
helpers,
web
components
across
the
web
parts
and
a
persona
card
fix,
and
then
we
also
see
the
release
of
3.21.0
fixes
paging
vertical
synonyms,
previews,
and
so
please
take
advantage.
This
is
one
of
the
coolest
collection
of
web
parts
in
the
pnp
family.
D
Thank
you.
So
if
you're
starting
a
new
development
task
with
spfx,
you
could
obviously
build
everything
from
scratch
on
your
own
or
you
could
leverage
the
awesome
samples
that
were
built
by
the
community.
So
we
have
two
github
repositories:
the
spfx
webparts
and
the
spfx
extensions,
where
you
can
find
samples
that
are
contributed
by
the
community
and
they're,
ranging
from
just
simple
concepts
like
how
do
I
use
a
one
of
those
pnp
controls
for
example,
or
full
solutions
and
utilities.
D
D
It
allows
you
to
actually
receive
notifications
from
selected
lists
and
libraries,
and
then
we
have
an
update
to
the
the
analytics
web
part
which
supports
google
analytics
v4
by
joao
ferreira.
So
those
are
on
the
extension
side.
On
the
web
part
side,
we
have
an
update
to
the
calendar
by
mohamed
amir,
who
fixes
basically
something
that
will
disable
the
ability
to
edit
recurrence
series.
D
If
the
user
doesn't
have
access
to
it,
we
have
a
new
tiles
web
part
by
omar
l
anis,
which
allows
you
to
actually
create
these
cool
tiles
web
parts,
and
you
can
fully
customize
that
the
membership
updater
by
nick
brown
has
been
updated
by
to
spfx1121
and
then
arigunawan
updated
the
facebook
page
social
plugin
to
uspfx121
as
well.
We
have
a
new
hero
web
part
by
omar
l
ennis,
which
allows
you
to
actually
create
these
cool
hero.
D
Web
parts
like
the
out
of
the
box
web
part,
but
customizable,
and
then
we
have
an
update
to
the
page
contributors
by
ari
gunawan
who
updated
it
to
spf
x,
112
1..
Finally,
we
have
a
private
library,
folder
manager
web
part
that
allows
you
to
actually
collaborate
with
people
and
create
separate
sections
where
you
can
actually
create
private
folders,
and
things
like
that.
It's
amazing
to
see
the
number
of
updates
that
we
have
that
are
now
using
spf
x121.
D
It
definitely
makes
it
easy
for
anyone
new
to
the
community
who
wants
to
get
started
with
the
samples,
because
they
can
just
download
the
latest
version
of
x
and
the
the
proper
version
of
node
and
get
started
quickly.
Thanks
everyone
for
your
contributions,
I
look
forward
to
seeing
more
contribution
back
to
you,
not
patrick.
A
B
I
I
can
do
that,
so
let
me
actually
share
my
screen
and
want
to
get
a
mode
come
on.
You
can
do
that
and
starting
and
I
think,
we'll
discuss
a
fine
format
now,
let's
wait
for
the
seats
to
fill
in,
I'm
already
recording
and
we
still
have
few
free
seats
on
the
table
bill
that
that's
actually
really
good.
You
look
like
the
one
drawing,
so
that's.
That's
really
really
good.
So.
B
Yeah,
oh
that's
true
home
alone,
as
well
cool.
I
think
we
are
full.
Is
that
the
50?
I
guess
we're
not
getting
any
more
people.
So
let's
do
some
hands
waving
everybody.
So
thank
you
for
joining.
Hopefully,
by
end
of
this
year,
we
will
actually
meet
each
other
physically.
That
would
be
awesome
done,
we'll
see
how
it
goes
if
nothing
else
we'll
keep
on
having
our
community
live
online
as
well.
Thank
you.
Everybody
cheers
cool.
A
A
E
We
both
work
at
some
praxis,
consulting
in
boston,
and
so
the
first
question
really
is:
why
did
we
go
ahead
and
build
this
and
the
the
story
here
is:
we've
all
sort
of
seen
this
over
the
last
year
and
a
half
through
covid
that
you
know
that
you
know
folks
are
asking
for
information
when
you
go
to
the
doctor's
office
or
when
you
go,
you
know
to
drop
your
kid
off
at
school,
or
what
have
you
and
they're
asking
questions
about
you
know.
Have
you
been
exposed?
E
What
is
your
potential
risk
profile
so
as
as
companies
and
countries
are
starting
to
open
their
offices
back
up,
we
wanted
to
provide
a
way
through
teams
to
allow
that
to
to
happen.
We
wanted
to
be
able
to
track
who's
in
the
office
at
any
given
time,
and
we
also
wanted
to
provide
a
way
for
administrators
or
hr
folks
or
human
resources,
folks
to
notify
people
if
they've
potentially
been
exposed.
So
it's
that
contact
tracing
piece.
E
So
what
we
did
was
we
built
a
team's
personal,
app
that
sits
inside
on
the
rail
and
if
it's
not
there
by
default,
you
can
just
go
in
and
click
the
button.
Now
for
your
every
you
know
your
average
user
they're
going
to
log
in
and
they'll
only
see,
self-check-in
and
we've
created
these
questions,
so
they
can
come
in
and
they
can
select
say
what
office
they're
in
you
know.
We've
got
japan,
we've
got
boston,
so
you
know
they
say
whether
or
not
they've
had
a
fever.
What
is
their
temperature?
E
These
are
all
configurable
and
I'll.
Show
that
in
a
couple
of
minutes,
sort
of
generic
coveted,
related
symptom
questions
and
then,
when
they're
done,
they
save
the
response
and
they
can
submit
this
once
a
day
and
at
this
point
their
job
is
done.
This
person
is,
is
at
home,
they're,
getting
ready
to
go
into
the
office,
so
they
fill
out
the
form
and
when
they're
done,
they
click
submit
and
then
they're
on
their
way
they
can
go
to
the
office.
E
Now.
For
me,
I'm
at
the
front
desk
and
I
can
see
whoever
is
in
the
office.
I
can
see
all
the
folks
here
that
have
checked
in
or
in
the
process
of
checking
it.
So
we
built
this
dashboard.
It
lets
you
flick
through
the
different
dates,
so
you
can
see
the
different
people's
names
on
the
left.
You
can
see
what
office
that
they've
decided
to
check
into.
E
So
you
can
see
thor
ironsides
has
is
the
person
that
just
checked
in
he
hasn't
checked
in
yet
so
he
came
to
the
office.
I'm
going
to
check
him
in
I'm
going
to
review
all
of
these
details
with
him.
What
he
submitted
in
that
form.
There's
no
real
personal
information
in
here,
so
we
didn't
sort
of
you
know,
there's
not
really
hipaa
or
in
the
us
requirements
there.
So
the
front
desk
person
can
just
go
ahead
and
check
them
in
and
say.
Okay,
these
all
look
good.
E
And
then
they
can
check
the
user
into
the
office,
and
at
this
point
now
it's
assumed
that
they,
you
know,
go
to
their
office,
go
to
their
meeting
whatever
it
is.
They
have
to
do
so
because
they're
at
the
front
desk,
the
front
desk
person
also
has
the
ability
to
check
in
themselves,
but
they
also
have
the
ability
to
check
in
a
guest
so
say:
there's
a
guest
here
to
see
thor.
E
E
Person
now
one
thing
that's
a
little
bit
different
is
that,
because
this
is
a
guest
user
and
I
just
ran
through
this
verbally
with
the
guest
user,
we
check
them
in
automatically.
So
there's
no,
you
know,
there's
no
question
because
we
just
ran
through
it.
We
don't
need
to
double
check
everything
with
them.
The
other
thing
that
you'll
notice
is
that
in
the
icons
on
the
left
hand
side,
if
any
of
these
people
were
online,
their
presence
would
be
notified
here.
So
they
would
have
the
you
know.
E
So
that's
the
that's
the
experience
for,
say
the
front
desk
person,
but
now
what?
If
you
are
an
hr
person
and
you
need
to
notify
potential
employees
of
a
of
a
possible
exposure
by
default.
This
shows
the
past.
You
know
two
weeks,
there's
search
capabilities
that
lets.
You
filter
this
down
to
a
specific
set
of
days
and
you
can
search
by
days
you
can
search
by
hour,
I
mean
by
office.
So
you
can
check.
E
E
E
C
C
So
we
went
ahead
and
built
an
ace
for
the
covid
app,
and
so
we
can
see
here
that
it.
The
ace,
is
on
the
dashboard
and
I
have
a
check
in
button
that
gives
me
that
form.
So
I
can
go
through
as
a
user
and
fill
out
my
form
and
then
just
go
ahead
and
submit
it,
and
so
that's
a
really
quick
way
that
I
can
get
right
to
the
form
from
my
dashboard
that
could
be
in
the
mobile
experience
or
whatever,
and
then
the
that
the
configuration
itself
has
me
pointing.
C
I
have
one
configuration
to
point
to
the
site
collection
where
my
lists
are
stored.
So
that's
how
that
ace
gets
set
up
and
then
further
when
you
click
on
the
ace
itself,
it
deep
links
into
teams
and
takes
us
right
to
that
covid
app
in
the
private,
app
that
loads
in
teams.
So
I
can
get
there
and
you
can
see
that
I
submitted
my
entry
in
and
I'm
good
to
go.
C
So,
let's
that's
a
you
know,
it's
a
quick,
easy
extension,
but
let's
look
at
the
code
a
little
bit
because
I
think
that's
more
interesting
for
people
to
see.
So
let
me
bring
up
my
code
now
there
we
go
okay,
so
this
adaptive
card
extension
is
another
addition
to
the
the
whole
solution
package
that
we
built.
So
when
we,
when
we
create
the
solution,
originally
we
had
the
web
parts
for
the
covid
app
that
you
saw
and
that
covet
admin
app.
C
C
C
So
we
go
through
a
knit
process
and
we
have
some
things
to
decide
like
the
home
site,
because
the
personal
app
is
doesn't
have
a
home.
It's
not
like
a
teams
tab
where
the
the
home
for
the
solution
is
in
the
team,
the
sharepoint
site,
where
the
team
is
this,
the
personal
app
sort
of
floats
without
a
home.
So
we
needed
to
tell
the
covid
ace
where
its
home
is
so
that
it,
the
so
pmp.js
which
is
what
I'm
using
to
go.
C
Get
the
data
from
the
list
knows
where
to
get
that
data,
so
I'm
pointing
to
where
that
home
is.
So
that's
one
of
the
things,
the
configurations
of
the
ace
and
then
we're
registering
the
card
in
the
quickview
which
I'm
going
to
go
up,
we're
initializing
pmp.js,
and
then
we
have
some
setup.
We
need
to
know
who
the
user
is
and
what
their
display
name
is
and
checking
whether
that
user
is
already
checked
in
for
today.
We
need
to
do
that
and
initializing
our
service
and
then
setting
up
our
state.
C
So
our
state
for
the
entire
ace
so
react
has
this
concept
of
state
and
the
ace
has
a
similar
concept
of
state.
So
the
the
entire
ace
has
a
state
and
we're
going
to
set
up
whether
the
user
can
check
in
or
not.
We've
determined
that
what
the
user's
id
is
and
what
their
display
name
is,
and
now
we
can
share
that
with
the
quick
view
and
the
card
view.
C
So
the
card
view
is
the
first
thing
that
we
load,
and
that
was
the
card
on
the
main
screen.
It's
super
simple:
it
has
a
title
and
a
description,
there's
not
a
ton
to
it
and
so
we're
just
using
the
primary
text
card
view.
There's
three
different
views
for
the
card
view:
one's
an
image
view,
one's
a
primary
text,
view
and
one's
this
basic
basic
view,
and
so
we're
just
saying:
okay,
we're
gonna
set
up
the
card
and
here's
the
data
for
the
card,
so
this
function
runs
and
it
sets
up
the
data.
C
So
all
we're
doing
is
checking.
Has
the
user
checked
in
already
and
did
the
service
initialized
properly?
Assuming
that
the
user
can
check
in
it'll
show
a
string
of
text
that
says:
hey
you
can
check
in
and
if
they've
already
checked
in,
then
it's
just
going
to
show
that
they've
already
checked
in
and
that
they
can't
do
anything
and
that
will
determine
whether
or
not
that
check
in
button
shows
at
the
bottom.
But
the
card
will
always
deep
link,
and
so
that's
what
this
last
function
here
is.
C
The
on
card
selection
sets
up
an
external
link
and
that
external
link
is
a
deep
link
in
the
teams
to
the
entity
that
this
is
so
that
number
right
there
that
good
right.
There
is
the
guide
for
the
web
part
and
you
can
find
that
down
in
the
the
web
parts
manifest.
So
if
you
look
in
the
web
parts
manifest
that
id
is
the
id
for
that
deep
link.
C
So
let
me
shut
that
one
second
come
back.
So
that's
where
that
deep
link
url
comes
from
okay.
So
that's
how
the
card
view
gets
rendered
so
assuming
that
the
user
can
then
check
in
they
have
that
button
and
we've
registered
that
we
have
a
quick
view
and
the
quick
view
is
where
we
can
be
a
little
more
dynamic
and
have
a
little
bit
more
control
of
what
things
look
like.
C
So
in
this
case
we're
going
to
build
the
quick
view-
and
let
me
just
close
this,
so
we
can
have
a
little
more
space
and
actually,
let
me
close
this,
so
we
have
a
little
more
space.
So
the
quick
view
is
where
we
got
the
questions,
and
so
now,
if
you
recall
the
questions
are
dynamic.
We
have
a
list
of
questions
so
they're
dynamically
driven
and
they
can
be
changed
at
any
time.
C
So
we
want
to
be
able
to
dynamically,
create
that
quick
view
which
isn't
necessarily
super
intuitive,
because
the
way
the
quick
view
normally
works
is
you
have
a
template
and
you
have
the
data
and
the
two
merge
together
and
they
display
the
quickview.
And
if
you
know
what
the
template's
going
to
be,
then
in
the
quickview
template
json
file,
you
can
build
the
template.
Putting
in
markers
for
where
your
data
should
merge
in
and
you're
all
done,
the
problem
with
this
particular
quick
view
is
that
those
questions
are
dynamic.
C
We
don't
know
how
many
there
are.
So
we
don't
know
how
many
spots
to
save
for
questions,
and
we
don't
know
what
type
of
question
is
it
a
text
question?
Is
it
a
yes?
No
question,
we
didn't
didn't
really
know,
that's
all
dynamic.
So
the
way
we
went
about
solving
this
problem
is
by
creating
a
baseline
template.
So
you
can
see
in
here
that
I
have
that
the
json
string
or
the
quickview
ace
card
template.
It
has
a
body
section
that
that
has
a
sort
of
a
header.
C
Then
it
has
a
text
block
for
the
office.
We
knew
it
was
going
to
have
office.
That
was
going
to
be
one
of
the
fixed
things,
so
I
have
a
text
block
for
the
office
and
then
for
the
office
string.
The
the
label
office
excuse
me
and
then
I
have
an
input
for
the
choices
for
the
different
offices.
Those
are
dynamic,
so
we
wanted
to
set
up
a
structure
to
be
able
to
inject
those
choices
into
the
the
template.
C
C
It
has
an
items
array,
that's
just
empty
at
the
moment,
but
we'll
get
to
that
and
then
last
but
not
least,
we
have
the
action
set,
which
has
the
submit
button
and
the
cancel
button
and
we
can
handle
those
as
well
and
I'll
show
you
that
in
a
minute,
so
the
only
other
thing
I
want
to
point
out
is
that
we
have
this
body,
it's
an
array
and
it
has
a
number
items
in
it.
So
the
zeroth
place
item
is
this.
The
first
place
item
is
this.
C
The
second
place
item
is
that
I
I'm
pointing
it
out
because
we're
going
to
use
that
information
when
we
come
back
to
the
quickview.
So,
let's
go
back
to
the
quick
view
and
we've
set
up
some
data.
Some
some
excuse
me
types
up
at
the
top,
let's
get
into
the
meat
of
it.
So
we
have
the
data
section
here
where
we're
going
to
create
the
data
that
is
going
to
be
merged
into
the
template,
I'm
going
to
skip
that
for
a
minute
and
come
down
to
the
template.
C
So
normally
what
we
would
just
do
is
we'd
say:
hey.
My
template
is
in
this
file
and
I
just
want
to
return
the
template,
so
we
we'd
literally
do
line
72
and
then
we
do
line
94
and
that
would
be
all
you'd
need
to
do,
because
your
template
would
be
configured
already
to
have
all
the
placeholders
for
all
the
data
that
you're
going
to
push
into
it.
C
In
our
instance,
we
need
to
dynamically
change
that
template
on
the
fly,
so
we're
going
to
load
the
template
in,
but
then
we're
going
to
modify
that
template
as
we
go
along.
So
in
the
in
the
zeroth
placeholder
of
that
body
array.
Remember,
I
pointed
out
that
the
body
has
a
bunch
of
objects
in
that
array.
C
I'm
going
to
set
a
display
name
for
the
quick
view
and
then
I'm
going
to
get
all
the
locations
out
of
our
service,
I'm
going
to
load
those
into
the
location
options
and
so
that
that
can
be
pushed
into
the
template.
For
so
we
have
the
the
first
one,
which
is
the
label
for
the
office.
So
I'm
just
gonna
have
a
string
that
defines
that
label
that
I
want
for
the
office
and
then
the
second
option
item
in
there
was
the
choice
list
for
the
locations.
C
So
I'm
going
to
set
the
choices
to
those
location
options
that
I
loaded
from
the
service
which
loads
them
from
the
sharepoint
list,
and
I'm
also
going
to
say
the
value
of
that
is
this
location
value
for
that's
the
the
label
for
the
data
label.
That's
going
to
merge
into
that,
and
then
I
need
to
build
the
questions
array,
and
so
those
are
going
to
go
into
that
items
which
was
the
third
or
fourth,
depending
on
how
you,
if
you're,
zero,
counting
or
not.
I
tend
to
zero
count.
C
And
if
we
go
to
the
definition
of
that,
you
can
see
that
I
knew
what
I
needed
for
the
values
for
that.
Based
on
what
the
template
needed
to
look
like
the
json
object
for
a
checkbox
needed
to
have
these
values
in
it.
So
I
built
a
constructor
that
allowed
me
to
do
that.
So
then,
all
I
have
to
do
is
say
push
a
new.
Yes,
no
answer
and
I'm
going
to
pass
in
the
questions
id
the
title
and
the
data
placeholder
for
that
question.
C
For
the
yes,
no
and
the
text
box
has
two
pieces
to
it,
so
I
needed
to
push
on
the
text
box
that
has
the
label
and
then
the
text
box.
That
is
the
answer
field
below
it
and
again
I'm
putting
on
for
that
text
box.
With
the
answer.
I
need
to
point
out
where
the
data
is
what's
the
merging
point
and
what
the
id
is
for
the
question
because
I'll
need
that
later
and
then,
as
I
said,
I
push
that
into
the
template.
So
now,
at
this
point
on
line
90,
my
template
is
now
complete.
C
I
dynamically
altered
it
in
memory
so
that
it
would
have
the
questions
that
I
needed
and
that
quick
view
would
look
the
way.
I
need
it
to
look
so
now,
when
I
return
my
template,
it's
all
modified
the
way
I
need
to,
and
now
the
solution
merges
that
template
with
the
data.
So
what
I
needed
for
the
data
is
to
get
answers.
So
I
have
all
my
questions.
C
I
needed
to
set
all
my
answers
to
blank
so
that
they
didn't
have
any
answers,
so
people
could
finish
filling
it
out
right
and
then
I
return
the
answers
and
then
the
solution
merges
the
data,
I.e
the
blank
values
with
the
template
and
displays
that
quick
view
on
the
screen
for
the
user
to
fill
out.
Now,
if
you
recall
at
the
bottom,
we
had
a
submit
button
and
a
cancel
button,
and
so
the
way
we
handle
that
is
with
a
feature
called
on
action
and
so
on.
C
Action
means
when
you
click
one
of
those
buttons
it
launches
this
function.
This
function,
then
I
can
say:
okay
did
they
hit
submit.
If
they
did,
then
I'm
going
to
go.
Look
at
the
data
and
I'm
going
to
create
an
entry
that
I'm
going
to
use
our
service
to
submit
their
answer
all
their
answers
into
a
new
line
item
in
the
self-check-in
list
in
the
root
site
collection.
C
It's
super
right
in
front
of
the
user
now
granted,
if
they're
in
teams
at
home
or
teams
on
their
mobile
phone
they'll
be
able
to
get
to
the
covet
app
that
way
as
well,
but
this
might
be
the
place
that
they
start
their
day
once
once
these
things
start
gaining
and
once
people
start
implementing
these,
the
new
viva
desktop,
which
was
the
the
new
name
for
the
home
site,
personal
app.
They
might
start
there
instead
and
so
to
be
able
to
have
that
card
and
go
oh
right.
Yeah.
C
I
gotta
check
in
today
and
have
that
right,
front
and
center
makes
their
day
go
a
little
faster
right
and
that's
what
we
want
to
have,
instead
of
them
having
to
click
all
around,
remember
to
do
all
those
things
it
becomes
front
and
center.
So
that
is
an
overview
of
how
the
ace
was
built.
Vesa
did
you
have
any
comments
you
wanted?
Did
I
miss
anything
yeah.
B
Can
we
go
back
on
to
ace
just
on
the
ux
of
the
ace,
just
to
recap
what
we
saw
in
the
code
and
coming
back
on
so
what
we
saw
in
the
code?
This
is
how
it
looks
like
so
just
to
be
clear,
so
1.13
sharepoint
framework
1.13
and
which
is
going
to
be
released
within
a
week
when
we
are
recording
this
community
call
for
those
who
are
watching
the
video
recording,
that's
the
one
which
will
include
then
the
support
for
creating
these
cards
and
these
cards
are
designed
for
more
primarily
mobile.
B
C
B
C
E
I've
been
answering
some
of
the
ones
in
the
chat.
One
thing
I
just
want
to
point
out
is:
we
are
going
to
be
releasing
this
as
a
sample
for
folks
to
see
how
we
did
this
and
that
you
can,
when
we
release
that
you
can
also
just
download
the
sppkg
file
and
it
will
provision
itself
with
sample
data,
so
you
can
just
you,
can
get
it
up
and
running
in
like
five
minutes.
C
And
you
want
to
see,
you
can
just
go
download
the
sppkg,
which
is
pre-built
and
in
the
deployment
folder
upload
in
into
your
tenant,
app
catalog,
get
it
provisioned,
sync
to
team,
so
that
it's
in
your
teams
in
the
personal
app
on
the
left-hand
rail
and
then
you
know,
go
ahead
and
as
soon
as
you
run
it
the
first
time
it
will.
If
you
have,
it,
will
configure
itself
it'll,
give
you
an
option
to
configure
itself
with
default
demo
data
or
you
can
start
from
scratch
either
way.
So
that's
a
really
good
point.
B
Cool
excellent,
thank
you
derek
thank
you,
julie,
really
awesome
stuff
and
it
it
likes
that
the
sample
will
be
available
as
part
of
the
1.13
beta
release.
So
you'll
get
access
technically
it's
available
already
in
the
github,
but
you
can't
actually
run
npm
install
because
the
1.13
is
not
yet
out.
So
julian
derek
has
been
bothered
to
private
preview,
so
they
have
been
having
access
on
the
bits.
C
Sppkg
file,
so
that
you
could,
you
can
install,
even
if
you
don't
have
the
preview
bits
like
messages
said,
and
even
if
you
don't
you
weren't
in
the
preview
program,
and
you
don't
have
the
dashboard,
you
can
still
download
the
sppkg
file,
install
it
in
your
tenant
and
you'll.
Get
the
teams
app.
You
just
won't
be
able
to
put
the
ace.
Even
though
it's
in
the
package,
you
won't
be
able
to
put
it
anywhere
in
your
tenant,
because
you
don't
have
the
bits
to
be
able
to
create
a
dashboard
to
put
it
on
there.
B
Until
we
as
a
microsoft
site,
release
those
functionalities
so
but
we're
getting
there
one
step
at
a
time
now
we
have
12
minutes,
so
I'm
going
to
take
roughly
10
minutes
and
to
quickly
do
a
kind
of
a
quick
introduction
on
the
team's
toolkit
v2
and
concentrating
on
the
sharepoint
framework
side
of
the
house.
So
let's
talk
about
this
one
team's
toolkit
version
2
is
in
previous
status
and
it
actually
supports
creation
of
the
ux
layer,
especially
tabs,
using
sharepoint
framework.
B
Now
we
are
working
together
with
teams
engineering
and
we
saw
studio
developer
division
and
for
the
with
the
tools
people
and
to
make
this
experience
more
optimal.
So
right
now
what
you're
seeing
today
is
quite
limited,
but
I
also
want
to
get
the
feedback
in
the
chat
on
what
you
would
like
to
see
and
and
how
things
are
looking.
And
hopefully
we
will
get
people
interested
on
testing
this
as
well.
B
So
you
can
actually
report
ideas
and
input
and
feedback
for
the
the
visual
studio
organization
as
well
now
as
before,
we
go
to
the
the
actual
demo
and
how
it
actually
works.
I
just
re
briefly
briefly:
gonna
take
two
minutes
to
talk
about
the
opportunity
and
why
we
are
doing
this.
So
of
course
we
have
145
million
daily
active
users
in
the
microsoft
teams.
We
have
more
than
200
million
monthly
active
users
in
sharepoint,
and
we
have
more
than
tens
of
millions
of
monthly
active
users
in
sharepoint
using
sharepoint
framework.
B
So
there's
tens
of
millions
of
people
who
are
using
already
spfx
sharepoint
framework
components
in
sharepoint
so
and
people
are
writing
tens
of
thousands
of
components
in
every
single
month,
so
we're
seeing
a
massive
massive
usage
on
sharepoint
framework,
and
so
people
want
to
write
components
using
sharepoint
framework.
So
why
wouldn't
we
then
extend
the
sharepoint
framework
to
be
the
extensibility
model
for
microsoft
themes,
as
you
saw
within
the
previous
demos
and
during
the
community
demos.
B
There
are
a
lot
of
capabilities
what
you
can
build
already
with
spfx
and
now
we're
improving
that
with
the
themes
toolkit
v2
and
looking
into
further
improvements
in
the
future
as
well.
Now,
just
a
quick
recap
on
the
sharepoint
framework.
Of
course,
a
lot
of
the
people
in
the
school
are
familiar
with
this
one,
but
it
is
really
the
easiest
way
to
build
your
enterprise
solutions
in
microsoft,
e65
and
it
has
automatic
single
sign-on
automatic
hosting.
B
You
don't
have
to
worry
about
anything
the
hosting
is
done
by
sharepoint,
even
though
you
would
be
actually
using
it
in
microsoft
teams
or
in
microsoft.
Viva.
It
has
a
consistent
dev
experience
and
it's
an
industry
standard
tooling,
it's
not
about
sharepoint
essence,
you
don't
need
to
understand,
feature
framework
or
xmls
or
jsons
or
whatever.
It's
just
web
stack
development,
typescript
and
node.
B
Now
this
is
slightly
different
experience
and
I'm
going
to
show
that
in
a
second
then
using
just
the
the
sharepoint
framework
field
and
generator
and
we're
working
with
the
visual
studio
team
to
get
it
more
integrated,
and
all
of
that
you
are
using
exactly
the
same
tooling
you're,
still
using
golovk
you're
still
using
node,
nodejs
and
all
of
them.
But
the
experience
is
a
bit
different
because
we
are
creating
the
project
for
much
different.
Let's
say
location,
let's
actually
move
in
to
have
a
quick
look
on
how
this
actually
works
in
practice.
B
First
of
all,
where
can
you
actually
get
it,
so
you
can
find
it
from
the
visual
studio
marketplace?
Typically,
you
wouldn't
actually
come
to
this
page
through
a
browser.
You
would
come
to
this
page
using
the
extension
view
in
the
visual
studio
code,
but
I'm
just
going
to
call
this
out
just
in
case
in
here
and
if
you
would
have
time-
and
that
would
be
highly
highly
highly
requested,
we
would
love
to
get
more,
let's
say,
ideas
and
issues
and
reports
in
this
github
repo.
B
So
this
is
the
location
where
we
would
like
to
get
suggestions,
ideas
and
feature
requests
related
on
sharepoint
framework
in
the
microsoft
teams,
toolkit
version
2.0,
and
maybe
maybe
you
think
that
they
should
know
already,
so
I'm
not
going
to
actually
suggest
x
and
y
and
z.
Please
do
it
might
be
that
the
person
who
is
actually
focusing
on
addressing
the
issue
list
is
not
aware
of
something
what
we
discussed
it
within
the
community
goal.
So
please,
please,
please
let
people
know
what
is
needed
so
because
everything
what
we
do
in
microsoft
is
for
your.
B
B
When
that's
has
been
done,
the
latest
version
by
the
way
at
the
time
is
2.2
still
in
preview,
you'll
actually
get
the
steam's
toolkit
available
in
the
left
and
menu.
You
can
actually
configure
that
to
be
optionally
available.
All
of
that
like,
like
normally
in
visual
studio
code
and
then
from
here,
we
provide
additional
guidance
additional
point
additional
starting
points.
So,
first
of
all,
I've
already
signed
into
the
usher
and
also
already
signed
into
my
dev
tenant
or
test
tenant.
B
So
I'm
not
going
to
sign
in,
but
it's
basically
asking
you
to
sign
into
those
environments,
so
it
can
be
perform
automatic
operations,
registrations
deployments
to
make
your
life
as
easy
as
possible,
so
really
really
cool
stuff
as
well,
and
then
you
can
easily
access
documentation
guidance.
All
of
that
from
here
as
well.
So
it's
kind
of
a
making.
It's
really
easy
for
you
to
get
started
and
creating
the
project,
let's
create
a
new
project
and
see
how
it
actually
works
in
practice,
so
creating
a
new
project.
B
It's
going
to
ask
me
in
here
in
the
top
section,
let's
actually
zoom
in
a
bit
here
we
go
one
more
there.
We
go,
create
a
new
microsoft
teams,
application
or
start
from
a
sample
right
now.
We
do
not
have
sharepoint
framework
samples
available
as
a
starting
point.
Should
we
open
question,
let
us
know-
and
we
could
actually
absolutely
include
the
sample
to
be
available
from
we
do
have
a
lot
of
samples.
Like
you
know,
we
have
hundreds
and
hundreds
of
samples
available
for
sharepoint
framework.
B
Now
what
I'm
going
to
do
is
then
I'm
going
to
select
to
create
a
new
themes
app
and
I'm
going
to
choose
the
tab
because
that's
the
most
diff.
Well,
that's
the
supported,
spf
x
implementation.
Right
now
in
the
team's
toolkit,
you
can
combine
spfx
with
other
options
as
well,
which
is
kind
of
cool,
so
you
can
have
a
bot
as
a
simple
solo,
a
separate
solution
under
the
same
solution
structure.
B
So
you
can
easily
move
between
the
bot
and
the
back
end
code
like
azure
function
and
the
tab
within
the
solution
structure.
So
I'm
going
to
choose
the
tab,
I'm
going
to
choose
that
the
hosting
type
is
sharepoint
framework
technically
hosting.
Is
microsoft
365
not
really
sharepoint
framework
but
anyway?
So
german,
always
I
think,
and
because
I'm
a
web
stack
developer.
B
This
is
the
more
most
natural
way
for
me
to
implement
things
because
hey
it's
typescript
or
I
can
native
vanilla
typescript
or
it
might
be
a
react,
so
I
can
choose
whatever
the
framework
in
the
same
way
as
with
sharepoint
framework
human
generator.
I
can
choose:
is
it
a
vanilla
javascript
as
vanilla
typescript
or
is
it
the
react,
typescript
implementation?
B
So,
let's
see
I
will
select
react.
It's
going
to
ask
me
the
hello,
the
name
of
the
things.
Let's
call
this
react
call
demo,
so
we
can
identify
that.
It's
going
to
ask
me
the
description
which
the
human
generators
would
be
asking
as
well.
It's
going
to
ask
me
what
is
the
implementation
type?
Of
course
it's
typescript,
because
why
not
and
then
it's
going
to
ask
me
where
I'm
going
to
actually
store
the
code.
Let's
select
that
folder
and
it's
going
to
ask
me
the
application
name.
B
Let's
call
this
spfx
call
demo,
so
I
can
actually
show
one
more
cool
thing
I
will
press
enter
and
that
basically
is
provisioning
the
solution.
So
now
I
have
the
solution
structure
here.
I
can
basically
say
that
my
spfx
solution
is
included
in
my
solution
structure.
This
is
basically
a.
How
would
I
put
it
themes,
toolkit
v2,
specific
structures,
then
there's
the
vs
code
information
and
then
in
my
solution.
Currently,
I
only
have
a
spfx
solution,
which
only
has
currently
one
web
part
inside
of
it,
and
it
has
some
set
of
default
settings
available.
B
Now,
as
part
of
the,
the
guidance
will
also
include
a
pr
the
readme
file,
where
we
then
provide
the
minimal
path
to
awesome.
So
it
will
make
sure
that
you
have
the
right
solutions,
right
versions
and
everything
else
available,
and
then
you
are
able
to
start
using
the
automation
which
is
available
in
the
teams
toolkit.
So
let
me
zoom
a
bit
away,
so
I
will
see
the
team's
toolkit
on
the
left
menu
and
I
can
basically
modify
the
manifest
in
here.
Of
course,
I
can
see
the
manifest
I
can
get
to
the
manifest.
B
I
can
modify
that
I
can
modify
the
images
I
can
adjust
the
settings
when
that's
actually
done.
I
can
validate
that
manifest
file
and
it's
basically
going
to
do
a
live
validation,
and
it's
going
to
tell
me
if
something
is
wrong
with
the
validation
and
all
of
that
I
can
build
the
teams.
Packets
which
basically
going
to
create
the
manifest
file-
and
I
can
provision
that
to
the
cloud
and
what
that
means-
is
that's
basically
taking
that
solution
package
and
it's
installing
that
directly
to
the
team's
antenna.
B
If
I
would
install
or
want
to
install
the
solution
to
the
tenant,
I
would
click
deploy
to
the
cloud
which,
unfortunately,
right
now
is
not
doing
anything
automatically
so
and
of
course
that
would
be
good
feedback.
Can
we
automate
this
so
the
team's
toolkit
automatic
deployment
is
not
currently
supported
for
a
sharepoint
framework
solution.
It
will
basically
now
install
a
run
the
npm,
install
and
then
package
the
sharepoint
package
and
ask
you
to
put
it
in
the
tenant
app
catalog.
B
But
after
that,
you
can
basically
then
test
the
solution
directly
in
teams
and
and
do
the
things.
So
it's
a
slightly
different
experience
than
the
yeoman
generator,
but
we
would
love
to
get
more
feedback
on
what's
needed.
How
is
it
working
try
to
hands-on
labs
and
tutorials
tutorials,
which
are
available
provide
feedback?
B
As
for
the
office,
dev
teams,
fx
repo,
and
so
we
know,
and
the
visual
studio
organization
knows
how
to
adjust
this
experience
to
better
match,
on
your
expectation,
really
cool
stuff
for
sure,
but
that's
it
for
my
sites
and
we
are
running
out
of
time
as
well.
So,
let's
flip
back
on
david's,
I
think
on
your
screen.
A
Absolutely
thank
you,
visa
excellent
demos
today.
Thank
you,
julie,
vesa
and
derek.
I
think
it's
important
to
note
for
those
watching
the
video
afterwards
again.
All
of
these
tools
and
resources
are
available
to
you
for
free
that
covid
attestation
solution
is
amazing
and
available
to
you
at
no
cost.
So
please
don't
hesitate
to
take
advantage.
Recording
of
this
will
be
available
in
24
hours
at
aka,
dot,
ms4,
slash,
m365,
pnp,
forward,
slash
videos.
Our
next
call
for
spfx
is
july.
A
29Th
same
bat,
channel
same
bat
time
7
a.m,
pacific
our
m365
general
development
call
will
be
next
week
july
22nd
at
7
a.m.
You
can
always
get
access
to
all
of
the
developer
community
calls
via
these
links
here.
Of
course,
you
can
always
as
well
go
to
ak
dot,
ms4
m365
pnp
to
access
all
the
links
we've
showed
you
today,
but
in
addition
to
that
we'd
like
to
thank
everyone
for
attending
and
again
thank
you
to
vesa,
julie
and
derek
for
the
demos
hope
everybody
has
a
wonderful
weekend
and
the
rest
of
your
week.