►
From YouTube: SharePoint Developer Monthly Community Call - May 2018
Description
SharePoint Developer (SP PnP) Community call recording from 8th of May 2018. Summary of the activities happened in the past month around SharePoint development guidance and a preview of SharePoint development announcements in Microsoft Build 2018.
Demos - SharePoint Framework solutions as tabs in Microsoft Teams, Changes in PnP Provisioning schema and solution, Latest on the SharePoint Framework reusable controls (open-source controls for your solutions),
Detailed agenda an links to specific sections available from http://dev.office.com/blogs
You can download recurrent invite for the monthly SharePoint community calls from http://aka.ms/sppnp-call.
A
So
welcome
everybody.
This
is
to
share
point
a
developer,
a
community
monthly
community
column,
a
20-18
edition.
So
this
is
May
28th
and
basically
this
is
the
typical
monthly
community
call
by
we're
going
to
go
through
the
latest
news
from
SharePoint
development
site
from
an
engineering
side
or
from
a
SharePoint
community
side
we're
going
to
talk
about
some
new
announcements,
so
I'm
gonna
spill,
the
beans
so
to
say
for
some
of
the
things
which
partly
was
mentioned
already
in
yesterday
and
built,
but
we're
gonna
talk
about
those
things
in
this
call
as
well.
A
But
I
can
also
keep
few
items,
let's
say
in
secrets
and
I
do
apologize
on
that.
That's
a
request
from
marketing
I'm
gonna
mention
then,
but
I'm
not
going
to
explain
what
they
are
as
because
they
are
in
the
roadmap
slide
on
on
the
presentation,
which
will
be
then
announced
and
demoed
later
today
in
built,
which
is
getting
recorded
and
also
on
Thursday
morning
PST,
a
time
frame,
AKMs
SPF
does
SPF
X
call
the
bi-weekly
special
interest
group
call
for
SharePoint
framework.
We
kind
of
do
live
demos
on
the
new
capabilities
as
well.
A
We
do
have
three
different
demos
today,
so
first
Paolo
and
Irving.
This
is
kind
of
a
double
demo,
so
Paolo
is
going
to
talk
about
the
schema
improvements
for
the
provision
against
and
then
Ian's
going
to
talk
about
the
engine
changes
on
that
one,
and
this
relates
from
the
BMP
TMP
remote
provisioning
engine,
which
still
actually
has
a
interesting
role
in
the
future,
a
recoilless
of
the
site,
designs
and
side
scripts,
and
we
can
talk
about
that,
one
during
the
demos
and
after
the
demos
as
well.
A
But
let's
see
how
it
goes
and
good
morning
and
afternoon
and
evening
and
whatever
from
whatever
you
are
calling
this
you
know,
like
mention
I'm
calling
from
Redmond
campus
this
time
hitting
the
built
are
right
after
this
call
in
Seattle
anyway.
So
let's
actually
get
going
on
the
today's
presentation.
I
do
have
few
slides
and
try
to
minimize
this
as
much
as
possible.
So
we
will
have
time
for
live
demos
and
discussion
on
the
new
stuff
before
we
go
there
quickly,
explaining
our
SharePoint
deaf
community
thinking.
A
So
obviously
we
do
have
SharePoint
developer
group
in
the
tech
community
site,
AKMs,
SP,
dev
or
SP
PNP
community
for
discussions
and
questions.
This
is
much
better
forum
than
try
to,
for
example,
ping
me
with
your
questions
because
I
simply
do
not
scale.
So
let's
try
to
get
those
questions
and
a
foreigner
to
a
forum
where
people
can
find
the
questions
and
help
each
other.
We
do
have
a
biweekly
SharePoint
framework
special
interest
group
called
every
single
two
by
weekly
Thursdays
on
7:00
a.m.
Pacific
time.
A
We
do
understand
that
for
Pacific
people
that's
pretty
early
or
it
may
actually
might
be
a
great
time
because
it's
just
before
you
go
to
work,
so
you
can
actually
join
on
that
call
and
listen
and
see
demos
while
you're
having
your
breakfast,
who
knows.
On
the
other
hand,
it's
a
closed
bar
world,
so
it
doesn't
matter
which
time
the
course
are.
It's
going
to
be
a
long
time
for
some
people
anyway,
and
then
we
have
a
biweekly
Spanish
air
point,
a
general
deaf.
This
is
around
CSUN
rest.
Api
is
solution
designs.
A
We
talk
about
site
designs
course.
I
sharepoint
column
formatting
topics
on
this
course
bi-weekly
as
well,
so
one
call
for
sharepoint
framework
and
one
call
for
kind
of
all
of
the
other
stuff,
and
then
we
do
have
this
monthly
community
course
until
meant
to
be
more
run-through
of
what
has
happened
within
the
past
month.
Also
cool
demos,
the
latest
changes,
any
announcements
from
sharepoint
engineering
will
be
done
in
this
course
as
well
cute.
So
let's
actually
move
on
on
the
actual
topics,
so
quick
numbers
from
April.
A
We
actually
previewed
some
of
these
already
last
week
in
the
one
of
the
special
interest
group
course,
but
we
had
a
162,000
watch
times
in
minutes
what
time
in
YouTube
we're
breaking
like
1.6
million
in
a
year
which
is
pretty
decent,
there's
a
thirty
seven
thousand
visitors
in
a
key
top
for
average
two
weeks.
This
is
by
the
way
by
far
the
biggest
github
organization
underneath
office.
So
anything
else
underneath
office
isn't
nearly
as
close
as
like
one
fifth
of
the
of
the
numbers
and
visitors
in
key
top.
A
So
that
clearly
shows
that
the
SharePoint
community
is
learning
how
to
use
the
open
source
and
adapting
to
open
source
technologies
fast,
which
is
great,
obviously
what
a
lot
of
using
github
as
well
on
dos
that
might
come
our
official
SharePoint
developer
documentation.
Eight
hundred
and
twenty
three
thousand
views
I'm
crossing
fingers
to
it,
1
million
by
end
of
June.
Who
knows?
There's
it's
just
my
personal
bet
against
myself.
A
A
So
eleven
more
than
eleven
thousand
tenants
are
used
to
PMP
open
source
components
in
the
last
month,
and
this
includes
the
PMP
seasonal
component,
PMP
chase
and
the
pimp
a
PowerShell,
and
these
are
the
ones
which
we
are
tracking.
We
almost
break
approach
to
the
ten
billion
requests
with
those
components
last
month,
I
can
step
on
one,
but
not
quite
so.
It
was
super
super
close
and
most
used
to
be
used
capabilities.
The
provisioning
engine.
A
A
But
what
I
want
to
show
with
this
line
is
that
if
you're
wondering
that
should
I
move
through
SharePoint
framework
development
is
anybody
else
actually
doing
them
doing
it,
and
the
answer
is
absolutely:
it
is
by
far
the
fastest
technology
being
adapted
in
office
365
right
now,
and
it's
being
used
countless
countless
of
tenants.
These
aren't
just
the
growth
charts
without
any
actual
numbers,
to
show
you
from
last
September
until
the
actually.
These
are
from
yesterday,
so
until
yesterday,
so
how
fast?
A
Actually
that
Sunday
is
the
last
day
yes
Sunday,
how
fast
and
what's
the
growth
curve
for
the
adoption
or
usage
per
person
or
users
per
channel,
and
they
look
actually
quite
identical,
which
is
pretty
cool.
The
big
jumps
on
they
use
it
very
per
user
means
that
a
larger
customers
are
taking
these
things
to
induce
and
that
doesn't
actually
jump
to
use.
It's
pertinent
because
it's
the
same
tenant
where
there
was
already
development
happening
before.
A
But
it's
super
cool
to
see
the
adoption
being
this
fast,
and
it
clearly
shows
that
the
SharePoint
framework
helps
people
to
be
successful.
So
if
you're
wondering
should
I
actually
have
a
look
on
that
one
so
that
you
must
have
time
on
that
one.
Is
there
a
future
on
that
one
at
a
lot
that
there
is
we
built
all
of
our
stuff
native
stuff,
first
party
stuff,
out-of-the-box
stuff
in
SharePoint
Online
using
SharePoint
framework.
A
So
that
gives
you
an
indication
of
of
how
much
we
actually
trust
on
the
SharePoint
framework,
and
that
wasn't
the
case
with
the
SharePoint
adding
model.
If
we
think
about
I.
Wouldn't
say
classic
adding
model
absolutely
valid.
Still.
Adding
model
is
for
third
party
customers,
first
product
components,
and
we
in
SharePoint
engineering
we
didn't
use
adding
model
as
such
as
the
platform
which
opened
framework
at
that's
different,
because
we
we
build
all
of
our
modern
experiences
using
SharePoint
framework
as
well.
A
Super
cool
moving
on
are
things
so
reminders
on
the
documentation
and
documentation
and
guidance
AKMs
SP
div
Docs
is
the
actress
or
doorstop.
My
stuff
comes
last
share
points
last
development
or
slash
sharepoint
and
then
clicking
the
development
link
from
there,
and
this
is
the
the
consolidated
a
platform
for
all
sharepoint
development
documentation,
the
latest.
A
What
I
heard
is
that
the
image
the
end
is
going
to
be
shut
down
by
end
of
June
I'm,
not
sure
what
the
shutdown
technically
means,
but
it
might
actually
mean
that
it
will
be
actually
actually
shut
down,
so
they
mistaken
content
will
be
gone.
So
we
are
moving
all
of
the
contents
to
do
stuff.
My
stuff
come
and
you
were
able
to
also
contribute
on
this
you're
able
to
provide
issues
on
these
all
the
comments
and
everything
else
is
in
the
kids
up.
A
So
this
is
a
really
really
great
step
forward
on
making
sure
that
anybody,
if
you
find
a
typo,
you
don't
have
to
worry
about
how
to
report
the
type
or
you
can
use
a
report
to
type
or
using
the
github
tooling
or
the
the
tooling,
in
the
disturb
myself.
That
coincide,
which
wasn't
the
case
with
MSDN,
because
emma
stan
was
slightly
different
now
on
the
other
stuff
running
into
issues.
So,
if
you
run
into
any
issues
on
sharepoint
api
sharepoint
online
API,
she
went
on
premises.
A
Api
shape
and
framework
doesn't
broadcast
as
you're
expecting
or
suddenly
something
changed.
Don't
being
me
in
email,
definitely
going
to
do
that.
That's
that
doesn't
scale
go
to
the
this
issue
list.
This
is
an
issue
list
in
the
SP
dev
Docs,
so
the
kita
preparatory
behind
of
the
sharepoint
development
documentation
and
submit
an
issue
for
us.
We
triage
these
issues
typically
twice
or
three
times
in
a
week.
This
week
will
be,
however,
an
exception
because
we
have
built
and
all
of
the
people
who
should
be
triaging.
These
issues
are
quite
busy
so
to
say
so.
A
Well,
it
might
take
a
while
if
it's
a
critical
issue,
we
absolutely
jump
on
it,
because
we
we
also
need
to
scale
in
the
engineering
side,
so
we
don't
have
tens
and
tens
and
hundreds
of
guys
just
waiting
for
your
issue
gets
reported.
Unfortunately,
that
would
be
brilliant,
but
that's
not
the
case,
so
be
patient.
We
absolutely
triage
this
1.1
and
yes,
no
more
devious,
IE
most,
hopefully
not
that's.
Turning
into
a
concept,
there
is
a
meme
anyway.
A
Also
the
comments
in
SharePoint,
a
div
docks
are
open
the
dishes
in
here
and
we're
treating
them
openly
in
the
issue
list.
If
you
see
an
issue
for
example
here,
which
is
tagged
as
a
dogs
issue,
it
is
coming
actually
from
the
dogs
microsoft.com
site.
So
it's
a
comment
in
the
documentation
and
also,
if
you're
interested
on
helping
us
that's
more
than
welcome
as
well,
because
that
that
would
actually
be
highly
beneficial
for
us.
Not
just
you
to
wait
us
to
response
whether
the
community,
helping
others
with
the
issues
as
well.
A
A
That
is
actually
true:
Vincent.
That's
a
small
easter
egg
on
github,
so
on
the
use
of
voice.
I
wanted
to
I've
started
doing
this
one
three
months
and
backs
estimation
and
tracking
at
the
top-10
user
post
entries.
We
are
tracking
these
internally
in
our
engineering.
We
do
understand
that
it
doesn't
seem
like
there's
a
humongous
amount
of
always
a
progress
on
some
of
these,
but
they
are
being
tree
asked
and
evaluated
in
upcoming
roadmap
all
the
time
internally
in
into
engineering,
so
the
taxonomy
REST
API,
it
is
in
the
discussions.
A
I
cannot
promise
you
when
or
how
it
would
be
resolved,
but
we
do
absolutely
understand
that
I
say
urgent.
It
is
a
cap
which
means
Nate
to
address
at
a
single,
a
single
page
application
to
SharePoint
framework.
We
will
potentially
have
something
new
to
make
mention
on
this
one
PI
ignite
women
can
actually
show
you
something
related
on
these
topics.
A
Support
dotnet
core
of
it
sees
them,
and
this
is
something
which
is
under,
let's
say,
development
or
planning
right
now.
So
we
are
absolutely
planning
to
do
that,
because
that
just
makes
sense
to
actually
have
a
dotnet
standard
version
of
season,
so
it
will
work
in
both
classic
dotnet
and
also
in
the.net
core
and
for
other
topics.
A
A
lot
of
improvements
not
going
to
mention
them
all
in
here,
but
we
kind
of
go
through
them
and
together
with
Paulo
and
urban
slightly
later
in
this
call
also
there's
a
new
version
of
the
PM
PHAs
library,
which
is
coming
really
soon.
The
1.05
it's
going
to
be
released
pretty
pretty
soon
Patrick
is
in
a
call
and
can
confirm,
is
it
in
hours
or
within
days,
but
it's
coming
superstone
related
on
that
one.
A
By
the
way,
if
you're
using
PM,
PHAs
core
the
classic
BMP
javascript
library,
we
do
recommend
that
you
would
move
into
the
BMP,
J's
library
and
Patrick.
If
you
can
paste
in
the
the
kids
are
playing
for
that
one.
That
would
be
beneficial
because
that's
the
one
where
we
are
now
investing
more
from
a
BMP
JavaScript
side
of
the
discussion
office,
365
CLI,
updated
to
1.2
version
new
system
version
available
as
well,
and
there's
plenty
of
updates
on
the
documentation
on
the
videos
as
well.
A
Thank
you,
Gotham
Thank,
You
Patrick
as
well,
and
almost
good
I've
actually
written
that
manually
on
the
chat
window.
Thank
you
very
much.
Thank
you.
Lee
for
your
contributions.
We
again
had
a
massive
list
of
contributors
during
this
month
for
SharePoint
development
topics
in
github
or
in
our
documents
or
in
our
samples,
so
we're
running
of
pretty
soon
room
for
the
one
slide
to
actually
list
all
of
you
within
the
monthly
call.
But
thank
you.
A
Your
contributions
are
absolutely
appreciated,
because
this
is
the
one
of
the
reasons
why
all
of
the
other
office
365
and
office
services
and
products
and
now
copying
the
model
from
SharePoint,
because
we
have
the
most
powerful
community.
We
actually
all
the
time,
contribute
and
help
each
other
on
making
of
being
successful.
So
and
that
clearly
works.
And
so
thank
you
for
your
effort
on
the
company
site.
We
had
a
pretty
typical
list
of
companies
from
the
people,
but
with
the
home
company
we
have
a
permission
to
say
that
they've
been
involved
in
this
work.
A
So
if
you
contributed-
and
your
company
is
not
here,
I
will
need
to
get
an
email
from
you
with
the
logo,
which
is
saying
explicitly
that
we
are
allowed
to
show
use
your
logo
in
the
presentations.
But
these
are
basically
the
companies
who
gave
their
employees
the
opportunity
to
contribute
back
for
the
SharePoint
community.
So
thank
you.
Thank
you.
A
Thank
you
for
letting
your
employees
to
work
together
with
us
in
SharePoint
engineering,
around
topics
in
the
SharePoint
and
office,
365
on
Microsoft
site,
quite
typical
list
of
people
and
obviously
there's
two
there's
two
BMP
crew
people.
There's
engineering
people,
then
there's
people
I
popped
chairman.
Thank
you,
people
for
contributing
with
live
community
demos
as
well,
and
a
few
other
people
who
contribute
that
on
outside
of
the
let's
say,
typical
group
of
people.
Thank
you
for
your
contributions,
absolutely
valuable,
because
this
helps
on
chroma
in
the
community
as
well.
A
Now
this
is
a
new
slide,
so
20
minutes
in
okay,
we're
gonna
make
this
so
a
few
things
on
the
roadmap.
This
is
going
to
be
shown
today
in
the
in
the
build
session.
No--But
says:
I
think
it's
around
3
p.m.
today
and
basically
and
what
we
kind
of
work
next
and
certain
things
with
some
kind
of
pinpoint
here.
So
we've
done
the
LMA
PSTA
as
the
packet
entry
8
and
our
properties
gi-du.
A
This
is
a
suspect
that
you,
if
you
follow
it
up
on,
what's
happening
in
SharePoint
development
of
SharePoint
you've
seen
us
to
move
forward.
The
native
craft,
access
from
SharePoint
Greenberg
has
been
in
preview
since
spring
and
I
do
know
that
this
might
be
something
that
people
were
hoping
to
get
in
production,
as
that
is
my
SBC,
but
that,
unfortunately,
will
not
happen
so
right
now
we're
looking
into
getting
the
native
craft
access
for
SharePoint
framework
g8
around
ignite.
A
So
it's
not
going
to
happen
in
a
short
timeframe
and
I
do
understand
that
that
might
be
a
disappointment.
But
it's
better
for
you
to
know
the
current
estimate
than
being
in
an
unknown
situation.
Then,
what's
really
cool,
so
enterprise
solutions
from
SharePoint
marks
of
teams
is
gonna.
Go
in
the
preview
quite
soon
I'm
going
to
do
a
quick
demo
that
one
today
I'm
gonna,
show
that
one
live
within
after
following
slides.
A
A
It
actually
works
within
a
SharePoint
team,
not
just
as
a
SharePoint
page
but
as
a
actual
application
as
a
team's
tab,
application
hosted
directly
and
natively
from
ship
one,
so
you
actually
has
to
have
all
the
benefits
of
SharePoint
framework
available
for
you
when
you
develop
a
anything
on
a
Microsoft
themes
as
a
tab
and
that's
brilliant
one.
Implementation
works
in
both
sites
and
that's
absolutely
absolutely
great.
We're
also
looking
into
having
to
is
be
solutions.
A
Then,
surveys
from
Microsoft
teams
to
SharePoint
site,
so
we're
kind
of
doing
what
that
matched
of
teams
has
really
well
implemented,
with
with
cystitis
resolutions
that
they
can
actually
be
surfaced
on
a
SharePoint
site
that
won't
come
to
the
preview
that
soon
so
we're
looking
into
getting
that
one
in
a
functional
state.
Point
ignite,
but
it's
better
to
note
that
it's
coming,
because
it's
pretty
logical
that
we
want
to
do
that
direction
as
well.
A
There's
a
global
deployment
for
SharePoint
framework-
and
this
is
the
one
item
and
the
next
type
in
dynamic
data
in
SharePoint
framework
components
with
some
kind
of
actually
and
I.
Do
know
this
is
unfair,
but
I'm
not
going
to
actually
talk
about
in
this
call,
because
I'm
going
to
do
live
demos
on
those
on
afternoon
and
then
we're
going
to
do
live
demos
on
them
on
Thursday,
so
keeping
you
in
suspension
by
them
and
then
shape
on
framework
at
SharePoint,
2019
SharePoint
2019
in
on-premises
will
include
modern
experiences,
so
you
will
have
SharePoint
extensions.
A
You
will
have
SharePoint
framework
and
all
of
the
beauties
around
SharePoint
framework
in
on-premises
as
well.
So
technically
now
after
we
get
this
stuff
released,
you
can
implement
the
SharePoint
framework,
a
web
part
which
works
in
on-premises,
sharepoint
online
or
in
Microsoft
themes,
and
you
don't
actually
have
to
do
anything
else
to
make
that
happen.
A
Wha-Oh
on
Winston's
question
on
the
seller,
ports
and
apps
source.
That
is
have
one
thing
which
is
not
actually
on
the
roadmap,
because
we
don't
want
to
actually
yet
promise
that
it
is
absolutely
well
it's
not
in
the
public
roadmap.
We
are
working
on
getting
that
clarified.
We
had
some
resourcing
challenges
on
our
side.
In
our
team,
which
is
responsible,
SharePoint
framework,
we
will
have
a
new
member
joining
our
team
pretty
soon
and
he
is
kind
of
take
or
her.
A
He
or
she
is
kind
of
take
responsibility
of
leading
the
app
source
and
is
a
story
for
SharePoint
framework,
so
that
is
moving,
but
I
can't
promise
that
will
it
be
available
by
ignite.
So
we
absolutely
understand
why
that
has
to
be
their
couch,
so
quick
demo
and
what
doesn't
mean
that
SharePoint
framework
web
part
as
a
Microsoft
team
stamp.
A
So
basically,
if
you
just
screenshots
on
showing
this
one
and
then
showing
alive
and
then
we
can
move
to
and
the
directional
topics,
but
the
whole
point
is
that
your
right
ones
and
you
can
serve-
is
the
same
customization
in
SharePoint
as
a
wet
bar
or
as
a
tap
in
Microsoft
themes,
and
this
doesn't
mean
that
it's
a
page
in
it
Microsoft
teams,
because
that
is
actually
supported
as
well,
rather
as
a
application
natively
hosted
within
the
Microsoft
team.
So
you
don't
have
any
additional
things
and
elements
visible
on
the
page,
then
the
actual
application.
A
This
is
super
great,
because
now
we
can
use
easy
and
automatic
hosting
in
SharePoint,
so
I
don't
classically
in
Microsoft
themes,
you
create
a
manifest
and
then
you
need
to
figure
out.
Where
do
we
actually
host
the
JavaScript
files
and
assets
and
everything
else
which
shape
and
framework
you
don't
actually
have
to
worry
about
that,
because
SharePoint
framework
supports
asset
packaging,
so
you
can
create
the
SP
pkg
file,
which
includes
JavaScript
files
and
images
deployed
after
the
SharePoint
and
voila.
A
Everything
is
hosted
for
you
for
free
using
the
native
app
catalog
deployment
model
and
that's
really
really
cool
and
all
SharePoint
framework.
Tooling
benefits
I
like
including
the
asset
packaging.
All
of
the
other
benefits
are
available
in
SharePoint
framework
as
well
for
your
tabs
in
the
Microsoft
themes.
So
let's
actually
talk
about
a
quick
kind
of
a
preview
from
a
UI
perspective,
I'm
going
to
show
this
one
in
life.
A
Here's
a
bit
part
which
has
which
is
using
the
the
SharePoint
framework,
reusable
controls
from
PMPs
I'll,
just
rendering
a
list
called
legal
matters
and
you
were
able
to
see
the
information
in
the
list.
Format.
The
same
application
visible
in
marks
of
themes
would
look
somewhat
McCowen.
It
is
actual
application.
It's
hosted
from
Microsoft
from
the
SharePoint,
but
it's
actually
seen
as
a
tab
as
an
application
directly
in
Microsoft
enos,
without
any
additional
complexity
and
we're
looking
into
making
this
integration
work
in
a
way
that
Microsoft
themes
understands
the
tenant
app
catalog
in
SharePoint
Online.
A
So
it
actually
is
able
to
surface
all
the
web
parts
which
are
supporting
the
Microsoft
themes,
presentation
natively
from
the
from
the
app
catalog
directly,
which
is
super
quick
one
step
at
a
time.
But
it
takes
we'll
we'll
get
there
eventually,
and
that
is
the
right
now
to
vision.
But
I
can
show
this
an
album
of
this
one
right
after
one
or
two
slides
themes
and
sauce
a
nice
resolution
in
themes.
So
in
a
same
way,
and
as
we
have
the
ISB
solutions
in
teams.
A
Well,
obviously,
it
just
makes
sense
for
us
in
SharePoint
site
and
support
surfacing
those
ISP
solutions
on
SharePoint
site,
rather
than
introducing
an
alternative,
again
implementation
or
a
category
or
gallery
or
whatever,
let's
actually
consolidate.
So,
let's
start
this
journey
of
thinking
implement
once
and
make
the
same
customization
work
across
office
365
in
a
easiest
possible
way,
because
that
just
makes
more
sense
than
having
a
calm,
Solutions
right.
So
one
step
at
a
time
we'll
start
by
having
the
the
web
components
or
SharePoint
framework
with
pots
in
the
marks
of
team
site.
A
But
then
the
follow
up
vision
is
absolutely
get.
The
teams
is
resolutions
available
in
the
Microsoft
SharePoint
site
because
it's
JavaScript
technology.
So
why
couldn't
we
make
this
happen
and
absolutely
it
will
make
happen
cute.
How
does
it
actually
work
ancestor,
high-level,
graphical
or
logical
architecture?
So,
basically,
as
a
administrator,
you
are
deploying
SPF
X
solutions
to
that
catalog.
A
So
you
get
all
of
the
benefits
out
of
SharePoint
framework
from
an
implementation
perspective
and
also
hosting
perspective,
but
they'll
still
you're
able
to
then
surface
this
application
in
most
of
themes
and
yes
Ralph.
This
will
be
this
is
about
built,
reveal
and
it
will
have
a
video.
So
I'm
gonna
do
a
live
demo
on
this
one
on
this
afternoon
in
built,
but
let's
actually
do
a
quick
demo
on
that
one
right
away.
So
let
me
share
my
screen
and.
A
A
Okay,
Bob
Koretz,
so
let's
do
this
in
here,
so
I'm
gonna
do
this
from
a
only
from
a
privacy
perspective.
I
do
not
see
your
messages
in
dying
window
right
now,
so
I'll
have
to
come
back
on.
Then
I
only
have
one
screen
on
my
usage
when
I'm
traveling.
So
but
here
we
have
a
web
part.
This
web
part
actually
is
showing
information
from
this
list,
so
this
list
is
actually
stored
in
the
root
of
the
tenant,
doesn't
technically
matter,
but
it's
a
list
of
legal
matters.
So
that's
a
normal
document
library.
A
This
one
here,
however,
is
a
bit
part.
This
webpart
is
using
the
SPF
x,
reusable
controls
which
are
coming
from
the
PM
PSR
as
well.
Elio
has
been,
let's
say,
the
leading
engine
in
the
PMP
team
for
helping
these
to
happen.
So
let
me
get
this
page
to
an
edit
mode,
so
you
can
actually
see
that
it's
a
web
part
and
we
are
able
to
then
modify
the
web
parts
in
this
case
relatively
simple
web
part
around
showing
legal
matters
and
depending
on
an
owner
I,
can
actually
filter.
A
Configuration
settings
as
I
have
in
the
web
part
property
pain
depending
on
what,
whatever,
whatever
you
actually
have
there.
So
I
can
actually
select
filter
based
on
current,
and
let's
put
that
one.
For
example,
yes,
click
apply
and
save
and
voila
we're
adding
that
legal
matters
application
directly
on
teams
as
a
team
staff
as
part
of
your
channel.
Now,
if
I
need
to
reconfigure,
this
I
can
absolutely
do
that
by
going
in
here.
A
Do
settings
and
I
can
actually
reconfigure
this
one
with
the
settings
of
the
web
part
and
application
to
apply
that
to
be
showing
all
of
the
legal
matters,
and
here
we
go
refreshing
the
data.
What
refreshing
the
data?
Where
is
my
settings?
My
settings?
Are
they
not
saved
okay,
they
my
impact.
It
doesn't
we
matter
if
I
can
actually
make
this
lets
them
know
between
refresh
okay
doesn't
matter,
and
then
we
can
actually
that's
a
demo
effect.
It's
pretty
early
built.
A
One
thing
to
notice
here
also
is
that
if
I
to
this
side-by-side
and
there's
a
bearer
instrument
for
installment
note
in
the
status
pending
entry,
here's
my
legal
matters
actually
from
SharePoint
site,
installment
note:
how
do
we
actually
make
this
side
by
side?
It
is
too
small.
Let
me
do
this
preparer
instrument,
that's
from
owner
of
SR,
you
want
and
that's
works.
So
it's
the
first
one,
so
let's
actually
modify
that
status
brown
and
let's
modify
the
active
that
status
being
active
and
let's
modify
that
one
to
be
something
else.
A
So
here
we
go
a
modified
pending
entry
saving
saved
and
one
two
three
there
we
go
updated
on
the
application,
so
you
can
actually
see
that
it's
a
live
application,
we're
not
fooling
you
under
stem
area.
You
can
see
those
application
getting
updated
and
that's
by
the
way,
using
socket
IO
to
get
that
one
reflected
on
the
changes
in
in
this
side.
But
technically
it's
a
wet
part
which
has
been
surfacing
the
same
data
from
SharePoint
as
to
SharePoint
web
part
being
hosted
on
SharePoint
site.
A
A
We
do
have
two
other
items
to
talk
about
today
as
well,
so
let's
actually
move
on
with
in
the
agenda,
but
I
think
it's
a
super
super
super
super
excitement,
siding
and
that
we're
heading
to
this
direction
and
were
able
to
see
the
kind
of
a
consolidation
of
the
development
models
between
the
applications
as
well.
This
is
purely
like
mentioned,
but
one
step
at
a
time,
one
step
at
a
time
and
we'll
get
to
the
right
conclusions
now.
Moving
on
other
topics,
I
think
it
Paola
your
turn
on
taking
over
the
person
sure.
B
First
of
all,
before
digging
into
the
details
of
the
schema
changes,
let
me
try
to
explain
you
why
we
are
still
talking
about
an
XML
schema
nowadays,
because
maybe
someone
is
saying
what
do
you
still
work
with
XML
stuff
in
SharePoint
and
impugning
engine?
Yes,
we
do.
We
do
because
from
a
PMP
provisioning
engine
perspective,
we
all
have
the
capability
to
store
is
a
template
of
a
site
as
a
file
on
a
file
system
or
in
SharePoint
Online
in
the
document,
library
or
whatever.
B
You
want,
for
example,
a
blob
storage
folder
container,
and
when
you
do
that,
you
can
use
an
XML
file
or
a
dot
PMP
file,
which
is
an
open,
XML
document
which
inside
still
as
an
XML
document,
which
will
represent
the
full
structure
of
a
provisioning
template.
The
fact
that
we
have
an
XML
file
to
represent
a
provisioning
template
makes
it
possible
for
us
to
write
or
edit
those
templates
using
any
text
editor
which
can
be.
B
Of
course
you
just
do
the
code
or
Visual
Studio
or
whatever
else
you
like
to
use
to
do,
XML
editing
so
that
you
are
are
free
and
you
have
the
capability
to
manually
edit
and
maintain
in
your
templates.
If
you
like,
and
from
some
degrees
of
perspective,
you
can
even
copy
some
of
the
old-school
SharePoint
feature
framework,
XML
content
into
the
provisioning
template,
XML,
I'm
thinking,
for
example,
about
the
feel
definition
which
can
be
almost
be
copied
from
the
feature
framework
to
the
new
PMP
provisioning
template.
B
And
that's
why,
usually,
every
five
or
six
months,
we
release
an
updated
version
of
the
schema
in
which
we
add
more
new
capabilities
and
we
improve
the
coverage
from
a
functionality
perspective
of
the
PMP
provisioning
engine.
But
the
schema
is
just
the
beginning
of
every
new
development
in
the
PMP
provisioning
engine.
B
We
collect
in
a
branch
which
is
called
experimental
branch
of
the
people
within
schema
repo,
the
proposals
for
changes
and
pull
requests,
or
just
as
issues
in
an
issue
list,
and
once
we
are
all
ready
to
ship
to
release
a
new
version
of
the
schema.
We
define
a
new
name,
for
example
right
now
we
just
released
the
one
for
May
2018
and
we
move
the
schema
into
the
provisioning
engine
so
in
the
core
library
of
PMP.
From
that
moment
in
time
we
start
building
the
engine,
so
the
functionality
at
the
engine
level.
B
So,
first
of
all,
we
release
the
schema
and
usually
later
on
we'll
release
the
support
at
the
engine
level.
This
is
not
what
happened
this
time
because
we
decided
to
be
as
fast
as
we
could
so
we
release
the
the
May
2018
schema
together
with
the
functionalities
at
the
engine
level,
and
that's
why
today
we
will
have
a
double
discussion,
this
one
and
another
one
just
following
this
one
with
Aaron
about
the
functionalities
at
the
engine
but,
as
I
said,
usually
everything's.
B
Syncs
month
we
released
a
new
version
of
the
schema
and
usually
in
a
couple
of
months
from
them,
we
have
a
full
support
at
the
engine
level.
Right
now
we
have
quite
a
lot
of
schema
versions
out
there,
but
just
below
the
latest
three
editions
of
the
schema
so
made
13,
18,
January,
2018
and
May
2017
are
those
still,
let
me
say,
valid
or
supported.
B
Meanwhile,
all
the
older
versions
are
deprecated
and
you
should
avoid
using
them
anymore.
Of
course,
if
you
already
have
templates
XML
template
stored
somewhere,
and
you
want
to
upgrade
them
to
the
latest
version
of
the
schema.
We
have
a
comment,
let
that
you
can
use
which
is
convert
the
MP
provisioning
template.
You
provide
the
path
of
the
old
XML
template
file
and
you
select.
What
is
the
schema
that
you
want
to
target?
B
Of
course
you
can
say
two
schema
latest
and
you
will
upgrade
them
your
template
to
the
latest
version,
or
you
can
just
specify
any
specific
version
that
you
want
to
target.
But
now
let
me
dig
into
the
news
and
into
the
new
capabilities
that
we
introduced
in
May
in
the
engine
from
a
tenant
level
perspective,
which
is
an
element
that
we
have
in
the
schema
and
that
we
introduced
in
January
this
year.
B
So
you
will
be
able
to
declare
at
the
engine
level
and
at
the
provision
in
the
bed
level
that
you
want
to
automate
from
the
ALM
perspective
and
from
an
administration
perspective
the
grant
of
those
permissions
so
that
you
will
not
an
80
guy
browsing
through
the
UI
of
the
new
central
administration
of
SharePoint
Online
to
grant
those
permissions
or
use
PowerShell
to
explicitly
grant
those
permissions.
But
you
simply
can
do
that
through
the
provisioning
template.
B
You
should
avoid
to
create
a
loop,
of
course,
and
from
a
tenant
perspective,
we
still
have
an
error
capability,
which
is
the
storage
entities
capability
which
allows
you
to
store
tenant
level
settings
in
your
tenant.
If
you
need
to
reuse
them
in
multiple
solutions
or
sides
from
our
web
site
things,
we
support
the
upside,
so
you
can
specify
the
URL
of
the
upside,
which
you
wanna,
connect
the
side
when
you
wanna
associate
that
side
to
a
hub.
We
introduced
that
just
at
the
schema
level,
not
yet
at
the
engine
level
support
for
external
lists.
B
So
now
we
have
a
disk
in
my
level
the
capability
to
store
information
about
the
external
lists.
Some
other
window
changes
like
the
right
security
as
well
as
at
the
document
set
level.
We
now
support
the
XML
documents
section
so
that
you
can
add
the
custom
settings
at
the
document
set
level
if
you
need
to
push
a
little
bit
more,
your
customization
when
religion
document
sets,
and
last
but
not
least
at
clients.
B
At
pages
level,
we
have
the
support
for
the
headers,
so
you
can
keep
the
default
header
or
you
can
hide
the
header
or
you
can
update
the
background
image,
overhead
or
stuff
like
that,
and
you
can
set
the
title
of
a
time
side
page
so
that
it
will
become
the
title
of
the
page
when
you
will
publish
it
as
an
user
in,
for
example,
in
a
communication
side.
So
let
me
switch
when.
A
You
go
there
and
just
to
quick
note
on
here.
So,
first
of
all,
the
comparing
this
one
decide
designs
inside
script,
tenant
level
configuration
will
never
be
inside
designs
of
side
script
or
never
say
never,
but
this
is
one
way,
so
you
can
use
the
PMP
provisioning
engine,
the
provision
site
designs,
the
side
scripts,
which
will
then,
for
example,
have
be
available
for
end-users,
and
if
somebody
in
this
call
is
wondering
why
isn't
Microsoft
natively
supporting
all
of
this
stuff
inside
the
science
inside
scripts,
there's
actually
pretty
illogical.
Conclusion
on
that
one
we
want
to.
A
We
will
at
some
point
potentially,
but
community
is
much
faster.
An
open
source
community
open
source
way
of
working
is
much
much
much
faster
than
the
work.
What
we
do
in
engineering
and
actually
community
has
even
more
resources,
because
people
spend
every
every
now
and
an
hour
here
and
there
that
sums
up
to
be
much
more
time
than
we
have
in
engineering
to
do
all
of
the
stuff.
That's
why
the
PMP
provisioning
engine,
for
example,
is
evolving
so
fast,
comparing
to
the
site,
designs
and
subscripts.
B
For
me,
thank
you,
I
forgot
to
take
over
as
a
presenter,
but
let
me
switch
very
very
quickly
on
my
lab
environment
to
show
you
a
sample,
XML
document
built
on
the
new
schema
just
to
give
you
an
idea
of
what
I'm
talking
about
and
then
I
will
leave
the
stage
to
our
way
to
show
the
engine
in
action
with
this
kind
of
stuff.
So
let
me
know
when
you
see
my
screen:
okay
cool.
B
So
you
can
create
a
bunch
of
storage
entity
items
with
a
key
and
value
and
they
will
be
stored
as
tenant
wide
level
settings.
Moreover,
we
have
the
Web
API
permissions,
a
section
through
which
you
can
grant
permissions
for
a
specific
resource
with
a
specific
permission:
scope,
as
I
told
you
before,
so
you
can
play
around
the
settings
of
a
SP
pkg
package,
which
includes
custom
permissions
to
consume
the
graph
or
external
api's.
Moreover,
at
the
web
settings
level,
let
me
make
a
search
for
it:
web
settings.
B
Okay,
we
have
the
capability
to
provide
the
hub
site
URL
and
the
comments
on
site
pages
that
disable,
if
needed,
and,
moreover,
at
least
level
so
list
instance.
We
have
the
right
security
as
well
as
the
real
security
attribute
and,
for
example,
right
here
we
should
have
here
the
capability
to
specify
some
literature
settings
to
support
external
lists.
So
if
you
want,
you
will
be
producing
able
to
support
the
external
lists
through
the
provisioning
engine
and
again
from
a
document
set
perspective.
B
We
have
support
for
maximal
documents.
As
you
can
see
in
the
definition
of
a
content
type,
you
can
provide
an
XML
document
section
to
give
custom
forms,
for
example,
in
settings
for
custom
forms
and
last
but
not
least,
that
client
side
the
pages
we
do
support
to
the
header,
and
we
can
have
an
error
of
type
default
that
we
can
fully
disable
the
header.
B
Okay,
we
can
have
a
custom
header
with
a
custom
image
and
if
you
want
a
translate
x
and
y,
if
you
want
to
do
some
nice
animation,
when
you
scroll
your
header
across
the
page,
that's
it
from
an
XML
schema
perspective
and,
as
I
said,
it
is
already
released
and
by
default
supported
by
the
engine
and
the
fly
now
I
think
with
our
win.
We
will
see
it
in
action
with
the
provisioning
engine.
C
A
B
C
Okay,
so
there's
two
solution
to
to
fishing
templates
here
the
one
we're
looking
at
right
now,
I
already
applied.
Let
me
so
you
can
actually
see
the
full
template
there
already
applied
to.
The
second
takes
a
bit
longer
and
it's
a
bit
boring
to
look
at
the
progress
bar.
But
what
this
one
does
it's
it
uploads
in
solution,
packets
there
we
go,
then,
when
it's
done,
we
double
check
that
your
CDN
is
configured
correctly
and
we
make
sure
that
there
is
an
origin
for
the
public
CDN
here.
C
So
we
enable
the
public
CDN
office365
CDN,
and
we
make
sure
that
these
origin
is
already
configured
there.
If
it's
already
there,
we
won't
do
anything
we'll
just
leave,
but
if
it's
not
there,
we
will
add
it,
and
this
is
we
added
here,
because
if
you
enable
this
in
the
very
early
stages,
this
is
already
emotional
specified
by
default
there
and
it
is
required
for
SPF
X.
C
So
we
just
edit
that
here
to
the
template,
then
a
bit
down
here
because
in
the
solution
that
we
provisioning
here,
one
of
these
or
a
few
of
the
parts
in
there
require
access
to
the
match
of
the
carafe.
So
there
will
be
your
request
outstanding
and,
with
this
Web
API
permission
scope
that
we
defined
here
we
grant
that
request.
C
Correct,
yes
and
then
I
have
basically
an
empty
provisioning
template
here.
So
basically,
that's
that's.
What
this
template
does
it
basically
upload
two
packets
configures
the
CDN
and
grants
the
permission
then
I
have
there
this
template,
which
is
a
bit
more
complete,
and
here
I
use
a
couple
of
things
from
that.
We
already
have
been
there
for
like
months
years
already,
so,
for
instance,
here
we
permit
Erised
a
couple
of
things.
We
have
a
city
here,
a
portal
title,
the
stock
symbol
that
we
configured
as
a
parameter.
C
So
we
can
easily
refer
to
them
in
this
in
the
rest
of
the
templates
by
without
actually
writing
that
everywhere,
deep
sound
that
we
want
to
have
to
Microsoft
stock
symbol
in
our
web
parts
to
be
shown
and
with
these
parameters
you
can
even
expose
them.
If
you
use
the
powershell
commandlets,
you
can
set
them,
send
them
through
the
powershell
commandlets,
so
they
will
be
replaced
with
the
actual
values
at
provisioning
time.
C
Here
we
set
a
storage
entity
and
in
this
case,
there's
a
storage
entity
because
there
is
an
SPF
extra
part
that
requires
access
to
a
certain
list,
and
you
see
there
there's
actually
just
a
big
bunch
of
parameters
that
we
specify
here.
So
here
we
have
the
collection,
ID,
the
side,
collection,
ID,
and
then
here
we
point
to
the
host
to
decide
to
the
list
URL
after
this
called
pin
details.
Where
does
that
least
come
from?
We
provision
that
a
bit
later
here
in
the
template,
so
we
create
that
storage
entity.
C
Then,
if
we
go
here
then
here
you
see
that
I
install
the
app
into
the
sides.
Let
me
also
wrap
this
one
better
here,
I
install
the
app
and
you
see
that
we
use
a
token,
because
we
have
no
idea
what
the
ideas
that
app
will
be.
So
here
we
usually
token
to
dynamically
figure
out
the
ID
of
the
app
and
install
that
app
into
the
site,
then,
because
I'm
applying
this
to
a
hub
site,
this
we
set
the
hub
site
navigation,
which
is
effectively
just
the
global
navigation
of
the
slide.
C
So
what
we
do
here
is,
we
add
two
pages
to
the
global
navigation
being
personal
and
organizational,
and
they
point
to
these
pages
here.
Those
pages
will
be
provisioned
to
be
down
here.
So
there's
a
couple
of
side
feels
this
is
also
like
old-school
provisioning,
template
of
content
types
here
that
we
do
here
here
we
have
the
client-side
pages,
and
here
it
becomes
interesting
again.
So
here
is
the
portal
homepage
and
enable
comments
is
set
to
false,
we
publish
it,
and
then
we
specify
the
header.
C
So
basically
we
say:
okay,
it's
a
custom,
header
and
point
to
this
specific
image
here,
which
is
located
in
the
side
in
the
assets
folder
and
that's
it
and
yeah.
You
could
use
a
web
part
there
for
that,
but
now
we
have
this
built
in
and
used
to
built-in
functionality
of
a
client-side
page
with
a
header.
C
Then
we
have
a
couple
of
sections
and
then
these
two
sections
we
install
specific,
specific
web
parts
with
all
kinds
of
properties
in
there,
etc,
etc,
and
we
go
down
here
with
the
personal
page,
the
same
idea
with
no
comments
we
allow.
We
set
the
same
there
on
the
personal
page
and
a
different
set
of
web
parts.
C
Here
then,
we
have
a
couple
of
lists:
nothing
special
there
and
here
we
add
some
custom
actions
being
SPF,
X
extensions
application,
customizers,
so
the
footer
and
a
header
and
redirect
and
classification
things,
and
then
here
we
upload
the
actual
image
file
to
the
assets
folder.
So
it's
the
same
file
that
we've
referred
to
in
the
header
of
the
page.
So
that
is
the
template
in
a
nutshell,
so
let
me
show
you
the
site.
C
This
is
the
communication
site
as
it
comes
out
of
the
box
and
if
we
go
to
PowerShell
I'm
already
connected
to
it
by
I
use
some
little
extension
PowerShell
allows
me
to
see
the
site
title
that
I'm
connected
to.
In
my
prompts
there
we
go
communications,
three
and
I
say,
and
if
we
look
here
there
is
my
total
foul
and
as
a
apply
apply
PNP
provisioning
templates
portal
external
and
there
we
go.
C
We
added
a
little
initializing
engine
message
there,
because
this
step
usually
takes
a
bit
longer
and
you
might
like
is
it
doing
something?
It
actually
is
initializing
the
engine.
What
it
effectively
is
doing
behind
the
scenes.
It
was
actually
initializing
all
the
tokens,
so
all
the
values
for
the
tokens-
and
that
means
it-
connects
to
your
site
and
retrieve
some
known
artifacts
and
maps
them
into
an
in-memory
list
of
tokens.
Now
it
goes
through
all
the
artifacts
that
it
discovers
through
all
the
lists
will
go
through
the
pages.
C
A
All
of
the
work
what
Earvin
is
doing
here
is
related
on
something
which
will
announce
later
today,
actually
but
you'll
get
the
benefits
out
of
what
Irvine
is
named
in
here
pretty
soon.
So
we
can
announce
this
later
today,
but
and
availability
will
be
most
likely
in
SPC,
but
basically
this
is
demonstrating
to
enter
and
provisioning
flow
for
modern
portals,
and
this
is
actually
super
super
cool,
stuff
crossing
fingers.
Everything
works
hopefully
so.
C
No
errors,
at
least
so
that's
good,
so
it
can
already
the
little
disclaimer.
It
will
not
look
good
in
the
current
state,
but
here's
the
the
site
as
it
was,
and
if
I
go
to
the
home
page
there
we
go.
We
have
the
new
site
with
my
banner
header
there,
my
new
title:
there
is
an
extension
that
just
throws
up
and
dialogue.
There's
my
wedding
web
part
sets
you
Helsinki.
There
is
my
stock
symbol
with
Microsoft,
etc,
etc.
C
Now
there
is
a
little
issue
with
half
sites
that
I
personally
find
a
bit
annoying,
but
that's
how
it
is
you
seen
has
not
been
updated
and
reloading.
Its
is
also
not
that
I
would
actually
do
that.
Ok,
sometimes
even
a
reload
doesn't
update
it,
but
there
we
go.
There's
my
navigation
here
and
if
I
go
to
personal,
you
will
get
a
different
different
page
with
different
functionality
in
there
and
etc.
So
this
is
the
the
new
add.
C
The
new
schema
at
work
with
the
new
functionality
in
there,
and
so
what
I
didn't
demo
here
is
the
facility
to
provision
side
designs
inside
scripts.
But
this
power
mentioned
it's
there
and
that's
actually
a
great
way
to
like
sort
of
pre
provision,
your
tenant.
So
you
have
a
say
yeah,
but
you
say:
you're
consulted.
You
get
a
new
customer
with
a
tenant.
A
Ok,
so
we're
gonna
go
slightly
late
today
and
you
apologize
on
that
one,
but
let's
switch
to
Elia
and
have
a
quick
look
on
the
latest
on
the
SPFs
country
rose.
Thank
you,
Irving
Thank,
You
Paula.
It's
good
to
see
the
role
of
the
of
the
engine
as
well
and
like
mention
the
engine
will
be
more
and
more
moving
to
this
kind
of
an
overall
tenant
level
configuration
set
up,
so
you
can
use
that
for
setting
up
your
tenants
test,
announce
really
easily
and
then
side
to
science
inside
scripts.
A
If
you
prefer
to
use
them,
you
can
absolutely
use
them
inside
of
the
tenant
settings
as
well,
but
Elia
is
going
to
talk
about
slightly
on
the
SharePoint
framework
control
still
and
we'll
get
this
recorded.
The
video
will
be
out
in
24
hours.
Typically,
if
you
need
to
drop
on
the
hour,
but
I
do
take
it
away.
D
Okay,
do
you
see
my
screen?
Okay,
okay,
perfect,
so,
first
of
all,
I
won't
take
it
very
long.
I
can
say
that
we
just
have
a
new
version
out
of
the
PMP
property
controls,
so
just
before
this
meeting
I
published
them.
But
what
are
these
reusable
controls?
They
will
give
you
a
lot
of
benefit
to
your
projects,
but
what
exactly
are
they?
So?
D
First
of
all,
there
are
two
projects:
two
projects,
one
for
property
bank,
since
property
controls
like
a
date
picker
like
a
term
picker
like
a
list
bigger,
but
we
also
have
controls
for
the
content.
Some
of
your
solutions,
like
the
vampire
title,
you
would
probably
know
every
web
part-
is
using,
which.
D
A
first
party
control,
which
we
converted
to
a
third
party
control,
which
we
now
can
use
within
our
solution
and
within
your
solutions
as
well.
We
have
the
placeholder,
which
shows
you
a
placeholder
that
you
still
have
to
configure
your
web
part
and
since
the
latest
release
since
release
a
bundle
3.0,
we
have
now
also
a
taxonomy
picker,
which
you
can
use
within
your
web
parts
and
not
only
for
the
property
pain
but
also
for
within
your
comfort
zone
and
also
a
listicle
which
is
also
available.
D
I
will
show
the
latest
ones
which
just
became
available.
So,
as
mentioned,
we
just
released
version
1.6
0.9
s
ago.
It
should
be
one
hour
because
we're
running
now
we're
already.
In
this
version
we
have
a
new
property
filled
collection
data
which
allows
you
to
add
a
list
state
of
this
configuration,
but
list
configuration
like
a
JSON
object,
representation
for
configuring.
Any
types
of
data
you
need,
within
the
other
part,
it's
kind
of
flexible
you
define
which
fields
you
want
to
insert.
We
support
strings,
Julian's
numbers
and
dropdowns.
We
also
have
the
property
field
order.
D
You
can
define
a
couple
of
items
and
you
can
define
the
own
order,
the
order
by
just
dragging
and
dropping.
We
have
now
also
a
swatch
color
picker,
and
we
have
a
couple
of
announcements
being
made
and
some
fixes
for
the
react
controls.
These
are
the
controls
which
can
be
used
within
your
components
or
within
your
back
part
special
on
the
page
and
since
version
3
we
have
the
taxonomy
picker
and
the
list
speaker
and
a
couple
of
issue
issues
that
were
fixed.
So
how
do
you
get
started?
D
First
of
all
to
projects
you
have
to
install
them
by
a
NPM,
of
course,
because
we're
running
s
VFX
projects
and
we
do
it
under
the
F
PMP
scope,
and
we
have
to
want
to
projects
for
that.
Spf
expert
of
controls
and
the
SPF
X
controls
3x
I'm
not
going
to
tell
more
about
that
I'm
just
going
to
dive
into
the
demo,
which
is
more
fun
than
just
watching
slice.
So
everything
lives
on
github.
So
if
you
have
issues
just
go
to
our
issue,
list
add
them
there
and
we
also
have
documentation.
D
So
documentation
can
be
just
be
found
on
the
top
of
our
github
repository
and
the
documentation
is
somewhat
similar
for
both
projects,
although,
depending
on
which
controls
you
are
going
to
use
it
sighs
it's
a
bit
different.
So
first
things.
First,
installing
everything
installing
is
quite
simple,
but
once
you
got
the
installs
there's
one
thing
you
need
to
configure
and
that's
the
localization
file
which
need
to
be
specified
in
your
conflict.
Adjacent
file.
We
have
couple
of
issues
are
ready
for
from
people
that
forgot
it.
This
is
one
thing
which
is
on
the
home
page.
D
That's
why
we
had
a
bit
over
there
because
before
it
was
somewhere
else,
so
less
confusion.
This
is
the
one
thing
you
have
to
ask,
and
once
you
have
a
desk,
you
can
start
using
them.
So,
let's
I
in
the
real
demo,
I
created
two
small
webparts
like,
for
instance
this
one,
my
first
one.
This
is
an
empty
web
part,
and
actually
it's
not
really
building
everything.
Okay,
let's
not
bother
with
it.
It's
not
floating
the
image
at
the
top.
So
probably
something
is
failing
behind
the
scenes.
I
promise
you
I
parrot.
D
So
what
are
we
going
to
do?
I'm
first,
going
to
show
the
new
collection
data
picker,
and
so
what
I'm
going
to
do
is
add
it
over
here
inside
my
lab,
our
file
and
everything
can
be
found
within
the
documentation.
So
the
first
thing
you
have
to
do
is
import
references
to
the
property
fields,
collection
data.
Once
you
insert
these
references,
you
can
start
using
it
as
within
your
web
parts
like
this,
so
the
property
fields,
collection
data-
contains
some
labels,
a
value
which
is
specified
within
your
web
part
and
then
a
couple
of
fields.
D
These
fields,
that's
the
business
logic
you
defined.
So
for
me,
for
my
part,
I
currently
define
a
title,
a
description
and
an
image.
So
what
I'm
going
to
do,
I'm
going
to
create
a
slideshow
or
the
slideshow
is
already
created,
although
it's
not,
we
have
loaded
because
there's
nothing
in
my
property
pain
at
the
moment.
D
I've
already
add
another
field,
which
is
the
number
fields
we
have
a
text
fields
within
s,
P
of
X
that
the
text
field
doesn't
form,
allows
you
to
insert
numbers,
but
the
problem
is
it's
always
returned
to
use
strings.
So
then
you
have
to
parse
it
to
an
integer.
This
field
is
automatically
going
to
give
you
a
number
so
that
you
don't
have
to
convert
it
again.
D
So
in
this
collection,
data,
picker
I
can
add
some
things
like,
for
instance,
a
title
and
I
just
come
in
to
copy
it
from
my
list.
So
that's
I,
you
don't
have
to
see
me
typing.
We
can
add
new
things.
We
can
remove
new
things
that
we
just
add
others
in
case
you
don't
want
it
anymore
and
that's
last
one
so
that
we
have
a
couple
of
things.
Oh
that's.
D
C
D
This
it
will
show
my
banner
it's
rotating
every
two
seconds:
I
can
change.
The
interval,
I
can
say
every
five
seconds
and
if
I
say
something
like
this
is
a
test,
you
will
automatically
see
that
it
shows
you
and
notification
hey.
This
is
actually
not
number
so
convert
it
back
to
a
number,
like
instance,
one
or
fine.
If
you
click
on
apply
now,
this
slideshow
is
going
to
run
every
five
seconds.
So
it's
going
to
change
every
five
seconds.
So
that's
the
collection
data.
D
C
D
Show
the
controls,
so
in
version
1.3,
dot
0.
We
got
two
great
controls
added
to
the
list
picker
and
the
what
was
the
delay
speaker
in
the
certificate.
So
let's
open
the
list
speaker
and
that's
good
and
that's
the
list
picker
and
the
third
picker
in
there.
So
at
the
moment
we
don't
have
anything
in
here.
So
same
thing.
First,
you
have
to
include
your
references.
Like
friends.
Is
the
list
picker
and
then
you
have
to
add
the
codes
like,
for
instance,
for
the
listpicker.
It's
this
thing.
D
D
Templates
for
this
one
I
configured
it
to
only
retrieve
all
the
document.
Libraries
or
all
the
libraries
includes
all
the
hidden
libraries,
no
or
yes
or
false.
Do
you
want
to
have
a
multi-select
form?
That's
something
you
can
also
do.
Let
me
set
my
screen
like
that,
and
then
we
can
see
the
difference
so
now.
I
have
a
single
selection.
I
might
specify
this
the
truth
and
our
wait.
Until
my
project
is
reloaded,
then
it
should
be
able
to
now
do
a
multi
selection
like
this
and.
A
One
thing
you
know
sorry
one
thing
to
notice
here,
because
somebody
might
be
always
turned
wondering
so:
what's
the
difference
between
these
and
obviously
why
fabric
well,
the
difference
is
that
obviously,
our
fabric
is
generic.
This
one
understands
that
it's
in
SharePoint,
so
you
don't
actually
have
to
query.
You
don't
do
the
rest
queries
we
do
that
all
for
you
inside
of
the
controls,
that's.
D
So
what
we
can
also
do
is,
we
can
also
add
the
texture
picker.
This
is
a
picker
which
is
also
converted
from
the
property
pane
controls
over
to
the
react,
controls
and
that's
also
a
fair
point
from
VESA.
We
are
using
office.
You
have
fabric
for
this,
so
that
means
that
we
have
a
dependency
on
react,
so
these
controls
can
only
be
used
in
react.
That's
why
also
the
project
is
called
react
controls
what
we
are
going
to
do
in
the
future.
D
We
don't
know
yet,
but
now,
with
angular
version,
six
coming
out
and
or
that
came
out
last
week
and
angle
elements,
it
could
be
that
there's
a
new
project
coming,
we
don't
know
yet.
So
what
can
be
done
with
a
taxonomic
picker
is
a
similar
approach.
Life
you
have
in
the
lists
like
you
can
search
HR,
but
you
can
also
click
on
this
thing,
and
now
we
have
our
basic
taxonomy,
picker
and
even
here
I
can
say,
I
teach
and
you
see
that
it
immediately
switch.
I
can
say,
ok,
which
leaves
me.
D
The
document
libraries
and
I
see
that
there
are
two
items
linked
with
IIT
in
my
document.
Library
I
didn't
want
to
show
any
other
functionality,
because
the
demo
that's
already
gave
with
the
big
teams.
He
already
showed
the
list
you
apart.
So
then
I
quickly
did
something
else
so
that
the
list
view
web
part
has
been
removed
and
some
other
kind
of
functionality
was
added
during
this
meeting.
D
So
I
hope
that
you
see
some
real
advantage
of
using
these
controls,
because
these
controls
can
really
speed
up
everything
and
you
don't
have
to
reinvent
the
wheel
every
knowing
them
as
just
use.
What
is
available
to
you
if
there
are
questions,
if
there
are
feedback,
if
there
are
issues
just
give
to
our
issues,
submit
them.
Ids
are
always
welcome.
D
A
Because
this
is
really
this
is
where
the
community
can
significantly
help
each
other
in
the
future,
because
this
helps
significantly
on
reducing
your
development
time,
because
you
don't
have
to
implement
the
wheel
once
again
and
again.
Luckily,
I
mentioned
now
we
do
apologize.
We
went
the
way
on
over
the
time
because
of
the
additional
mics
of
teams
demo,
which
I
did
I,
do
apologize
on
that
one,
but
the
recording
will
be
available
within
24
hours.
A
Thank
you,
everybody
for
joining
Thank,
You,
Paula
or
even
an
Elio
for
your
great
demos,
all
post
social
media
notes
when
the
video
is
available
and
for
those
who
might
be
join
me
on
the
afternoon
on
the
build
session
on
other
ones
who
are
not
in
built.
We
kind
of
do
live
demos
and
VFX
stuff
on
Thursdays
special
interest
group
call,
so
I'm
gonna
do
two
similar
demos.
What
I'm
doing
in
builds
related
on
the
new
stuff
on
the
SharePoint
framework.
Thank
you,
everybody.
Thank
you
for
contributions.