►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 30th of August. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI and Reusable SPFx controls.
Cool demos on build SharePoint Framework Application Customizers and Web Parts.
You can download an invite to this bi-weekly call from https://aka.ms/spdev-spfx-call.
A
Hello
and
welcome
to
the
SharePoint
framework
in
JavaScript
special
interest
group
bi-weekly:
sync:
it
is
August
30th
the
end
of
summer,
which
is
always
a
sad
time
of
the
year,
but
I'm
excited
for
fall
and
I
hope
everybody
is
as
well
for
those
of
you
might
be
new
to
the
call
or
new
to
watching
these
recordings.
We
always
like
to
go
over
what
we're
discussing
and
why
we
have
these
calls.
A
So
the
special
interest
group
calls
were
part
of
the
larger
SharePoint
patterns
and
practices
program,
and
the
idea
is
really
to
provide
a
forum
to
focus
on
different
areas.
So
this
call
is
focused
on
an
open
discussion
around
SharePoint
framework
and
client-side
development
patterns
associated
with
SharePoint,
as
well
as
the
pjs
libraries
and
the
reusable
controls
and
office
365
CLI,
which
all
of
which
are
emphasizing
simple,
repeatable,
tested,
designs
and
patterns
to
hopefully
make
your
development
lives
a
little
bit
easier.
A
B
A
But
so,
if
you're
still
doing
the
see-saw
managed
code
development,
the
other
special
interest
group
call
may
be
of
interest
to
you
and
of
course,
please
do
attend
as
many
of
these
calls
as
you
would
like.
We
always
love
to
have
you
here.
So
two
links
down
there
at
the
bottom,
SP
P
and
P
community
will
take
you
to
the
Microsoft
tech
community,
for
so
that
into
the
SharePoint
section
of
the
Microsoft
tech
community.
So
you
can
ask
your
you
know.
Sort
of
general
questions
is
a
great
place
for
the
type
of
questions
about.
A
How
would
you
design
this
solution?
What
how
would
you
structure
this
application
things
like
that
that
aren't
necessarily
questions
for
a
specific
library
or
SharePoint
framework
itself
and
the
second
link
there
AKMs
SP
Doc's,
will
take
you
to
the
SharePoint
developer,
documentation
for
all
of
SharePoint
developer
space,
so
whether
you're
new
to
SharePoint
framework
and
looking
to
learn
that
and
get
involved
in
that
you
can
follow
through
all
the
tutorials
demos
there,
but
as
well.
The
seesaw
managed
code
development
and
even
the
the
truly
ancient
before
time,
WSP
full
code
deployment
solutions.
A
But
no
our
site
definitions,
definitions
or
delete
the
root
site
collection,
all
your
developer
documentation,
but
we
digress
all
the
developer.
Documentation
is
at
that
location
and
we
are
working
to
improve
that
constantly.
So,
if
you
do
see
places
we
can
improve
that
or
things
that
might
be
missing
or
things
that
could
be
made
better
or
more
clear.
Please
do
let
us
know
I
believe
and
I'm
not
lying
when
I
say
this,
there's
a
there's.
A
feedback
link
at
the
bottom
of
those
pages
so
definitely
check
that
out.
A
So
moving
into
our
agenda.
For
this
call,
as
always
we'll
start
basis,
is
hi
again
man.
We
really
need
to
get
that
deleted,
but
it's
hidden
when
you
edit
the
slide,
which
is
an
awkward
engineering
update
on
SharePoint
framework,
we'll
do
a
quick
update
on
the
P
and
P
j
s,
client-side
libraries
as
well
as
office,
365
CLI
and
the
S
P
FX,
reusable
controls
and
then
we'll
get
into
two
great
demos,
one
from
Madi
on
an
application
customizer
to
notify
end-users
of
a
SharePoint
site.
A
When
the
underlying
group
has
been
archived
so
a
neat
solution
there
and
then
from
David,
we've
got
building
template,
SPF,
X
webparts.
Another
great
solution
so
excited
to
see
both
of
those
demos
coming
up
later
in
the
call-
and
hopefully
we'll
have
a
little
bit
of
time
at
the
end
for
Q&A,
but
as
always,
I
will
try
and
keep
up
with
the
questions
and
the
chat
in
the
IM
window
so
feel
free
to
post
your
questions
and
things
like
that.
There.
A
So
if
you
have
ideas
for
a
demo,
I
would
like
to
do
something
it's
as
easy
as
just
reaching
out
to
myself
or
visa
and
we'll
get
you
on
the
schedule.
We
are
a
little
booked
out
at
this
point.
So
don't
fear
we
will
get
you
on
the
agenda,
but
it
will
be
a
couple
calls
out
at
this
point.
But
if
you
have
something
please
do
reach
out,
let
us
know
love
to
get
you
booked
and
loved.
A
To
give
you
an
opportunity
to
show
off
the
awesome
work
you're
doing
out
there
for
your
customers
or
for
your
company.
You
can
always
demo
an
at
PMP
solution
as
well,
so
anything
office,
365,
CLI,
the
PJs
libraries
or
the
reasonable
controls
make
great
demos
both
inside
and
outside
of
SharePoint
framework.
As
always,
we
very
much
encourage
you
to
contribute
on
github,
which
can
take
a
couple
different
shapes
you
can
provide
us.
You
can
report
issues
on
either
SharePoint
framework
or
any
of
the
things
I've
mentioned
that
the
libraries,
the
controls
or
the
CLI.
A
You
can
report
issues.
You
can
submit
pull
requests
very
much.
We
welcome
those
pull
requests.
So
if
you
have
an
idea-
and
it's
a
quick
little
change,
please
do
do
a
pull
request
when
I
get
some
time.
I'm
gonna,
try
and
record
a
video
on
that
process
of
you
know
having
an
idea
or
taking
an
issue
and
working
that
all
the
way
through
to
a
pull
request,
so
keep
an
eye
out
for
that-
hopefully,
maybe
later
this
week.
A
Well,
it's
already
Thursday
so
maybe
early
next
week
and
then
finally,
we
very
much
if
it's
not
a
specific
issue
or
things
like
that,
it's
just
general
feedback.
Absolutely
welcome
that
as
well.
Feedback
on
these
calls
feedback
on
our
documentation,
feedback
on
you
know
just
sort
of
how
we're
doing
things.
What
we
could
do
better
very
much
always
appreciate
that.
So
we
in
the
core
team
definitely
talk
about
it
discuss.
You
know
we
heard
from
so-and-so
this.
What
can
we
do
to
to
help
with
that?
So
please
keep
that
feedback
coming.
A
B
You
I'm
taking
over
the
presenter
if
I
can
or
you're
sharing
a
screen
know
you
practice
your
own
slides
that
was
successful,
so
a
few
things
from
a
engineering
side
of
the
house
opposite
to
classic
slides.
It's
always
keeping
here.
First
of
all,
the
documentation,
a
chemist,
spdf
Docs,
we
will
do
a
pretty
big
push
on
updated
documentation
in
here
actually
later
today,
so
updated
documentation
on
SharePoint
framework,
new
stuff,
updated
documentation
on
modern
experiences
and
few
other
stuff
to
address
some
of
the
community
questions
and
discussion
which
have
been
happening
lately.
B
The
views
are
growing
quite
nicely
in
here.
The
August
is,
however,
the
summer
vacation
time
in
Europe,
which
means
that
they're
slightly
down
in
August,
potentially
from
July,
but
we'll
see
how
it
goes
and
the
other
thing
what
I
want
to
pinpoint
and
I
always
have
this
in
the
slides
is
the
issue
list.
So
please
keep
on
reporting
these
issues
initial
list
we
are
falling
behind
and
we're
slightly
behind
of
addressing
them
we're
trying
to
catch
up
as
fast
as
possible,
ignite
one-point-six
release.
B
What
about
ship
on
framework
so
quickly
from
a
adaption
and
use
its
perspective?
So
once
again,
if
you're
looking
into
people
using
SharePoint
framework
answer
is
yes,
they
are
so,
and
it's
it's
actually
interesting.
I
just
today
left
quick
calculations
on
the
under
usage.
So
last
time
in
ignite.
If
we
compare
to
usage
from
a
year
ago
in
ignite,
it's
the
use,
it
says
ten
times
of
the
net
was
in
a
year
ago
in
ignite,
so
the
SharePoint
framework
usage
has
exploded
ten
times
bigger
than
it
was
a
year
ago
in
ignite.
B
So
that
gives
you
a
perspective
on
how
fast
and
how
huge
and
how
widely
sharepoint
framework
is
already
used
in
SharePoint
Online.
Now,
obviously,
it
will
be
used
in
ship
on
2019,
because
ship,
a
20-19
supports
natively
one
on
pages
ship
160
in
fitchburg
to
support
ship
and
favorite
web
parts,
and
the
usage
is
actually
even
this
week
this
this
matrix,
which
you
can
see
on
the
slides.
These
are
custom
third-party
solutions
running
in
the
SharePoint
from
last
a
year
ago,
July
until
actually
yesterday.
B
So
the
final
marker
is
yesterday's
marker,
so
you
can
clearly
see
the
growth
pattern
and
it's
actually
it's
growing
exponentially.
So
the
look
this
week-
I,
don't
know
what's
happening,
but
it's
it's
again
we're
making
all-time
records
on
the
ship
on
framework
usage,
so
that
is
pretty
cool
and
obviously
what
whatever
we
are
releasing
right.
Now,
it's
kind
of
just
explore
well
CRO
to
use
its
even
more
so
using
SharePoint
framework
as
a
tooling
for
creating
tabs
in
the
Microsoft
team,
starting
from
1.7.
B
It's
gonna
help
on
what
people
are
kind
of
used
it
more
1.6,
and
this
is
a
actually
let's
start
with
a
within
the
chronometer
chrono.
Well,
within
the
order
of
the
slide,
so
chevron
framework
on
POSIX
ETA
is
still
is
end
of
August
and
we
never
ship
on
Friday.
So
what
is
today?
We
kind
of
ship
1.6
so
in
the
focused,
but
we
never
shipped
on
Friday.
So
what
is
today
we're
gonna?
Yes,
the
winner
is
Joe,
so
unless
there's
a
really
really
really
really
really
last-minute.
Oh,
my
god,
we
completely
missed
this.
B
The
1.6
will
go,
live
within
two
and
a
half
hours,
so
you
can
expect
announcements
in
social
media
in
Facebook
and
in
Twitter
and
blog
post
and
everything
else
within
pretty
much
in
two
and
a
half
hours.
If
that
doesn't
happen,
it
means
that
we
found
out
a
really
hit
last
minute:
oh
my
god.
We
can't
do
something
and
we
need
to
delay
that
until
early
next
week,
in
the
worst
case
scenario,
we
never
ship
on
Friday,
because
you
should
never
actually
deploy
a
production-ready
code
on
Friday.
That's
just
an
owner
in
nightly
business.
B
Our
stutters
big
thing,
obviously,
is
the
tenant
wide
deployment
of
SharePoint
framework
extension
and
so
basically
from
a
catalog,
you're
able
to
say
hey
this
shipment
framework
extension
I
want
that
to
be
enabled
in
every
single
communication
site
in
my
tenant,
with
the
snap,
our
fingers,
pom
your
footers
and
faders,
and
whatever
will
be
automatically
available
across
all
of
the
sites.
Potentially,
if
you
want,
you
can
actually
target
to
every
single
site
from
a
modern
morning.
Experience
perspective.
B
The
key
point
to
remember
on
the
extensions
is
that
the
extensions
only
work
on
the
modern
experience,
not
on
a
classic
experience,
so
you
can't
use
the
tenant
wide
deployment
option
for
classic
experience,
but
for
modern
experience
everything
works
in
any
single
file.
Now,
in
one
point
one
point:
what
is
it
rough
bones
anyway
for
one
point:
seven,
so
we
needed
to
actually
postpone
some
capabilities
which
were
originally
panic,
put
in
the
one
point
six
and
they
were
under
caution
like
they
miss
the
date
marker
and
they're.
B
Now
in
one
point:
seven
so,
for
example,
shipment
2019
native
support
in
human
and
then
socket
IO
preview,
which
actually
we
are
debating
if
we
could
actually
do
a
niche
release
between
one
point,
six
and
one
point:
seven,
because
it's
a
isolated,
separate
package.
So,
let's
see,
if
that
happened,
ta
of
dynamic
data
is
planned
to
be
in
one
point:
seven
preview
of
themes,
tab
development
and
so
that
I
ever
mentioned.
B
Sixteen
support
was
delayed
there
and
there's
a
few
cool
things
which
will
actually
announced
and
ignite
within
a
few
weeks
related
on
addressing
the
common
asks.
What
people
are
actually
asking
should
be
reported
in
SharePoint
framework,
an
ETA
for
1.7
right
now
is
end
of
October.
So
we're
doing
this
not
on
the
Ignite
timeframe.
We
both
show
capabilities
and
ignite
and
then
we'll
finalize
them
and
then
we'll
ship
them
in
October
and
to
make
sure
that
everything
is
available.
B
Are
you
going
to
talk
it
on
SharePoint,
Online,
Chevron,
2016
above
and
shep
in
2019
above
and
then,
if
you
choose
the
SharePoint
2019,
it's
going
to
point
the
packages
to
one
point,
four
point
one
except
for
the
craft
API
as
because
krafayis
are
not
available
in
opera.
Now,
obviously
there
will
be
also
enhanced
a
SharePoint
support
in
a
craft
API.
We
can
announce
some
things
there
in
ignite,
so
be
looking
into
about
that.
There's
plenty
of
work
being
done
on
on
there.
B
There
will
be
a
general
feature,
improvements
on
the
other
areas
of
functionality,
areas
left,
side,
design,
side,
scripts,
modern
themes
and
all
of
that
stuff,
and
then
I
wanted
to
make
sure
that
this
is
mentioned
in
our
roadmap
sites
as
well.
So
season
don't
know
standards
PowerShell
core
the
both
are
in
the
roadmap,
but
these
are
now
scheduled
to
get
started
on
after
ignite.
So
hopefully,
by
end
of
the
year,
we'll
have
a
season
that
standard
officially
out
for
Microsoft,
which
is
which
clearly
has
a
a
clear
demand
as
well
good.
B
Is
least
beautiful
meeting,
possibly
dropping
with
one
point
six
on
David's
question
on
the
on
the
view
formatting
via
formatting
is
actually
not
part
of
shape
and
framework.
So
she
open
framework
is,
is
more
on
when
we
write
a
code
when
you
develop
an
acrid
script
view
formatting
and
column
formatting
our
ship
as
an
independent
functionality,
is
more
like
a
citizen
developer
functionalities
and
they
should
be
we're.
Commenting
should
be
out
before
ignite
as
well.
B
B
This
particular
solution
contains
nine
different
mics
of
graph
wit
pots,
for
example,
show
my
latest
email
show
my
upcoming
calendar
in
meetings,
show,
might
open
tasks
and
all
of
that
stuff
or
show
my
conducts
those
web
parts
are
available
for
you
from
a
source
code
perspective
from
the
shipment
start
begin,
and
it
has
not
yet
been
updated
to
one
point:
six.
It
will
be
updated
to
one
point
six,
hopefully
next
week,
so
the
team
is
working
on
getting
this
one
updated.
Now
that
one
point
six
crossing
fingers
will
go
live
later
today.
B
A
So
take
over
just
a
second
here,
so
quick
updates
on
the
PNP
client,
PGS,
client,
side,
libraries
next
release
targeted
for
September
7th.
This
I
mentioned
last
call
this
might
be
a
major
release.
It's
not
gonna,
be
it's
gonna,
be
one
dot,
one
dot
five,
so
falling
right
in
line
it's
mostly
gonna,
be
internal
changes,
so
should
be
fairly
invisible
to
folks
consuming
the
library.
A
But
if
you
see
some
issues
because
we
did
make
internal
changes
to
how
some
things
work,
if
you
see
issues,
please
just
report
and
we're
gonna
fix
just
as
quick
as
we
can.
We've
also
included
a
bunch
of
new
functionality,
so
would
encourage
you
try
out.
The
current
beta
is
up-to-date.
Please
give
us
some
feedback
on
that.
We've
already
gotten
some
great
feedback
on
that
as
well.
Updates
on
the
CDN
guidance
are
coming.
A
We've
worked
with
some
some
folks
on
the
engineering
team
to
better
understand
how
to
integrate
with
SPF
X
externals
and
then
so
that
that
stuff
will
get
updated.
With
the
next
release
we
removed,
we
used
to
use
a
custom
dictionary
class
we've
removed
that
in
favor
of
map,
and
we
used
to
use
some
custom
error
classes
and
we've
just
gone
ahead
and
removed
those
in
favor
of
just
throwing
a
new
error.
Instead
of
a
new
one
of
our
errors.
A
We
also
some
some
good
ideas
from
the
community.
One
of
them
was
support
for
caching
search
results.
So
that's
now
going
to
be
supported.
There's
gonna
be
a
new
method,
as
well
as
the
search
object
itself
search
instances
will
support
the
using
caching
chaining
so
we'll
have
that
coming
in
the
next
release,
and
much
more
so,
we've
got
the
changelog
which,
right
now
the
updated
change
log
is
sitting
in
kind
of
a
giant
pull
request,
but
we'll
get
that
stuff
merged
likely
later
today
or
tomorrow
morning.
A
So
we
can
get
the
Friday
beta
out
for
everybody.
One
thing
I
wanted
to
mention
is
we
definitely
wanted
to
encourage
you
to
submit
pull
requests.
We
get
a
lot
of
great
ideas
from
folks
and
we
sometimes
have
a
lot
of
times.
Sometimes
don't
have
a
lot
of
time
to
implement
those
things
so
want
to
make
it
clear.
We
definitely
encourage
pull
requests.
If
you
want
to
contribute,
if
you
want,
you
know
to
see
your
idea,
definitely
make
it
into
the
next
version.
A
pull
request
is
the
way
to
do
that.
A
So
we
very
much
accept
those
very
much
encourage
those
don't
want
to
let
or
make
folks
think
that
we're
not
looking
for
contributions.
We
definitely
are
so.
Your
pull
requests
are
absolutely
encouraged.
The
only
thing
I
would
say
if
you're
gonna
do
some
very
large
change
just
reach
out.
First,
you
can
open
an
issue
we'll
discuss
it.
A
I
just
want
to
make
sure
it's
something
we'll
be
able
to
merge
before
you
spend
a
whole
lot
of
time
on
something,
but
absolutely
welcome
those
contributions
and
pool
requests
and
down
there
at
the
bottom,
P
and
P
get
up
in
PJs.
We've
got
the
documentation
there.
We've
also
got
about
a
little
bit
of
work
around
finalizing.
It
need
to
work
with
Chris
Kent
did
a
great
job
of
updating
the
documentation
is
going
to
be
a
great
update.
A
Excuse
me
new
beta
version,
one
six
zero
is
coming
out
or
is
out.
Excuse
me
with
support
for
managing
content
types
fields,
modern
pages,
Microsoft
teams,
as
well
as
upgrading
SPF
X
projects
in
all
versions
from
one
to
one
five
one.
If
you
haven't
checked
that
last
capability
out,
it's
really
cool,
it
allows
you
to
take
your
existing
SharePoint
framework
solutions
that
may
have
been
built
on
an
earlier
version
and
upgrade
them
to
the
latest
version.
So
really
cool
capability,
really
neat
thing.
Please
do
try
that
out.
A
A
Think
AC
did
a
lot
of
that
and
perhaps
some
others
from
the
community
apologize
if
I've
left
anybody,
lint
yeah
left
anybody
out,
but
check
that
capability
out
very
cool
and
some
some
other
work
that
continues
in
progress
is
around
the
cross-platform
PNP
starter
kit
set
up
script,
so
that
would
be
the
ability
to
set
up
the
starter
kit
using
the
CLI.
So
that
would
be
a
very
cool
thing
and
kind
of
unlock
some
cross-platform
capability
and
then,
as
well
as
some
additional
and
sort
of
we
always
have
that
open
question.
A
We
always
welcome
that
feedback
and
you
can
install
the
latest
version
from
NPM
with
NPM
install
G
at
P
and
P
slash
office,
365
CLI,
there's
an
aka
ms
link
down
there
at
the
bottom
for
more
information
as
well
as
you
can
follow
the
hashtag
office,
365
CLI
on
Twitter,
there's
a
git
er
channel
and
as
well
that
Doc's
link
for
more
information
and
getting
started
now
updates
around
the
SPF
X,
reusable
controls,
not
as
much
updates
this
week.
Elio
has
been
super
busy
on
some
believe
it
or
not
of
his
real
job.
A
I
can't
believe
he's
doing
that,
but
just
want
to
remind
folks
if
you
haven't
checked
out
the
reusable
controls.
There's
two
flavors
there's
the
property
controls
which
are
designed
to
work
easily
inside
the
property
pane
when
you
edit
your
SharePoint
framework.
Webparts,
can
save
you
a
lot
of
time
and
effort
for
creating
very
rich
editing.
Experiences
for
your
webparts
as
well
to
react,
clunk,
laughs,
Wow
I
am
just
babbling
today
react
content
controls
which
serve
to
really
enhance
your
experience
inside
the
presentation
of
your
webparts.
A
So
those
are
going
to
give
you
more
control
and
then
as
well,
really
save
you
a
lot
of
time
and
building
these
rich
experiences
and
because
they're
built
on
an
office
UI
fabric,
you're
gonna,
get
that
seamless
experience
inside
sharepoint
where
it
looks
like
built-in
functionality
so
check
out
both
of
these
packages.
Really
cool
will
definitely
save
you
some
time
and
a
lot
of
effort
in
sort
of
creating
these
things
on
your
own
so
check
those
out.
A
The
two
most
use
is
the
placeholder
control
and
the
webpart
title
control
so
check
those
out
and
then
some
upcoming
work
we're
feeding
controls
from
the
first
party
out-of-the-box
engineering
work.
So
we're
doing
a
lot
of
give-and-take
back
forth
between
this
reusable
control,
work
and
the
actual
engineering
teams
to
really
create
that
rich
experience
and
then,
as
always,
we're
working
to
improve
all
the
existing
controls
we
have.
So
if
you
have
ideas
or
see
issues
with
any
of
those,
please
do
report
them.
A
We
absolutely
want
to
get
those
fix
and
you
know
again
make
it
better
for
everybody.
That's
the
the
goal
of
kind
of
all
this
work,
so
more
information
to
links
down
there
at
the
bottom
will
take
you
to
the
docs
for
the
property
controls
and
the
reusable
content
controls
there.
You
can
see
the
links
so
check
those
out
and
definitely,
if
you're
doing,
SharePoint
framework
development
do
have
a
look
at
these
controls.
They
are
a
real
time-saver.
It's
really
valuable
contribution
to
the
community
and
there's
been
a
lot
of
community
work
there
as
well.
A
I,
don't
mean
to
say
it's
just
Elio
working
on
those.
A
lot
of
other
folks
have
pitched
in,
and
we
very
much
appreciate
everybody's
involvement
so
with
that
I
will
turn
things
over
to
Matti
for
his
demo.
This
is
an
application
customizer
to
notify
end
users
inside
SharePoint
that
the
underlying
group
has
been
archived.
Hopefully,
I've
said
that
right,
yeah.
B
C
Because
this
is
my
first
contribution
actually
a
first
demo,
so
my
name
is
Muffy
Popkin
and
I'm
from
Finland
working
as
a
senior
architect
on
you
know,
factor
which
is
finished:
IT
company
operating
in
the
Nordics
currently
working
with
new
business
offerings.
Modern
employee
experience,
teamwork
stuff,
like
that
for
like
SharePoint
teams
of
history,
65,
etc.
C
C
Here's
my
Twitter
and
I
also
started
a
blog
which
is
quite
empty
actually,
and
most
of
it
is
still
in
Finnish.
So,
but
you
can
check
it
out.
If
you
want
that's
it
about
the
intro,
then
about
the
demo.
I
don't
want
to
save
it.
So
today,
I'm
actually
demonstrating
my
hobby
project
a
little
hobby
project,
which
is
a
simple
application:
customizer,
which
is
notifying
the
end
user.
C
If
the
team
behind
it
team
site
is
set
as
archive
and
no
is
it
actually
a
group
property
because
I
didn't
find
it
from
the
graph
API,
but
the
teams
teams
bad
idea,
actually
returns
it
so
to
the
demo,
then
yeah.
The
solution
is
actually
utilizing.
Microsoft
graph
team's
beta,
API
and
and
also
some
p.m.
C
PJs
core,
still
I'm
planning
to
actually
migrate
the
PNP
J's
later
and
also
did
a
1.6
SPF
X
version
laser
today,
maybe
yeah
how
about
today
mom
here's
some
just
newly
created
fresh
out
of
the
box,
modern
team
site,
where
I
have
already
connected
to
a
team
Anna
and
also
it's
loading.
The
application
customizer
from
my
local
environment
I
have
called
server
already
running
there.
C
That
doesn't
matter
actually
how
it
works
and,
as
you
can
see
it's
now
archived
then
I
get
back
to
the
site
and
just
hit
refresh
and
once
everything
is
actually
loaded.
It
will
display
that
the
little
notification
that
this
team
is
actually
set
as
archived
so
simple
of
simple
as
that
I
think
powerful,
but
of
course
simple
and
hey,
where
you
can
actually
find
my
code,
then
a
little
bit
of
code,
because
there
is
only
a
little
bit
of
bit
of
code
here.
C
It
just
gave
me
a
401
I,
don't
know
why,
but
it
got
fixed
during
this
call
and
if
the
is
archive
property,
which
is
actually
returned,
also
is
set
to
to
true
it's
just
going
to
render
a
little
react
element
which
is
with
just
containing
and
message
bar
where,
where
is
the
actual
type,
is
set.
The
server
warning-
and
there
is
some
localization
also
included-
and
for
packaging
we
just
need
some
craft
API
permissions,
so
there
should
be
a
scope.
Group
read
all
included
to
make
this
work
then
about
the
deployment
side.
C
C
Application,
customizer,
hey
and
I
actually
forgot
to
actually
upload
it
here,
but
but
this
is
just
normal
operation
I,
don't
know
why
all
of
these
are
missing
here.
So
if
I
just
go
to
my
app
catalog
and
just
drop
the
package
here,
this
is
all
familiar
to
you,
I
think
and
make
this
available
to
all
sites
and
deploy
and
then
I
need
also
go
to
the
admin
admin
center
and
go
the
Derby
management
hey.
What
is
this
and
just
approve
the
access
to
Microsoft
graph
and,
of
course,
I
have
done
it
before.
C
A
A
A
A
D
A
D
Exactly
okay,
so
I
guess
to
do
a
small
demo
of
each
of
the
web
parts.
Before
we
go,
we
go
deeper
into
the
handlebar
template.
There
are
four
different
web
parts
that
exist
in
that
package.
You
have
a
links
list
which
you'll
see
called
featured
topics
on
his
display
where,
as
mouse
is
hovering
and
then
can
you
edit
the
page
Dave
and
go
into
the
property
panel
for
that.
D
D
D
But
yeah
you
can
then
just
map
the
individual
columns
on
the
list
into
the
different
properties
that
you
see
for
the
public's
or
any
of
the
other
webparts
we
have
the
next
web.
Part
type
would
be
the
featured
contents
web
part
which
do
we
have
one
of
those
on
this
page
neighbor
as
it
is
on
the
government's
page.
It's
the
office,
365
services
that
you
see.
B
D
So
then
yeah
they're
in
the
basic
mode,
which
is
the
non
list,
packed
mode
yeah.
We
actually
set
up,
so
you
can
go
in
and
edit
the
individual
items
so
go
in
and
then
you
can,
as
you
type
it'll
update.
Obviously
so
you
could
have
them
either
stored
within
the
web
part
or
as
a
list
box
view
that
you
could
then
use
on
multiple
different
pages.
D
D
D
D
And
finally,
the
I
guess
the
most
flexible
of
them
would
be
the
hub.
The
template
web
part,
which
relies
on
a
handlebar
template
to
produce
the
display
so
the
for
the
handlebar
template.
You
can
either
back
it
by
a
list
or
my
search
and
you
just
select
the
list
and
the
filters,
and
then
they
can.
We,
since
we're
not
going
to
save
this
page.
Can
you
add
a
blank
template
but
parts
of
the
page
that
we
can
show
what
happens
when
you
first
edit.
D
And
then,
after
doing
the
hand
of
our
template
itself,
you
have
the
ability
to
check
the
check
box
for
optimizing.
The
template,
which
pre
compiles
the
handlebar
template
and
to
say
improve
the
performance,
but
it's
kind
of
the
trade-off
where
you
have
in
order
to
rebuild
the
template
after
changes,
you
have
to
put
the
page
back
into
edit
mode.
D
D
B
B
In
a
unwilling
or
blocked
situation,
but
this
is
basically
where
we
are
actually
seeing
this
from
Shire,
so
this
is
chars
apparently
shires
tenants
where
this
is
used
in
production
use
it.
So
this
this
is
webpart
which
is
used
by
our
company
in
production
as
well.
Yep,
so
really
cool
stuff
and
I'm
David,
a
Mike
and-
and
there
has
been
quite
a
few
MVP-
is
actually
involved
of
implementing
this
webform.
The
big
part
solution
is
actually
open
sourced
in
github
under
the
SPF
solutions.
B
So
the
link
is
in
time
window,
we'll
put
it
in
the
video
notes
as
well.
It's
it's
really
great
functionality.
It's
been
there
actually
for
quite
a
long
time
as
well.
So
it's
been
helping
people
to
adapt
the
templating
system
in
a
multiple
ways,
so
really
cool
stuff.
Absolutely,
and
now
that
I'm,
remembering
I,
think
we
have
a
full
list
of
authors
here
somewhere
and
no,
we
don't
actually,
unfortunately,
so
I
can't
give
credits
for
the
o'the
MVPs
who
have
been
involved
in
this,
because
this
just
out
first,
it.
B
D
B
Related
on
this
one
so
or
whether
this
would
be
potentially
included
in
the
reusable
controls
that
BMP
SPFs
reusable
control,
so
it
would
be
in
the
reusable,
really
easily
reusable
from
a
package.
So
we
can
absolutely
help
on
getting
this
one
on
the
reusable
controls,
because
the
BMP
reusable
controls
we
we
source
some
of
those
ideas,
obviously
from
these
solutions
and
also
from
out-of-the-box
controls,
which
we
used
internally
in
engineering,
because
we
can't
open
sourced
them.
We
actually
share
some
of
the
code
truth
to
BMP
reusable
controls,
which
we've
mentioned
earlier.
B
B
And
we
can
talk
about
that.
One
obviously
yeah
whenever
it's
suitable
anyway,
so
really
create
great
demand,
great
functionality,
great
solution.
Absolutely
so,
should
we
go
back
on
the
slides,
Patrick
we're
still
at,
but
we
actually
have
12
minutes.
This
is
good.
We
have
time
for
Q&A
because
typically
we
take
too
much
time
under
of
not
too
much
time
but
more
time
on
the
code
level
as
well
and
ie
being
built.
We
well
I
talk
too
much.
So
that's
for
that's
what
you're
trying
to
say.
A
B
B
Yes,
there's
a
certain
API,
so
it's
unfortunate
they're
still
undocumented.
We
are
tracking
these.
These
are
being
routed
to
the
right
feature:
crews,
the
problem
in
the
many
of
the
API.
So
how
would
I
put
this
in
a
polite
way
that
my
colleagues
in
future
PMS
wouldn't
get
angry?
So
in
some
of
the
feature?
Crews,
the
PM's
prioritize
first
party
experience-
and
they
forgot
about
that.
B
The
third
party,
like
the
developers,
might
be
interested
on
the
capability,
and
this
is
this
is
mainly
because
they
want
to
get
their
their
functionality
first
out
so
that
they
can
get
feedback
in
and
that's
basically
the
reason
why.
Quite
often,
you
see
some
new
webparts
using
some
api's,
which
are
not
unfortunately,
document
so
that
that's
basically
unfortunate
side-effect
of
getting
stuff
out
as
fast
as
possible.
Now
we
are
trying
to
figure
out
how
to
get
this
sorted,
assorted
internal
in
engineering.
B
It
is
a
fight
between
the
amount
of
resources
plus
the
processes
plus
the
demand
of
shipping,
plus
the
minimal
Viable
Product
approach,
and
all
of
that,
so
it's
I
do
not
have
a
timelines
or
any
updates
on
this
particular
one
689
item.
Unfortunately,
but
I
do
understand
the
challenge
of
first
party
having
access
from
certain
ideas
which
I'm
not
recommended
for
third
party,
because
that
kind
of
freights
the
the
promise.
B
What
we've
been
saying
for
SharePoint
framework
you're
using
exactly
the
same
tooling,
exactly
the
same
API
as
first
party
and
unless
we
in
engineering
actually
expose
this
API
is
and
document
AP
is
you
can
really
use
the
API,
so
you
can't
achieve
the
same
thing.
So
it
is
acknowledged.
This
is
internal
debate,
internal
discussion
in
engineering.
How
we
get
this
one
resolved
in
a
long
run
so
and
I
came
from
it.
I
can't
provide
any
additional
data
so
now.
B
Bmp
provisioning
stuff:
well,
that's
a
curve
for
my
creations
will
help
be
able
to
go
from
2013
to
2019,
and
so
the
PMP
provisioning
is
for
provisioning.
It's
not
actually
technically
for
my
creations,
so
we
do
not
support
extracting
of
contact.
Then
we
support
extracting
of
content
only
and
a
welcome
pay.
It's
not
on
any
other
page,
and
that's
that's
really.
Why
and
it's
knowing
the
decision
that
we're
not
looking
into
moving
to
the
my
creation
world
now
we'll
the
same
template
work
in
2013
or
2019
answers.
Actually,
yes,
they
did.
The
same.
B
Template
does
work
in
2013
and
2019,
so
by
default.
That
should
be
fine.
The
we
do
not
have,
however
PMT
powershell
PMP
sees
them
right
now
for
2019.
If
you
use
2016
version
or
shipment
online
EMP
PowerShell,
it
will
work
with
2019
preview
from
now,
eventually
it
will
break
whenever
2019
is
falling
behind
of
the
API
chances.
B
Comfort
story,
maybe
we'll.
We
should
actually
talk
about
this
one
in
this
not
into
SPF
X
goal,
but
on
the
other
one
in
a
week
from
now.
So
what
is
the
version
and
we're
going
to
have
forward
good
point?
David
has
question
on
any
API
is
in
work
for
audience
targeting.
Yes,
there
is
an
API
us
in
work
audience
targeting
so
one
of
the
big
things
where
we
are
baiting
now
there
will
be
plenty
of
talks
on
this
one
and
ignite.
B
What
is
targeting
worked
really
well
in
on-premises,
because
you
will
be
able
to
control
the
how
often
audiences
were
compiled
in
SharePoint
Online
audience
targeting
actually
does
not
work,
because
in
the
SharePoint
Online
audiences
are
compiled
once
a
week
and
that's
way
too
rarely
so
in
SharePoint
Online.
You
should
be
targeting
based
on
user
profile
attributes
not
based
on
audiences,
because
you
can't
really
the
classic
audience
model,
isn't
really
working
that
well
the
for
future.
We
there
will
be
a
ways
of
defining
audiences
and
scopes
and
groups
and
everything
else.
B
So
that's
in
the
in
the
world,
so
you're
able
to
say
this
webpart
would
be
visible
only
for
a
subset
of
people
based
on
this
attribute,
for
example,
in
a
user
profile.
But
it's
what
it
will
be
well
how
it
will
actually
work
in
detail.
What's
the
API
layer
of
that
there's
nothing,
we
can
share
in
detail
right
now,
because
we
don't
want
to
over
the
over
promise
and
then
not
deliver
and
then
you'll
be
angry.
So
the
classic
Microsoft
way
of
saying
well
I
can't
say
anything
but
absolutely
looking
into
that.
B
So,
let's
see
that
was
Davis
question
SBA
single
page
application
capability
in
SPF
X.
There
will
be
discussions
on
that
one
in
ignite,
so
I
can't
go
to
too
much
details,
ignite
I,
think
it's
the
Wednesday's
session
or
is
Thursday.
It's
Luke
on
pads
right
after
my
session,
the
BMP
open
source
session
on
Wednesday
or
Thursday
afternoon,
based
on
the
current
schedule,
we
kind
of
talk
about
all
of
the
details
from
that
can
move
the
gear
multirow.
Can
we
get
more
detail
on
developer
tenant
I
do
not
think
so.
The
answer
is
no.
B
It's
not
definitely
part
of
the
the
developer
tenant
functionalities.
It
is
such
a
big
thing
actually,
because
multi
garrett
geo
bases
amazed
that
you
have
multiple
tenants.
So
it's
it's
not
part
of
the
developer
turn
on
set
efore
last.
If
the
plastic
part
allows
in
checks
in
javascript-
and
this
is
good
question
from
work
actually-
and
this
is
really
really
fundamental
question-
if
the
past
web
part
as
an
example
to
last
web
part
which
David
showed
and
Mike
showed
allows
interesting
JavaScript,
how
do
you
presume
the
handle
security
to
avoid
abuse?
B
Or
is
it
the
only
way
to
set
no
script
and
POC
completely
now?
The
way
part
way
to
show
saw
is
actually
a
SharePoint
framework
web
part
and
that
chiffon
framework
web
part,
which
saw,
does
actually
work
in
a
no
script
sites,
because
it
is
a
shape
on
framework
web
part,
which
has
been
a
proof
to
be
to
be
used
in
the
tenant
by
the
tenant
administrator
when
able
to
applique
was
added
on
to
add
catalog.
B
So,
basically,
in
this
case,
in
this
particular
case,
in
shire,
States
or
Dame's
on
Mike's
case
that
way
part
even
though
it
it
it,
you
can
and
potentially
add
scripts
on
it.
If
it
allows
scripting
it
does,
it
can
be
used
in
the
no
script
sites
because
it
has
been
approved
by
the
tenant
administrator
by
allowing
SharePoint
ephemeral
solution
to
be
added.
B
We,
including
that
functionality-
and
this
comes
down
on
the
on
the
fact
that
people
and
administrators
and
whoever
owns
that
catalog,
really
needs
to
understand
what
are
they
shipping
so
what's
inside
of
the
packages,
basically,
any
sharepoint
framework
solution
inside
of
those
packages
can
contain
scripts
and
the
scripts
are
potential
security
threats.
So
it's
almost
like
the
classic
farm
solutions
in
in
on-premises
you've
seriously
needed
to
know
what
buttons
out
of
the
solution,
because
otherwise
you
might
compromise
the
farm
or
it
might
compromise
latina.
B
But
that's
what
the
sharepoint
framework
gives
you
is
the
centralized
control
for
allowing
still
straights,
but
you
have
the
governance.
You
have
the
administrative
operations
you're
able
to
pull
support
for
the
for
the
components
from
the
one
centralized
location,
which
is
tab
catalan.
Now,
if
you
don't
review
your
code,
if
just
put
anything
on
on
that
catalog
here
and
your
end,
users
are
able
to
then
in
check
whatever
random
script
order.
The
solution
contains
random
stuff.
B
B
No
that's
never
gonna
happen.
Danielle
should
we
defines
as
definitely
stop
using
content,
type
hops
and
provision
content,
types
and
AIDS
individual
motor
sites,
and
this
is
food
question
from
Daniel
West
alike,
and
this
is
this
is
really
really
the
really
subject
topic.
Last
time
when
I
said
something,
there
was
like
twenty
five
comments:
immediate
thing
that
I
on
Windows
saying
yeah,
but
what
if
I
do
X
&,
Y,
&
Z,
and
what,
if
I,
do
X
&
Y
and
say?
B
That's
really,
that's
really
the
reason
why
we're
trying
to
think
through
how
do
we
message
this
properly,
but
in
the
we
are
not
really
currently
investing
on
content,
ipod
and
so
are
right
now.
Currently,
the
thinking
is
more
on
using
site
designs
using
PMP
provisioning
using
remote
provisioning
techniques
to
make
sure
that
you
have
the
native
content
types
and
metadata
available
in
the
site.
B
So
it's
our
current
create
it
now
it
has
implications
and
we
get
that
and
we're
looking
into
addressing
those
implications
like
a
centralized
control
for
those
content,
types
and
all
data
theoretically,
content
type
up
in
paper
in
slides.
Is
it's
magical?
It's
it's
pixie
dust.
It's
just
completely
awesome!
You
have
a
one
location
to
control
your
content
type
and
those
are
getting
replicated
anywhere.
The
problem
is
to
performance
implications
of
that.
B
So,
whenever
you're,
creating
a
site,
collection
and
those
content,
types
are
not
actually
there
by
default
immediately,
they
are
scratch
early,
getting
let's
say,
leak
to
that
newly
created
site
collection,
which
is
one
complaint
from
customers
and
the
other
complaint
would
be
then
well,
but
I
want
to
have
content
types.
Media
found
outside
collection.
Okay.
If
we
do
that,
then
the
site
collection
provisioning
takes
longer,
and
then
the
customers
are
complaining
that
why
does
it
take
so
long
to
create
my
site
collection?
B
So
it
is
it's
one
of
these
things
where
the
original
intention
of
content
that
are
absolutely
good,
absolutely
brilliant.
The
current
implementation
of
conduct
ipod
isn't
really
scalable
it's.
It
has
performance
issues
and
we're
looking
into
alternative
options
of
that
and
what
it
will
be.
Exactly
are
it's
not
something
which
we
precisely
even
know
so,
but
using
remote
provisioning
as
part
of
site
designs,
getting
content
types
inside
of
site
collection
or
using
PNP
provisioning
to
get
them
in
is
absolutely
a
future
proven
process.
B
Okay,
David
is
saying
that
report
will
not
show
no
script
and
no
script
site.
That
is
an
option
in
the
side
of
the
web
part
solution,
so
that's
absolutely
valid
as
well
and
Thank
You
Steven
for
defining
my
talk.
So
if
my
talk
is
on
Wednesday
to
15
to
3,
if
30
and
then
Luca
and
that
session
is
from
4
in
that
Wednesday
in
this
I
think
it's
well
I
think
it's
not
3rd
floor
of
the
conference
center
I
know
most
times
only
use
pre-built
templates.
That
is
absolutely
true.
B
B
So
what
we're
doing
more
and
more
in
the
Microsoft
and
in
the
SharePoint
is
that
we're
planning
to
use
artificial
intelligence,
we're
planning
to
do
is
automatic,
attacking
automatic
metadata,
and
then
that
would
mean
that
the
infusers
are
not
being
asked
to
actually
fulfill
the
metadata
it
is
being
set
based
on
the
user
profile.
Based
on
the
file
based
on
organization
of
that,
and
that
would
actually
solve
the
requirement
of
having
the
metadata
as
a
int
user
editable
setting
so
but
that's
really,
where
we're
heading
gradually.
So
are
we
planning
to
replicate
see?
B
They
have
no
comments,
no
plans
from
now
we're
not
well
we're
saying
that
we
do
not
invest
on
it
deprecation.
Basically,
quite
often,
people
think
that
deprecation
means
that
it's
no
longer
supported
deprecation
actually
means
that
they're
no
longer
in
investing
on
it.
So
it
doesn't
mean
that
it's
gonna
go
away
now,
we're
over
time.
I
think
we
need
to
close
as
well
and
right.
A
Media
will
be
September
13th.
That's
in
two
weeks
look
forward
to
seeing
everybody.
Then
we've
got
two
great
demos
lined
up
for
that.
The
next
general
sharepoint
development
special
interest
group
meeting
will
be
next
Thursday,
September,
6th
and
I
look
forward
to
seeing
folks
at
that
as
well.
Everybody
have
a
great
weekend
thanks
for
joining
the
call,
thanks
for
the
great
demos
today
appreciate
everybody's
time.
Talk
to
you
soon,
bye
thank.