►
From YouTube: SharePoint Developer Monthly Community Call - June 2018
Description
SharePoint Developer (SP PnP) Community call recording from 12th of June 2018. Summary of the activities happened in the past month around SharePoint development guidance, roadmap updates, future plans for the SharePoint Framework.
New PnP Core Team members and changes in the GitHub plan for the open-source projects.
Demos - Introduction of SharePoint Starter Kit and PnPjs Taxonomy API support,
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
shabaan
financial
practices.
It's
a
monthly
community
called.
So
this
is
the
June
2018
edition
we've
been
having
this
monthly
community
call
since
December
2014.
So
this
is
quite
quite
a
few
years.
Actually,
we've
been
doing
a
SharePoint
deaf
community
calls
and
try
to
promote
the
open
source
and
sharing
is
caring,
ad
terminology
and
an
slogans
with
the
sharepoint
developer
group.
Now
in
these
monthly
community
calls.
A
This
is
mainly
for
going
through
what
has
happened
within
the
last
month
and
also
talk
about
certain,
let's
say
wider
specifics
around
the
ship
on
development.
So
today
we're
going
to
talk
about
slightly
numbers,
we're
going
to
talk
about
what
has
happened
within
Mattoon
and
what
was
part
of
the
tune
released
who
contributed
as
part
of
the
tune
release
and
what
companies
were
also
involved
in
the
in
the
churn
release.
They
will
talk
about
certain
other,
let's
say
news
and
areas
around
the
community
work
and
announcements
and
Road
math
topics.
A
We
also
have
two
different
demos
coming
up
today
and
let
me
actually
flip
the
slide
so
why
a
first
demo
will
be
coming
from
Patrick
Rodgers.
So
Patrick
has
been
leading
the
effort
for
SharePoint
about
to
be
an
PHAs
library
and
BM.
Phas
is
a
great
great
JavaScript
library,
offering
you
a
fluent
API
getting
access
on
the
SharePoint
REST
API.
So
you
don't
have
to
remember
what
is
the
rest
URLs
and
all
of
that
you
can
use
the
fluent
API
from
Patrick
and
the
team
behind
off
the
PMP
chase
and
accessing
information.
A
One
of
the
big
things
around
that
one
inmate
was
the
announcement
of
fluent
API
for
taxonomy
and
that's
huge
because
there
is
no
rest
api
for
taxonomy
api
and
sharepoint
online,
but
the
PM
phas
is
now
offering
you
an
easy
way
to
get
accessed
on
the
taxonomy
information
using
kind
of
the
fluent
way
of
getting
access
on
the
API.
So
you
can
do
Kroop.
A
That
term
set
the
terms,
and
then
you
can
access
all
of
the
terms
within
the
particular
terms
that
Patrick's
going
to
demonstrate
that
on
later
today,
and
then
we
kind
of
talk
about
out
that
the
last
demo
or
the
second
demo
is
around
to
share
on
star
tickets.
We're
going
to
talk
about
that
one
as
well.
A
It
is
a
great
starter
kit
for
showing
you
how
to
extend
the
crate
come
out
of
the
box
communication
sign
by
adding
additional
webparts
and
extensions
and
how
to
how
to
create
really
portal,
like
experiences
using
God
at
the
Box
communication
site,
by
adding
additional
certain,
let's
say,
customer
specific
customizations
or
extensibility
on
top
of
it.
This
is
really
a
first
version
of
that
release.
We
will
keep
on
evolving
that
one
as
we
move
along
in
this
journey
now
quickly
and
there's
always
new
people.
A
Turning
on
this
course
so
quickly
explaining
the
model,
what
we
have
on
the
shipment
developer,
community
or
the
SharePoint
and
developer
topics,
our
community
is
actually
pretty
insanely
active.
To
be
honest,
we
have
different
selections
on
different
ways
of
engaging
with
the
community.
You
can
use
the
SharePoint
developer
group
in
Microsoft
Tech
community
by
going
spdf
our
SP
PNP
community
URL.
You
can
join
our
bi-weekly
SharePoint
framework
community
core.
Where
we
talk
about
specifically,
what's
new
on
SharePoint
framework,
we
have
SharePoint
framework
demos
and
all
of
that
stuff.
A
Then
we
have
a
separate
bi-weekly,
SharePoint
general
dev
call
and
in
this
cope
going
to
talk
about,
let's
say,
maker
stuff
like
flow
and
power
apps
and
how
they
how
they
associate
with
with
SharePoint.
We
talk
about
the
per
site,
provisioning.
We
talk
about
the
MP
PowerShell
and
all
of
that
stuff
as
well,
and
then
we
have
this
monthly
community
course
where
we
go
through.
What
has
Bulow
happened
within
the
past
month,
and
then
we
have
also
a
demos
in
this
course
as
well.
So
all
of
these
things,
you
don't
have
to
join.
A
All
of
these.
You
can
join
all
of
this.
If
you
have
availability
and
you
can
choose
what
is
your
interest
and
you
can
choose
which
of
the
course
you
want
to
actually
join
the
easiest
way
to
keep
kind
of
up-to-date
on
what's
happening
in
the
SharePoint
dev
is
to
join
once
a
month
in
the
monthly
community
call
if
you
don't
have
availability
to
join
the
other
course
or
what
is
a
participate
on
the
discussions,
other
ones
now
in
May
just
quickly
showing
some
numbers
as
well
in
May
from
the
SharePoint
developer
community
and
perspective.
A
We
had
one
hundred
and
fifty-seven
thousand
watts
times
in
YouTube.
We
haven't
actually
released
that
many
new
videos,
except
the
community
call
recordings
which
have,
by
the
way,
create
videos
as
well.
So
all
of
these
demos
and
all
of
the
stuff
is
getting
released
and
shared
at
within
24
hours
after
the
community
call.
So
if
you
have
a
colleague
or
somebody
who
missed
this
call-
and
they
would
like
to
see
the
demo-
which
we
do
this
call
or
you
want
to
go
back
and
re,
see
what
has
been
released.
A
You
can
always
go
to
our
YouTube
channel
and
have
a
look
on
the
old
calls
there,
and
there
was
twenty
seven
thousand
views
in
YouTube
with
a
pretty
decent
number
for
a
monthly
views
in
the
Keith
hump.
We
have
thirty-eight
thousand
unique
visitors
for
the
past
two
weeks
or
average
in
two
weeks
in
May
and
one
hundred
and
seventy
two
thousand
views
and
github
altogether,
which
is
quite
nice
number
as
well.
A
So
people
are
finding
more
and
more
our
open
source,
tooling
our
open
source
samples
and
things,
and
they
know
how
to
communicate
together
with
engineering
as
well.
In
the
docs
of
Microsoft
that
come
with
the
BMP
initiative,
coordinated
by
engineering
also
owns.
We
had
eight
hundred
and
ninety
eight
thousand
views,
so
we
just
barely
missed
the
eight
nine
hundred
thousand
views
in
the
share
in
the
dust
of
knife
so
from
a
SharePoint
deaf
sign,
but
we're
looking
into
hitting
and
the
1
million
marker
pretty
soon.
A
These
are
reusable
open-source
components
which
are
being
I,
created
and
coordinated
or
developed
by
the
community
to
cater
and,
for
example,
the
PMP
see
some
core
and
BMP
chase
and
BMP
PowerShell,
and
these
were
used
in
to
more
than
12,000
tenants.
They
generate
at
ninety-nine
point
nine
billion
requests,
so
we
didn't
quite
break
the
ten
billion
again
we're
super
close
on
that
and
the
most-used
capability
is
the
provisioning
engine,
so
the
remote
provisioning
engine
for
giving
you
templating
capabilities
for
sharepoint,
online
or
on-premises
as
well.
A
Now
often,
people
are
also
interested
on
what
about
the
new
thing?
The
new
model,
the
latest
thing
in
SharePoint
Online,
which
is
shape
and
framework-
is
it
actually
catching
fire?
Do
I
really
need
to
learn
this
new
stuff?
Well,
yes,
you
do.
A
lot
of
our
community.
Members
are
already
learning
this
stuff
and
they're
using
widely
my
SharePoint
framework,
so
SharePoint
framework
is
by
far
the
most
used
customization
model
in
office,
365
or
Microsoft
365.
A
A
Its
pertinent,
what's
actually
interesting
is
that
the
users
per
tenant
is
being
more
exponential,
then
the
users
per
user-
and
this
is
indicating
already
that
more
and
more
people
are
using
deff
tenants,
so
they're
learning
how
to
do
development
of
Fairmont
framework,
and
that
will
be
then
soon
visible
on
the
other
side
of
other
side
of
the
charts
as
well.
Now
a
few
reminders,
documentation
and
guidance,
a
kms
s
PDF
doc.
So
this
is
the
documentation
platform.
A
Like
mentioned,
we
almost
hit
nine
hundred
thousand
views
on
May
people
can
find
the
relevant
and
up-to-date
documentation
in
here.
There
are
some
pages
which
are
not
quite
up
to
date
and
if
you
find
some
issues
on
the
documentation,
please
open
up
an
issue.
Add
a
comment
on
the
page
and
saying:
well:
I,
don't
agree
on
this
one.
We
should
get
this
one
updated
after
data,
so
we're
able
to
actually
then
go
back
and
view
the
page
and
then
potentially
update
the
page.
A
If
there's
an
issues
with
the
page,
all
of
the
SharePoint
framework
guidance
is
here,
there's
plenty
of
tutorials
how
to
get
started
on
the
stuff.
There's
plenty
of
recommendations
and
and
video
references
in
these
materials
as
well,
and
we're
looking
into
adding
additional
training
material
here
as
well
in
the
future.
A
Now
the
kind
of
related
thing
if
you're
running
in
the
SharePoint
developer
topic
issues,
please
please,
please
let
us
know
in
shape
on
the
engineering,
we're
highly
interested
on
helping
you
on
trying
to
figure
out
what
Oh
strong
within
your
api's
or
within
your
solutions,
and
if
you
would
call
the
normal
shape
point
support
they.
Unfortunately,
the
normal
standard
support.
They
do
not
actually
provide
support
for
developer
questions,
and
that's
why
we
have
opened
up
this
issue
list
and
espied
abducts.
A
We
are
still
slightly
catching
up
on
the
on
the
opened
issues,
since
the
may
was
super
crazy
for
us
to
pretty
big
conferences.
So
we
kind
of
a
slightly
are
falling
behind
following
up
on
what's
happening,
but
we're
catching
this
relatively
soon.
But
the
whole
point
is
that
you're
able,
if
you
run
into
an
issue,
you
can't
explain.
What's
the
issue
you
can
go
here,
submit
an
issue
and
we'll
have
a
look
on
it.
A
Please
please
please
go
to
the
AKMs
SP
dev
user
voice,
please
let
us
know-
and
please
add,
input
on
the
on
the
actual
comments,
what
we
are
also
interested
and
not
just
around
the
number
of
votes,
but
if
possible,
you
can
always
add
a
comment
there
and
add
some
sort
of
a
description
on
your
business
case
as
well.
Why
are
using
the
feature?
A
Why
is
certain
thing
important
for
you,
because
that
helps
us
on
prioritizing
the
needed
capabilities
for
SharePoint
development
platform
in
the
future,
which
is
obviously
important
for
us
as
well,
and
even
though
we're
Microsoft,
we
do
not
have
an
infinite
resources,
which
is
a
pity.
It
would
be
awesome
if
it
would
have,
because
we
would
be
able
to
help
all
of
your
people,
but
we
can't
always
do
that.
So
we
need
to
prioritize
our
time
and
our
resources
based
on
the
people
and
based
on
the
the
entries
and
about
what
you're.
A
Having
now
excuse
me
for
a
quick
break,
because
I
I
needed
to
actually
get
a
picture
on
the
number
of
attendees.
We
are
quite
away
making
an
all-time
record
on
the
participant
numbers
in
this
core,
which
is
pretty
cool
with
just.
There
was
201
participants
in
the
course
one
minute
ago,
and
now
we're
gonna
slide
it
down.
That's
one
good
and
the
tool
release
went
live
yesterday
as
tuned
release.
A
There
was
numerous
existing
samples
which
were
upgraded
to
one
point,
four
point:
1
or
1.5
version
already
at
this
point,
there's
quite
a
lot
of
updated
documentation
and
guidance
and
that's
moving
along
quite
nicely
and
as
we
can
see
that
we
are
getting
quite
a
lot
of
views
and
those
as
well,
which
seems
to
indicate
that
people
are
finding
their
valuable
and
they
will
say,
updates
on
the
reusable
SharePoint
framework
controls.
And
this
is
something
which
just
just
to
kind
of
promote
that
as
well.
A
It
is
a
great
way
of
reducing
to
amount
of
work
you
need
to
actually
implement
in
your
web
part.
So
have
a
look
on
the
PMP,
reusable
SPF,
X
controls,
and
these
aren't
there
to
reduce
the
amount
of
resources.
What
you
need
to
invest
and
we
in
shape
on
the
engineering
we
are
using
this
SharePoint
BMA
SPF,
X,
reusable
control
as
a
way
for
sharing
our
knowledge
and
our
internal
use.
Controls
for
you
and
we're
looking
into
doing
this
within
the
next
quarters
as
well.
A
So
we're
adding
additional
controls,
additional
capabilities
for
you
to
take
advantage.
So
you
don't
have
to
always
start
from
scratch.
Implementing,
for
example,
property,
paying
controls
or
advanced
controls
for
some
of
your
web
parts
on
the
PMP
component
side,
they
will
say
new
at
one
point
one
version
of
the
MBTA's
library.
A
On
the
other
section,
the
SharePoint
starter
kit
we're
going
to
talk
about
that
one
in
few
slides
a
slightly
more
detailed
and
we
will
have
a
live
demo
on
that
one
for
from
Paulo
or
me,
depending
on.
If
Paulo
can
actually
joined,
he
has
a
family
priorities
which
he
might
or
might
not
be
able
to
actually
join
on
this
call,
but
that's
fine
now
and
then
we
had
a
new
version
of
Office
365
CLI,
which
is
a
cross-platform
comment
line
act
tool
which
will
you
be
to
can
also
actually
nowadays
use
also
for
upgrading.
A
Your
one
point
four
point:
one
version
of
SharePoint
for
a
number
of
solutions
to
one
point:
five,
so
there's
nice
automation
included
in
there
to
help
you
on
the
journey
of
upgrading
to
the
latest
version
now
and
oversee
new
version
of
client-side
object
model
which
is
good
and
updates
on
the
s
PDF
documentation
in
general
to
be
a
full
list
of
contributing
contributors
is
available
in
here.
So
thank
you
once
again
tremendously
for
your
contributions
within
the
dismount
you've
been
highly
helpful
on
making
sure
that
other
people
can
be
successful
within
their
works
as
well.
A
A
So
let
me
click
in
there
and
these
are
the
actual
companies
and
then
which
we
have
a
permission
to
actually
show
or
permission
of
the
logos
of
those
companies
who
be
who
the
people
have
worked
for
who
contributed
on
the
list
monster
on
the
in
2018
released.
If
your
name
is
on
the
previous
slide,
but
your
company
logo
is
not
here.
Please
share
your
company
logo
for
the
future
preference
and
we're
happy
to
get
your
company
logo
mentioned
in
here.
A
A
Good
now,
Microsoft
site,
obviously
there's
a
big
list
of
people.
This
isn't
the
full
list
of
people
who
have
participated
on
the
communica
on
our
development
topics
and
the
engineering.
But
these
are
the
people.
Who've
been
actively
involved
in
the
community
contributions
or
community
side
of
the
story
from
Microsoft
as
well.
Some
of
them
are
from
shape
and
engineering
like
I
am.
A
Some
of
them
are
not
so
they're
from
our
internal
community
side
of
the
story
as
well
now
few
additional
things
so
next,
that's
kind
of
the
summary
on
what
has
happened
in
June,
just
few
news,
which
I
wanted
to
actually
raise
still
on
discussion
before
we
go
to
the
Patrick's
demo
around
the
taxonomy
API.
As
with
the
super
cool
as
well,
there's
one
two
big
things:
what
we're
planning
to
do,
or
one
news
and
a
big
thing,
what
we're
planning
to
do
within
the
VMP
well
in
the
SharePoint
deaf
community
sign.
A
First
of
all,
we
do
have
two
new
community
members
in
the
PNP
core
team.
We
haven't
had
a
yet
time
to
write
the
blog
post
about
this
one,
but
Chris
Kent
and
Stephan
Bower
I
have
been
moving
into
the
PNP
core
team
members,
team
and
they're,
helping
us
and
they're
leading
their
own
efforts
under
the
PNP
or
SharePoint
dev
on
Perella,
so
Chris
Kent
is
leading
the
effort
on
the
well
column,
formatting
list
formatting
web
part,
SP,
FX
web
part
side
of
the
game.
A
Chris
has
been
extremely
active
on
that
side
and
helping
on
on
others
being
was
highly
successful
on
there
and
then
Stefan
Bower
is
starting
to
lead
for
around
the
custom,
human
template
or
extension.
So
we
are
building
a
open-source
extense
extension
on
top
of
the
other
two
box.
Human
templates
for
SharePoint
framework
and
Stefan
is
going
to
lead
that
effort.
The
intention
is
them
to
provide
native
support
for
angular
elements,
view
handlebars
and
whatever
comes
to
mind
from
that
perspective.
A
So
these
are
Kristin
and
ask
Stefan
is
now
part
of
the
extended
MVP
team
for
PMP
crew,
not
being
big
core
team,
whatever
we
want
to
call
that
I,
don't
even
know,
but
they
own
stuff
in
the
in
the
SharePoint.
Deaf
community
side
or
open
source
community
side.
The
second
thing
on
what
we're
looking
into
doing
is
that
this
is
more
on
a
curry
day
on
on,
let's
say,
what's
open
source
and
what's
actually
natively
from
the
SharePoint
engineering.
A
Actually
all
of
them
will
be
relocated
under
the
BMP
of
github
organization,
and
this
is
just
to
make
sure
that
people
understand
the
difference
between
what's
part
of
the
SharePoint
engineering,
let's
say
work
and
what's
part
of
the
community
open-source
work.
So
this
should
help
on
then,
let's
say
defriend
da
ting
that
it's
an
open
source
initiative.
It
is
a
community
driven
initiative,
so
it's
located
in
the
side
of
the
PNP
organization.
A
Obviously,
these
are
both
sites
to
SharePoint
organisation
and
PNP
organization,
as
github
are
being
managed
by
the
same
group
of
people,
but
this
is
just
a
different
date.
Let's
say
the
location,
if
you
have
forked
already
a
repository.
This
does.
This
is
completely
seamless
for
you,
so
it
doesn't
actually
break
anything.
Github
is
a
magical
platform,
and
so,
even
though
we
will
relocate
some
of
the
repositories
cross,
the
organization,
so
they
take
to
make
Li,
have
a
different
URL
or
a
new
URL
github
is
fixing
all
of
that
those
in
the
requests
automatically.
A
The
second
big
thing:
what
I
wanted
to
quickly
mentioned
around
the
May
announcements?
The
may
thing
may
have
been
extremely
busy
for
engineering
people
to
SPC
and
other
conferences,
and
also
for
the
BMP
crude.
So
one
of
the
big
things
which
we
invested
heavily
time
and
we
announced
in
the
SBC-
was
the
SharePoint
starter
kit,
but
just
want
to
make
sure
that
everybody
has
seen
this
and
they
are
aware
of
this
work
as
well.
A
So
the
PMP
astrologist
is
a
a
starter
kit
for
modern
experiences
and
basically
a
kms
s/pdif
starter
kit
is
the
URL
where
you
can
find
the
key
top
location
where
you
can
find
source
code,
provisioning,
automation,
ready
to
package
SP
pkg
file,
so
you
can
easily
take
some
of
these
web
parts
into
a
use.
This
basically
is
automating
or
provisioning.
A
You
a
set
of
site
collections,
it's
it
is
point
e
fault
and
provisioning,
a
Hopf
site
which
is
a
communication
site,
and
then
it
associate
stood
ifferent
and
other
site
collections,
that's
hub
site
and
and
then
it
applies
a
custom
branding
for
the
hub
side.
It
actually
adds,
let's
say
five
to
six
custom
webparts
on
the
front
page
of
the
front
four
of
the
of
the
portal
it
has
more
than
15
webparts
inside
of
it.
It
has
more
than
seven
extensions
inside
of
it
or
them,
as
demonstrated
there
as
well
source
code.
A
Everything
is
available
for
you
to
reuse.
It
uses
a
custom
theme,
so
it
is
using
an
orange
as
the
theme
and
somebody
everybody
is
always
asking
why
orange
well
orange
is
my
favorite
color.
So
we
chose
an
orange
as
that's
the
core,
but
it's
there
mainly
to
demonstrate
the
fact
that
you
can
actually
have
a
custom
trending
in
the
in
the
world.
Well,
it
demonstrate
the
level
of
a
custom
branding
what
you
can
actually
do
within
the
modern
experiences.
This
is
an
open-source
community
treatment
and
development
model.
A
It
is
an
MIT
license,
so
you're
able
to
pull
the
source
code
and
everything
down
you're
able
to
reuse
whatever
you
want
in
any
way
you
want.
So
there's
no,
let's
say
restrictions
for
you
to
reuse
these
in
any
way
within
your
own
deployments
or
in
your
customer
in
cases
which
is
one
of
the
really
intentions
of
this
one
as
well.
A
But
it
actually
shows
how
to
make
all
of
this
happen
automatically
everything
is
in
a
key
table.
You
can
reuse
this
anywhere,
you
want,
you
can
access
the
serf
code
and
anything
as
really
really
easily.
So
let
me
actually
just
in
case
or
really
I'm.
Gonna
actually
add
the
actual
URL
and
thank
you
Dirk
for
actually
adding
the
URL
into
our
window,
just
making
sure
that
that's
covered
there
and
everything
is
available
already
we're
looking
into
improving
the
documentation.
A
It
is
already
in
a
decent
level,
because
the
automation
script
is
quite
automatic
and
I'm
gonna
talk
about
that
one
after
Patrick's
demo
in
practice
and
some
next
steps
for
the
starter
kit.
We
improving
the
documentation
and
guidance
right
now.
We
are
still
lacking
kind
of
intern
solution.
Design
clarification.
Why
did
we
do
this?
What's
there?
What
about
the
webparts?
How
do
they
work
and
all
of
that?
A
Where
do
I
said
ten
on
administrator,
you
can
sign
in
and
you
can
able
to,
let's
say,
modify
the
theme
file,
you're
able
to
modify
the
default
images
and
say
provision
and
within
a
matter
of
five
minutes,
it's
roughly
for
the
six
minutes
slightly
depends
on
a
tenant
speed.
It's
gonna
actually
automatically
get
everything
provision,
so
you
will
have
this
nice
self-service
website
to
provision
this
demo
environment
to
any
tenant
as
easy
as
possible.
A
Now
quick,
a
few
slides
and
I
do
apologize,
there's
quite
a
lot
of
content,
but
but
that's
fine
I
think
this
is
a
super
valuable
content
as
well
so
few
things
on
the
roadmap
calendar
year.
If
we've
released
a
lot
of
substance
during
the
spring,
obviously,
right
now
on
summer
fall
timeframe,
we
want
to
have
a
ga
version
of
the
craft
access
for
SharePoint
framework.
That
is
not
part
of
the
1.5.
A
We
will
have
global
deployment
of
SharePoint
framework
extension
support
as
part
of
1.6
every
release
of
SharePoint
framework
we'll
have
a
dynamic
data
which
is
already
in
preview.
That's
communications
between
the
components
and
then
the
SharePoint
framework
is
order
to
SharePoint
2019,
including
modern
experiences.
So
you
will
have
the
1.4
version
of
SharePoint
framework
support
it
in
the
SharePoint
2019
in
SharePoint.
A
1.5
came
out
in
June
5th,
just
making
some
repeats
on
this
one
and
there's
quite
a
lot
of
cool
stuff.
In
here,
I'm
not
going
to
deep
dive
on
all
of
these
things,
but
obviously
it's
good
to
have
1.5
out
we
and
we
know
that
there
are
some
capabilities
which
people
were
hoping
to
be
involved
in
1.5,
which
are
not
there,
but
they're
now
planned
to
be
in
the
1.6
and
1.6
version
of
SharePoint
framework
is
planned
to
be
released
by
end
of
July
2018.
A
So
it
won't
be
too
many
months,
but
it
will
be
like
one
and
a
half
months
from
now
when
this
1.6
version
is
out
and
we
are
planning
to
have
GA
version
of
the
craft
and
third
party
API
calls
in
there
gyah
version
of
dialog
framework
support
for
react,
16
and
a
few
other
things
in
this
release
as
well.
By
ignite
on
ignite.
We
should
have
1.7
version
of
SharePoint
framework
out
and
what
will
be
there?
I
cannot
disclose
yet
that
so,
let's
concentrate
on
1.6
for
now
good
a
lot
of
talking.
A
Let's
actually
move
into
the
demo,
and,
let's
flip
for
me
to
Patrick
and
Pat,
is
going
to
do
a
live
demo
on
the
PMP
chase
and
the
new
flow
and
taxonomy
API,
which
is
absolutely
brilliant
way
of
accessing
the
information
in
the
taxonomy
service.
Patrick
how's,
the
audio,
hey,
your
audio
is
fine
call.
B
A
B
A
Let's
actually
do
it
then,
and
I'm
gonna
share
my
screen
and
cross
my
fingers
that
this
didn't
works.
But
let's
see
I've
been
having
a
pretty
good
luck
on
this
one.
During
today,
hey
it
seems
to
be
working,
and
somebody
here
to
confirm
I
got
Ramon
excellent.
If
you
got
it,
it
went
across
the
pond,
which
means
that
a
lot
of
other
people
cut
it
as
well.
So
we
wanted
to
have
a
talk
about
the
SharePoint
starter
kit,
and
this
is
like
nation.
A
This
is
really
meant
to
show
you
what
you
can
do
with
the
communication
sites
and
and
there's
its
mixture
of
harder
to
box
with
parts
and
a
custom
web
parts
as
well.
Now
the
location
for
getting
access
on
shipments
target
is
github.com.
Sharepoint,
starter
kit
up.
There
comes
a
SharePoint
/sb,
a
starter
kit,
and
this
really
the
location
where
you
can
then
load
this
now
you
can
clone
the
package
or
you
can
click
the
green
one
and
then
click
download
the
zip
to
be
fair,
and
we
do
recommend
on
learning
how
to
use
github.
A
So
it
would
be
worthwhile
to
to
actually
not
download
the
zip
file,
but
you
can
absolutely
do
that
as
well.
Now,
in
my
case,
I
have
this
up
and
running
in
my
machine
and
I:
do
apologize,
I
didn't
quite
have
a
time
to
now
practice.
I
was
hoping
that
Patrick
I
would
do
go
first,
but
if
that's
fine,
let's
actually
do
this
from
here.
So
in
my
case,
let
me
show
you
what
we
actually
get
when
you
install
that
in
your
machine
or
get
it
in
your
machine.
A
So
in
my
case
we
have
the
individual,
folders
or
I've
cloned
the
repo
and
in
my
case
destined
and
the
folders
are
indie.
Kids
folder
again
depends
on
on
your
local
setup,
but
the
main
document
documentation
folder,
is
relatively
empty.
Still.
It
actually
contains
guidance
on
how
to
set
up
the
tenant
and
level
information.
So
if
I
go
to
the
documentation
now,
if
we
go
to
the
documentation
folder,
we
can
actually
in
the
tenant
settings
we
can
actually
see
what's
available
and
what
has
to
be
configured
in
the
tenant
level.
A
What
you
need
to
do
there's
no
way
for
automating
this
in
a
tenant
level,
because
there's
no
API
is
to
make
this
happen,
we're
potentially
looking
into
alternative
ways
of
doing
personalization
for
this
capability
in
the
future,
but
for
now
that's
needed
and
then,
if
you're
looking
into
exposing
also
stock
information,
you
would
have
to
use
the
offer
bandits
and
claim
your
API
key
to
do
that,
because
we
are
using
that
alpha.
Bandage
API
is
for
showing
stock
information.
A
Now
some
people
are
still
saying
no
sound,
but
there
is
a
sound.
There
is
a
sound.
Please
tell
somebody
tell
me
that
there's
sound
good,
that
audio
means
that
okay,
cool,
excellent.
Now.
Okay,
let
me,
then,
quickly
get
him
back
in
the
in
the
line
on
what
we
actually
have
here.
So
let
me
go
to
my
folder.
So
here's
my
share
pants
target
cloned
my
local
machine
in
here.
A
If
I
go
see
the
provision
provisioning,
we
actually
can
find
a
deploy,
powershell
script
and
deploy
powershell
script
is
the
only
thing
what
you
actually
need
to
do
here.
So
if
you
have
a
completely
clean
tenant,
you
can
easily
follow
up
on
the
guidance
in
the
front
page,
which
is
saying,
prepare
your
tenant
upload
and
deployed
SP
pkt
file
from
packets
folder
to
your
app
catalog.
This
is
only
to
avoid
and
reduce
the
time
of
the
report
for
the
set
up.
A
Technically,
our
script
is
actually
not
getting
us
Biblica
t
file
for
you
as
well,
but
if
you
want
to
reduce
the
time
being
spent
on
the
set
up,
you
can
actually
upload
that
from
the
package
file
and
then
you
run
a
comma
connect,
the
NP
online
to
your
tenant,
and
then
you
run,
deploy
and
with
standard
URL.
It
doesn't
have
to
be
the
admin
URL
and
then
you
do
a
site
prefix
and
that's
gonna
then
set
up
and
the
whole
setup
for
your
tinner.
So
in
my
case
I
executed
this
earlier
today.
A
A
A
So
in
here
order
to
box
back
board
out
of
a
box
back
port.
That's
a
custom
web
part
with
the
report.
There
is
actually
out
of
the
box
with
the
web
part
coming
pretty
soon
as
well.
So
not
sure
if
this
is
going
to
remain
in
the
packaged.
Our
stock
is
going
to
looking
good.
It's
going
up,
that's
always
a
good
sign,
and
then
this
is
a
banner
web
part
which
is
a
custom
web
part
and
then
we're
word
will
time
web
part.
This
also
demonstrates
the
the
extension
which
is
in
here.
A
Some
people
might
not
like
it,
but
this
one
also
has
a
set
of
company
links,
and
then
you
can
always
do
the
edit
and
add
here
a
own
SBP
and
be
the
most
important
sharepoint
and
deaf
community
EMP,
and
the
URL
to
remember
is
what
a
kms
is
pp
and
be
right
and
clicking
add
and
that's
going
to
actually
save
that
URL
to
the
user
profile,
and
that
was
to
use
a
profile
property
which
is
getting
used
in
here.
In
this
particular
setup,
hello
I
didn't
actually
test
it.
A
A
So
let
me
do
a
controller
portal
jumping
to
the
contoso
portal
and
jumping
to
the
example
craft,
which
is
the
personal
here.
This
link
is
added
automatically
in
the
in
the
hop
navigation.
It
actually
shows
then
how
to
get
access
on
the
graph
and
data
behind
of
the
graph
API.
So,
for
example,
in
my
case,
my
tasks
and
my
personal
email
in
this
particular
tenant
and
then
contacts
or
upcoming
meetings,
pretty
cool
stuff.
It
also
actually
has
a
few
extensions
like
mentioned.
A
So
if
I
go
to
the
site
contents,
in
this
case,
we
can
actually
see
that
we
in
the
site
contents
list.
We
have
a
large
list
and
in
this
alert
list
we
have
created
a
alert
which
is
called
company
summer
event
next
week.
Please
remember
the
register
company
event
and
there's
a
start
date
and
an
end
date
how
it's
being
visible
now
an
alert
type.
A
This
here
is
basically
controlling
what
kind
of
information
is
getting
shown
in
the
extension,
so
header
extension
getting
shown
these
alerts
for
the
end
users,
which
is
pretty
cool
way
of
extending
and
the
UI
as
well.
Now
the
code
itself
not
going
to
deep
dive
in
here,
because
hopefully,
Patrick's
demo
is
still
available,
but
if
I
go
in
here
and
then
I
went
to
a
completely
wrong
location.
Let
me
actually
close
that.
Let
me
go
in
here
and
let's
go
solution,
and
here
we
go
now.
If
I
can
open
up
this
host
area
code.
A
A
This
one
has
one
two,
three,
four:
five:
six:
seven,
eight
nine
10
11
12
13,
14,
15,
16
17
with
pods,
for
example,
the
personal
calendar,
personal
emails,
other
care
access
on
that
you're
able
to
have
a
look
on
the
implementation
of
that
functionality.
All
of
these
are
being
built
using
react
because
they're
using
office,
UI
fabric
or
they're,
using
the
SharePoint
framework,
reusable
controls
from
BMP
and
and
the
office
you
I
have
react.
Office,
uff,
recreate
controls.
Just
to
give
you
the
consistent
look
and
feel
so.
A
But
it's
actually
there's
a
lot
of
a
lot
of
insights
on
this
implementation.
We
saw
how
to
use
the
craft
client
how
to
get
the
information,
how
to
render
the
information
in
the
different
scenarios.
All
of
the
extensions
are
here
as
well
one
two,
three
four
five,
six,
seven
extensions
which
are
available
for
take
advantage.
For
example,
the
the
portal
folder,
which
is
the
extending
footer
or.
B
A
A
So
if
I
create
a
new
team
site
or
communication
site
or
team
site
collaboration
folder,
why,
after
running
the
setup,
you
will
see
a
countenance
a
team
site
site
design
which
is
demonstrated
in
the
setup
as
well,
and
we
are
able
to
then
create
a
new
site
based
on
this
site,
design
and
site
script
behind
off
the
site
designs.
Now,
let's
do
that.
A
One
two
three
four
five
right
about
now
finish
button
is
active
clicking
that
one
Pam
param
param
and
we
will
actually
have
a
modern
team
site
where
we
then
run
a
site
design
where
we
actually
associate
this
newly
created
site
to
a
hub
site,
and
then
we
associate
in
SharePoint
framework
extension
folder
to
the
site.
So
let's
have
a
look
on
the
updated
site.
A
We
can
actually
see
that
the
the
site
has
been
associated
to
hop
because
we
have
the
hub
navigation
available
automatically
in
here,
and
we
also
actually
have
this
pretty
cool
folder,
which
actually
supports
adding
the
custom
links
to
yourself
as
well.
So
there's
a
a
slightly
different,
looking
footer,
which
is
working
quite
nicely.
There's
a
company
company
links
here,
visible
in
here
as
well,
so
quite
nice
setup
and
all
of
the
source
code.
Everything
is
ready
for
you
to
take
advantage
now.
I
do
apologize
on
the
technical
issue.
Patrick
are
you
there?
B
All
right
before
it
crashes,
so
this
is
the
same
demo.
I
talked
through
at
the
European
collaboration
summit,
which
may
be
the
technical
difficulties
are
just
this
demo
causes
them
somehow,
but
so
what
you're
looking
at
here
is.
This
is
the
this
is
the
project.
This
is
the
PJs
full
libraries
and
what
I'm
using
is
the
f5
debugging
capabilities
to
just
run
these
demo
files
and
wanted
to
show
this
off.
B
The
goal
of
this
library
was
to
really
give
folks
a
fluent
easy
way
to
access
manage
metadata
in
SharePoint,
an
understanding
that
the
REST
API
there's
still
no
REST
API
backing
this,
but
we
wanted
to
present
an
API
surface
for
folks
to
use
that
would
be
very
similar
and
familiar
with
what
we've
done
with,
for
example,
the
at
P
and
PSP
library,
for
example,
or
any
of
the
others
in
this
p.m.
PJs
family
of
libraries.
B
So
the
first
thing
you'll
note
at
the
top
we're
importing
an
object
called
taxonomy
from
P
and
P
slash,
SP
taxonomy.
This
matches
exactly
what
you
do
with
the
SharePoint
library
importing
that
SP
object,
but
here
are
importing
taxonomy
you
do
need
so,
for
example,
this
is
going
to
be
running
in
node.js,
so
you
would
still
need
to
call
the
setup
method
here.
You
would
still
need
to
call
if
you
were
in
SharePoint
framework.
B
You
would
call
the
setup
method
and
supply
the
SharePoint
framework
context
in
exactly
the
same
way
you
do
for
SharePoint
and
in
fact,
just
to
sort
of
give
you
some
insight
into
this.
We're
actually
inside
the
taxonomy
library
we're
just
a
liasing,
the
SP
setup
methods,
so
there's
no
extra
magic
going
on
with
taxonomy,
but
the
reason
for
doing
that
is
I
think
it
makes
it
a
lot
easier
for
folks.
B
If
you
just
are
working
with
taxonomy,
you
don't
have
to
import
the
SP
library,
call
it
setup
method
and
call
you
know,
then
taxonomy
methods
it
might
not
make.
It
might
be
a
little
unclear
exactly
how
that
would
flow.
So
you
can
call
it
taxonomy
not
set
up
here
we're
just
creating
our
node
fetch
client.
So
this
is
using
a
a
CS
registered
client,
ID
and
secret
I'm
getting
those
out
of
a
settings
file
so
that
those
are
hidden
away.
B
B
Is
your
your
sort
of
root,
object
or
starting
point
for
your
fluent
queries,
and
so
what
we're
doing
is
we're
calling
the
method
forget
the
fault,
site,
collection,
term
store
and
then
you've
seen
in
the
past,
you've
seen
us
use
this
get
a
call
with
the
SP
libraries.
It's
the
same
idea
here
and
what
we're
doing
under
the
hood
is
we're
actually
building,
and
you
can
see
the
results
come
down.
We'll
talk
about
that
in
a
second.
What
we're
actually
doing
is
under
the
hood
building.
B
Our
XML
requests
to
the
client
SVC
endpoint,
and
this
get
is
actually
invoking
that
so
we've
kept
the
same,
we'll
call
it
sort
of
same
language
or
same
semantics
as
we
did
in
the
SP
library
talking
to
rest.
So
this
appears
very
rest
like,
but
under
the
hood
is
being
converted
to
a
client,
SVC
query
and
then
we're
just
logging.
Our
JSON
return
object
which
what
we've
got
down
here,
as
you
can
see,
we've
gotten
we've
called
the
process,
query
endpoint
and
then
we've
gotten
back.
Where
is
it
starts?
Where
does
it
start?
So?
B
Here's
our
office,
so
here's
our
properties
is
online.
We've
got
our
languages,
our
name
and
we're
getting
these
things
back,
so
it
works
very
familiar
with
what
you're
used
to
with
the
ESPE
stuff.
So
I'm
going
to
comment
that
out
and
I
want
to
show
a
couple
other
examples
here
of
just
how
we've
sort
of
stuck
with
that
fluent
idea.
So
tox
on
amis
have
term
stores
term
stores.
You
want
to
get
that
by
ID,
and
then
we
want
to
select
from
that
term
store
the
name.
B
This
can
run
but
present
this
fluid
API
and
allow
you
to
work
very
easily
and
in
a
manner
you're
familiar
with
if
you've
used
the
PM
pjs
libraries
in
the
past.
So
we're
hoping
to
make
adoption
of
this
very
simple
but
still
very
powerful
and
allow
you
to
get
this
managed
metadata
out
of
SharePoint,
which
has
been
obviously
it's
been.
B
Dependencies
from
your
project,
so
you
can
see
here,
got
our
names
back,
so
that's
the
term
store
name
and
then
this
is
the
term
set
name
which
is
just
you
know,
kind
of
junk,
because
this
is
all
just
my
testing
tenant,
but
you
can
see,
we've
been
able
to
fluently,
get
that
stuff
back
and
you'll
see
many
of
the
other
methods
follow
that
kind
of
stuff,
and
the
last
I
want
to
show
you
two
more
things
as
we
go
in
here.
We
of
course
wanted
to
support
batching
in
a
similar
way.
B
One
of
the
complexities
here
is:
we
can't
share
batches
right.
You
can't
share
a
batch
from
between
the
rest
and
the
client
SVC.
So
what
we've
done
is
you
create
the
batch
instead
of
off
of
your
SP
object
or
your
SP
web
object?
You
create
it
right
off
the
taxonomy
and
that's
gonna
create
a
different
batch
object
because
it's
working
with
the
client
as
to
be
seen
it
works
in
a
different
way,
but
that
complexity
is
then
again
hidden
away
and
we're
able
to
make
our
calls
I'm
gonna
hit
f5.
B
So
this
can
run
as
I'm
talking
we're
able
to
make
our
calls
in
exactly
the
same
way,
so
we're
getting
the
the
site,
collection
default
term
store,
selecting
its
name
and
in
the
same
syntax
that
we've
set
up
with
the
SP
stuff
I'm
saying
in
batch
and
I'm
passing
that
batch
object
in
and
I'm
calling
get
I'm
doing.
The
same
thing
here
get
my
ID
and
then
I'm
executing
that
batch
and
one
of
the
things
you'll
note
here
is
I'm
just
doing
get
requests,
but
this
also
works
with
updates
or
creates
with
the
post
requests.
B
This
exact
same
pattern
will
work.
You
just
pass
it
into
the
batch
and
call
the
batch
execution
same
patterns.
We've
set
up
with
the
SharePoint
libraries
again
hoping
to
make
adoption
easier,
and
you
can
see
I've
just
written
out
one
two
three,
so
you
can
see
that
were
actually
as
well
resolving
all
those
promises
in
order
that
you
would
expect.
So
you
might
get
some
data
here.
You
might
get
some
data
here
and
then,
once
the
entire
batch
has
completed,
you
might
update
your
UI.
A
A
So
PMPA
/phas
is
the
new
version
of
the
PMPA
s
core.
So
this
is
a
replacement
of
the
classic
vm
PHAs
core
and
which
is
more
modern
and
it
has
the
taxonomy
things
and
all
of
that's
available.
So
that's,
that's
all
kid
and
and
Patrick's
is
still
ongoing.
I'm
showing
us
this.
He
apparently
hasn't
noticed
that
we
lost
audio,
which
is
actually
is
a
pity.
A
But
basically
the
whole
point
of
this
one.
What
you're
seeing
here
is
that
you
have
a
fluent
API
and
what
we're
intended
to
do
with
this
one
right
now
this
is,
there
is
no
such
thing
and,
as
a
rest,
api
is
for
taxonomy.
This
is
using
classic
client,
SBC's
and
sing
captivating
those
calls
behind
the
scenes
which
is
supported,
because
that
is
actually
a
a
client
site
that
is
documented
in
the
protocol
Docs.
Now
it's
not
the
preferred
way,
and
sooner
or
later
there
will
be
a
native
REST
API
available
as
well.
A
Now
what
that
one
means
that
whenever
the
Native
rest
day
I
arrest,
API
is
available.
I'm
gonna,
move
back
on
the
slide
and
whenever
the
native
REST
API
is
available,
will
flip
the
implementation
of
the
p.m.
PHAs
to
use
the
native
REST
API.
So,
if
you're
using
this
implementation
right
now
it
will,
it
should
be
relatively
or
completely
hopeful
assume
less
seamless
for
you
that
in
the
transition
to
the
new
model-
and
that
is
available
now
we're
heating
the
hour
as
well,
we
just
can't
get
the
straight
in
every
single
call.
A
We
have
some
issues,
but
that
is
indeed
the
new
ripple.
Github.Com
/p
n
/b
MJ
s,
so
that
should
be
fine.
Now
not
zoom,
less
a
seamless,
oman,
fair
point:
zoom
less
is
Finglas,
but
it
means
a
seamless
in
english,
so
there's
a
big
transition
over
there
now
the
rest
api
of
a
taxonomy
is
not
in
shape
on
2019,
it's
always
cloud
first,
so
you
will
not
see
anything
client-side
development
style
first
in
SharePoint
2019,
because
SharePoint
2019
is
based
on
SharePoint
Online,
but
it
was
forked
a
few
months
ago.
A
So
SharePoint
in
2019
is
an
older
version
of
SharePoint
than
SharePoint
Online
with
the
Souper,
which
is
important
to
also
understand
so
now
as
part
of
the
SharePoint
Online.
We
are
currently
looking
into
investing
more
on
the
enterprise
content
management
story.
There
is
work
being
done.
I
cannot
explain
even
the
the
estimate
right
now
for
the
potential
taxonomy
api,
because
we
don't
want
to
promise
anything.
Will
it
be
at
some
point
in
SharePoint
Online?
Absolutely
that
is
the
intention.
A
Yes,
okay,
now
Patrick
realized
that
he
lost
earlier
cool
and
we
do
apologize
on
the
technical
issues.
I
think
we
were
able
to
capture
and
all
of
the
live
demos,
so
everything
is
recorded,
we'll
get
the
video
out
in
24
hours
and
the
video
will
be
available
in
the
YouTube
channel
at
a
kms
spdf
videos
in
24
hours.
Typically,
it
will
be
20
hours
from
now
or
something
like
that.
So
after
noon
on
my
time
zone
when
I'm
sitting
in
Finland
but
Thank
You
Patrick,
thank
you
everybody
for
joining.
A
We
do
apologize,
we're
trying
to
figure
out
if
we
potentially
need
to
flip
the
technology
for
these
conference
calls
because
we're
heating
already
more
than
200
to
ten
days
on
this
course.
But
thank
you
everybody
for
joining.
Thank
you
for
your
patience.
We
will
try
to
figure
out.
How
can
we
guarantee
more
reliable
platform
in
the
future?
Please
keep
on
giving
us
the
feedback
in
the
in
the
issue
list
and
using
the
other
social
media
channels.
Thank
you,
everybody
and
we'll
be
absolutely
in
touch
bye-bye.