►
From YouTube: PnP Monthly Community Call - January 2018
Description
SharePoint PnP Community call recording from 9th of January 2018. Summary of the activities happened in the past month around SharePoint development guidance and 3 specific demos around SharePoint development topics.
A
B
Welcome
everybody:
this
is
the
SharePoint
patterns
and
practices
or
shape
on
deaf
ecosystem
system.
The
monthly
community
call-
and
this
is
the
January
2018
zation
so
nowadays,
and
the
SharePoint
BMP
equals
the
share
points
and
if
ecosystem,
essentially
everything
in
the
ship
on
development,
guidance
and
samples
and
everything
else,
goes
through
our
initiative
and
we're
being
coordinated
by
the
SharePoint
engineering
and,
that's
being
obviously
me
and
my
managers
and
my
team
members
who
own
the
SharePoint
framework
and
all
of
the
SharePoint
API
as
well.
B
My
name
is
Ivan
and
I'm
gonna
be
the
host
today
again
so
I'm
gonna
start
within
15
minutes
intro
and
then
we're
gonna
have
three
different
demos
slightly
later
today.
But
let's
quickly
have
a
look
on
the
agenda,
so
I'm
gonna
have
a
quick
look
on
the
on
the
shape
on
development
kind
of
a
latest
news.
We're
gonna
have
a
quick
look
on
the
roadmap.
Quick,
look
on
the
new
thing
on
the
on
our
user
voice
status
and
few
other
details.
We
will
not
have
as
expected
the
same
structure
as
previously
in
this
monthly
call.
B
Anyway,
we
have
three
different
demos:
Paolo
is
gonna,
demonstrate
or
show
in
practice,
and
the
preview
of
the
upcoming
third
party
API
sand
craft
improvements
with
SharePoint
framework,
and
this
is
something
which
isn't
quite
necessarily
working
properly,
but
we
kind
of
walk
through
the
process
and
let's
see
how
how
it's
actually
working
today
and
that's
one
of
the
reasons
why
it
has
not
yet
been
shipped
for
preview.
We
are
still
working
on
on
making
the
whole
functionality
stable
enough.
So
we
can
start
to
preview
and
get
the
comments
and
feedback
from
the
community
sign.
B
Then,
after
Paolo
we
have
Alex
gonna,
do
a
nice
demo,
a
nice
demo
around
the
low
kite
and
common
set
customizer
relatively
simple
customizer,
but
it
actually
is
showing
in
quite
nice
business
case
and
completely
valid
business
case.
So
we're
able
to
lock
items
from
a
list
boil
for
yourself
using
this
one
framework,
extension
and
then,
as
a
last
but
not
least,
Chris
Kent,
sharing
the
column,
formatting
client-side
web
part
super
cool
stuff
on
on
how
to
create
column,
formatting
definitions
for
list
columns.
B
So
that's
all
good,
so,
let's
actually
get
on
going
on
the
new
structure
on
the
presentation
and
a
few
news
before
we
go
to
the
demos
section
just
quickly
to
introduction
or
explain,
because
there's
always
a
new
people
in
this
call
and
on
the
SharePoint
community
and
SharePoint
develop
an
ecosystem
side
on
SharePoint
PNP
sign.
You
have
multiple
choices:
to
align
your
participation
based
on
your
availability.
B
So
if
you
have
questions,
you
want
to
have
a
random
follow
up
on
random
things
what's
happening,
you
can
always
use
our
community
SharePoint
developer
group
in
the
AKM
SSB
PNP
community
URL,
that's
gonna,
be
in
the
tech
community
or
Microsoft
tech
community
and
there's
a
crude
thereof
called
share
pond
developer,
where
you
can
ask
questions
and
people
are
helping
on
those
questions.
We
do
have
my
weekly
issue
up
on
frameworks.
B
Special
interest
group
call
where
we
go
through
the
latest
on
the
SharePoint
framework
latest
on
VM
PHAs
core
and,
for
example,
CLI
office,
365,
CLI
and
reusable
controls
and
all
of
the
client-side
development
topics
on
a
SharePoint,
and
that
that
special
interest
group
is
meeting
on
bi-weekly
basis.
We
also
have
a
biweekly
kind
of
a
general
SharePoint
Development
special
interest
group
call
where
we
concentrate
more
on
how
would
I
put
it
not
a
classic
but
more
managed
code,
ways
of
customizing,
SharePoint,
so
essentially
stuff
which
is
running
in
a
short
time.
B
At
your
base,
trim,
old-timer
jobs,
BMP
see
some
BMP
powershell
and
all
of
those
scenarios,
so
not
necessarily
client-side
development,
but
rather
overall
thinking
on
the
SharePoint
customizations
and
then
we
have
this
monthly
community
calls,
and
this
is
essentially
a
summary
on
what
has
happened
within
the
previous
month,
just
covering
the
latest
news
and
latest
announcements,
and
we
all
in
all
of
these
course.
We
also
have
always
live
demos,
so
you
can
actually
see
something
cool.
B
Typically,
what
all
of
them
are
super
cool
and
then
there's
hopefully
always
time
for
Q&A
in
the
end
as
well.
The
monthly
community
calls
are
typically
quite
crowded
or
dead,
sorry
they're
quite
busy.
So
there's
not
that
much
time
in
the
end
for
Q&A,
but
during
the
call
you
can
absolutely
use
the
ion
window.
If
you
have
any
specific
questions
on
the
topics
which
we
go
through,
we
have
been
recording
members,
internal
and
external,
helping
other
questions
as
well.
B
Good,
let's
get
on
going
on
things,
so
the
only
metrics
on
only
number
slide,
which
I
wanted
to
quickly
show
just
two.
We
have
so
we've
been
showing
distance
from
the
dawn
of
our
monthly
community
calls
from
2014.
So
we
had
quite
a
lot
of
people
watching
our
YouTube
videos.
We
went
slightly
down
from
December
sorry
from
November
in
during
December,
but
that's
completely
understandable.
December
is
a
holiday
season.
We
had
anyway
118
thousand
watch
time
minutes
in
the
YouTube
channel
in
the
official
SharePoint
dev
YouTube
channel.
B
This
is
triple
the
amount
of
visitors
in
a
key
table,
so
clearly
people
are
learning
more
and
more
how
to
use
kids
up
and
how
to
use
open
source
initiatives
for
their
business
benefit
and
in
the
doctor,
Mac
stuff
that
come
underneath
the
ship
on
debt
and
if
we
had
four
five
hundred
and
eighty
two
thousand
views,
which
is
a
relatively
good
number,
it
meant
also
slightly
down
from
November
but
to
the
holiday
season.
That
is
absolutely
understandable.
B
On
the
pnp
reusable
component
side,
we
had
more
eight
thousand
tenants
roughly
using
our
reducing
the
PMPA,
reusable
components.
These
are
BMP
season
component
BMP,
PowerShell
and
PM
PHAs,
core
data,
TB
requests
somehow
magically
went
up
20%
during
December.
We
do
not
know
why,
because
we
haven't,
we
don't
have
the
data
to
understand
done,
but
it
seems
to
be
that
on
during
December
there
was
well
potentially
there
was
quite
a
lot
of
customers
doing
my
creations
and
these
tools
to
help
on
the
micro
sigh
so
during
holiday
season.
B
Quite
often,
people
are
migrating
to
a
new
platform,
and
that
would
explain
the
20%
increase
on
the
traffic
and
the
most-used
capability
again
was
the
provisioning
engine,
but
which
was
used
almost
in
2000
tenants
within
the
last
month
on
the
topics
and
general
news.
I
will
keep
this
one
in
our
documentation
or
in
our
presentations
in
the
future
as
well.
So
a
kms
s/pdif
docks
our
official
location
for
all
of
the
ship
and
development
documentation.
B
So
this
includes
adding
model
SharePoint
framework,
future
on-premises
a
story
and
everything
MSDN
is
gradually
going
to
be
locked
down
or
archived,
and
all
of
our
active
and
new
documentation
will
be
in
docks
of
microsoft.com
sign.
What's
good
about
this,
one
is
that
you
are
able
to
contribute
if
money
back,
you
can
contribute
by
letting
us
know
that,
there's
a
block
on
the
documentation
or
you
can
even
contribute
by
submitting
a
pull
request
towards
this
material.
Everything
is
in
the
key
table
under
the
SharePoint
organization.
B
You
know
the
other
thing
which
we
wanted
to
kind
of
a
help,
people
to
help
them
or
we
want
to
improve
the
support
story
around
the
SharePoint
dev
questions.
In
the
past,
if
you
haven't
had
a
premier
support
and
you've
been
conducting,
for
example,
the
Microsoft
support
and
saying
well
I
have
this
development
topic
and
something
that
seems
to
not
work.
It
has
been
really
difficult
for
you
to
get
any
assistance
and
necessarily
true
the
classic
support
or
getting
connected
on
the
engineering.
B
Now
we
want
to
change
this
in
the
future,
because
we
want
to
help
people
to
be
resolve
these
issues
and
we
want
to
have
a
channel
where
you
can
potentially
report
us
any
critical
issues
what
you
might
run
into,
so
we
will
actually
know
about
them.
So
using
the
SPF
Docs
repository
initial,
is
there
a
kms
address
the
sake
MSS
bit
of
issues?
B
You
are
able
to
report
issues
towards
to
SharePoint
engineering
and
we
are
triaging
these
twice
a
week
and
we
also
track
them
in
our
internal
resource
to
the
online
task
lists
and
towards
the
engineer
and
that's
going
to
help
us
to
know.
If
there's
any
critical
issues,
there's
any
any
issues,
also
from
a
documentation
side.
We
are
tracking
them
using
in
here.
So
we
know
actually
that
something
is
wrong
and
we
can
easily
fix
that.
If
it's
a
small
thing,
we
can
fix
that
extremely
fast,
especially
if
it's
a
documentation
issue.
B
If
it's
a
service
level
issued
and
we'll
see
how
fast
we
can
actually
resolve
that.
But
please
please,
please
let
us
know
if
something
is
wrong.
You
don't
like
something.
You
have
a
question
and
you
have
feedback.
Please
use
this,
and
this
is
a
great
channel
to
get
conducted
directly,
which
you
happen
to
engineering
and
it's
super
useful
for
everybody
in
the
SharePoint
development.
Now,
on
other
topics,
kind
of
a
news
I
wanted
to
quickly
do
a
road
map
before
we
go
into
the
what
has
happened
within
the
december
and
on
the
road
map
slide.
B
This
is
something
what
we've
been
showing
on
the
special
interest
group
course.
Quite
often,
we
have
shipped
quite
a
lot
of
stuff
since
the
mid-september-
and
this
is
the
time
just
before
ignite,
because
week
before
ignite,
we
actually
enabled
SharePoint
framework
in
on-premises
or
within
shape
on
2016
future
back
to
the
latest
thing
which
went
live
available.
Is
the
site
designs
with
an
extensibility
point?
So
this
was
something
which
we
were
planning
to
go
live
with
by
end
of
last
year.
B
We
did,
however,
had
some
complications
on
getting
that
functionality
available
and
it
gradually
went
enabled
in
the
first
release
tenants
during
the
last
week
or
end
of
last
week
by
well.
It
is
early
this
week
so
already
today,
100%
of
the
first
release
tenants
has
now
decide
to
sign
since
side
scripts
extensibility
the
story
enabled
so
we're
able
to
actually
create
those
slightest
signs
and
side
scripts.
We
will
release
a
webcast
on
that
topic.
Also,
next
Monday
we
will
demonstrate
how
these
things
can
be
actually
done
in
practice.
B
There
is
a
great
documentation
available
on
that
one
already
coming
soon
more
microsoft
crash
support
for
SharePoint
framework
and
which
will
allow
you
to
have
any
scopes
in
the
Microsoft
graph,
which
is
pretty
cool
as
long
as
the
tenant
administrator
approves.
This
goes
what
your
application
is
want
to
do,
so
we
give
full
access
and
full
flexibility
for
tenant
administrators
to
control.
What
are
the
permissions
and
Microsoft
graph
towards
the
Microsoft
graph
or
against
any
as
your
Active
Directory
application
in
the
tenor.
So
that
means
that
you
can
secure.
B
B
There's
always
some
complications,
because
it's
coming
into
preview,
it's
not
coming
to
production,
lab
and
we're
trying
to
figure
out
and
fix
those
and
get
the
stuff
available
for
you
to
give
us
more
feedback,
then
the
hub
site
and
hub
API,
so
coming
quite
soon
as
well
and
croak
with
IAB,
is
on
plan
to
go
live
during
this
quarter.
There
might
be
some
delays
on
these,
so
please
do
not,
let's
say,
commit
your
business
or
your.
B
Let's
say
money
investments
based
on
this
promise,
because
these
dates
might
change
absolutely
the
things
which
I
wanted
to
quickly
walk
through
and
clearly
I'm,
not
going
to
hit
the
fifteen
minutes
at
this
time
either,
but
good
to
know
so
quickly
to
mention
few
things
around
the
user
voice.
So
we
do
track
to
use
the
voice
entries
we've
been.
Maybe
in
the
past
you
haven't
seen
that
much
activity
that
much
activity
on
the
on
the
use
of
our
site.
B
We
aren't
tracking
this
in,
in
relatively
reason,
not
recently
quite
often,
and
we
are
aware
of
the
numbers-
let's
put
it
this
way,
so
I
wanted
to
quickly
walk
through
what
are
we
doing
and
planning
to
do
with
this
and
no
promises
on
the
timelines?
But
let
me
explain
quickly
where
we
are
because
I
think
that's
slightly
will
be
beneficial
for
you
as
well,
so
the
taxonomy
rest
and
taxonomy
changes
are
in
our
roadmap
later
this
year.
B
Now
this
calendar
year
was
looking
into
having
more
investments
on
the
ECM
side
on
the
document,
management
and
all
of
this
side,
and
these
are
potential
things
which
might
be
actually
getting
prioritized
over
there.
Obviously,
having
the
taxonomy
REST
API
item,
having
more
than
almost
1,000
volts,
will
definitely
increase
the
priority
of
that
particular
item.
So
absolutely
we're
looking
into
doing
that.
B
Both
of
these
are
currently
under
discussion
in
our
SharePoint
framework
team
or
within
our
team.
It's
a
host
responsible
of
SharePoint
framework,
obviously
having
more
votes,
will
help
us
to
prioritize
these
things,
but
we
absolutely
acknowledge
and
the
request
and
most
likely
these
things
will
be
enabling
sooner
or
later,
support
for
dotnet
core
with
season,
and
this
is
slightly
more
problematic
than
it
might
think
might
be.
Sounding
do
our
build
process!
I'm
not
gonna,
go
into
technical
details,
we
understand
ask,
and
it
has
already
324
votes,
so
it's
getting
more
visibility
also
internally.
B
It
is
not,
however,
just
a
simple
thing
to
make.
This
happen
and
within
our
monthly
release
cycle,
so
we're
looking
into
that
one
no
promises
when
and
that
might
be
coming
available
other
than
that
there's
some
season
requests
and
REST
API
requests.
The
number
nine
is
kind
of
an
interesting
the
REST
API
citizens
it
we
are
now
looking
into
solving.
B
Hopefully-
and
we
will
get
proper
rest
API
documentation
around
that
time
frame.
Good
small
update
on
the
on
the
things
I'm
not
going
to
go
do
details
detailed
on
the
every
single
one
of
them,
but
I'm
just
gonna
ensure
that
everybody
understand
that
we
are
actually
tracking.
These
things
quite
closely
in
the
engineering
side,
which
quickly
January
28
in
summary,
not
going
to
deep
dive
again
on
these
things.
If
you
go
to
death
drafts
that
comes
as
blocks,
you
will
find
at
the
January
2018
update
that
has
massive
amount
of
links,
massive
amount
of
information.
B
What
was
actually
released
during
this
month,
not
going
to
go
through
all
of
these
things,
but
basically
there
was
new
samples
on
SharePoint
framework,
new
guidance,
videos
and
documentation
on
the
SharePoint
framework
sign.
There
was
again
obviously
a
new
version
of
the
BMP
PowerShell
with
the
new
command,
let's
available,
which
will
help
you
to
automate
operations
and
sharepoint
online
or
in
on-premises,
and
a
new
version
of
the
of
the
BMP
say
some
coral
component.
We
also
have
the
site,
design,
preview
and
material
is
now
available
with
the
documentation
side,
and
there
is
an
open
source.
B
Chasin
repository
to
share
side
scripts
with
the
community,
so
you're
able
to
already
go
there
and
have
a
look
on
hey.
Are
there
an
available
sample
side,
scripts
and
you're
able
to
use
them
within
your
tenant
as
a
test
exercise
for
the
side
scripts?
We
also
have
a
my
creation
guidance
for
classic
experiences
to
modern
experiences.
B
You
will
see
more
on
that
one
more
of
that
kind
of
guidance
in
the
future,
so
we'll
leave
it
really
looking
into
helping
you
on
doing
to
my
creation
from
the
modern
X
classic
experiences
and
SharePoint
Online
to
the
modern
experiences
and
SharePoint
Online,
and
that
should
be
pretty
same
with
the
sharepoint
2019.
I
cannot
confirm
yet,
but
the
modern
experiences
will
be
in
2019
but
obvious
way,
and
that
is
absolutely
our
intention
so
into
sharepoint
2019.
B
It
would
have
the
modern
experiences
inside
of
it
office
365,
our
CLI
updates,
which
is
great
capability
as
well,
and
new
column
formatting,
as
samples
are
available.
Good
moving
on
are
things
quite
a
lot
of
new
webcasts.
Obviously,
the
webcasts
are
quite
important
within
our
guidance
they
deep
they
are
interactive.
B
Huge.
Thank
you
for
your
assistance
and
again
I'm,
not
gonna
mention
all
of
you,
but
thank
you.
Thank
you
for
assisting
us
on
this
journey
and
with
your
contributions
in
the
github
or
in
other
community
channels.
Your
contributions
will
help
the
others
to
succeed,
and
this
is
how
things
are
evolving
across
the
whole
IT
community.
So
more
and
more
people
are
using
open
source
in
moment
more
and
more.
We
are
working
together
towards
solving
these
things.
B
Now,
on
the
Microsoft
side,
our
team
is
growing
as
well,
so
multiple
people
are
coming
from
a
different
sections
in
different
organization
from
Microsoft
side,
helping
on
this
journey,
helping
either
by
contributing
in
the
community
sides
in
the
same
way
as
the
external
community,
or
that
it
might
be
part
of
their
job
to
be
part
of
this
community
and
open
source
initiatives.
But
thank
you
for
your
contributions
as
well
now,
on
the
demo
section,
twenty
minutes
not
too
bad.
Actually,
let's
start
with
a
paolo
and
paula
can
actually
start
sharing
because
paolo
you
are.
A
So
yes,
Thank
You
vissa
and
let's
see
how
to
create
a
SharePoint
framework
solutions
which
can
leverage
the
new
capability
in
order
to
consume
on
the
micro
graph,
API
or
any
other
third
party
API
is
using
a
custom
set
of
permission
scopes.
So,
first
of
all,
let's
see
one
demo
in
which
I
simply
consume
the
max
of
graph
to
browse
and
to
search
for
specific
users
with
a
name
or
display
name
or
last
name
matching
a
search
criteria.
A
In
order
to
do
that,
first
of
all,
in
the
packages
solution
JSON
file,
you
will
have
to
specify
the
permission
scopes
that
you
will
need
and,
as
you
can
see
here,
there
is
a
new
configuration
parameter,
called
Web
API
permission
requests,
which
is
an
array
of
permission
requests.
Each
of
them
is
made
of
a
resource
ID
and
of
a
scope.
The
resource
ID
can
be
the
name
of
the
target
API
that
you
want
to
consume
and
for
which
you
want
to
have
a
specific
permission,
scope
or
can
be
the
object
ID
of
that
resource.
A
Bear
in
mind
that
the
object
ID
is
unique
per
tenant.
So
if
you
want
to
create
a
multi-tenant
solution
or
if
you
are
an
ISV
that
want
to
sell
your
solution
to
multiple
customers,
it's
better
to
use
the
name
of
the
API,
the
object
ID
will
be
tied
to
the
specific
tenant
in
which
you
are.
The
same
applies
for
the
scope.
You
can
provide
the
name
of
the
scope
or
you
can
provide
the
global,
unique
identifier
of
the
scope.
A
In
my
opinion,
both
the
name
of
the
app
and
the
name
of
the
scope
are
better
than
the
good,
of
course,
and
here
and
we
are
just
requesting
for
the
permission
to
access
all
of
the
basic
information
of
all
of
the
user
in
our
tenant,
so
user
dot
with
basic
that
all
for
the
Microsoft
graph.
Once
we
have
declare
the
permission
request,
which
can
be
multiple,
we
can
have
multiple
permission.
Scopes
requests
here
in
the
JSON
file.
A
We
need
to
consume
the
target
API
and
to
consume
any
of
the
target
API,
whether
it
is
the
graph
or
any
other
third
party
API.
We
have
two
new
types
available
in
SPF
X.
There
will
be
available
as
soon
as
this
capability
will
be
released.
So
let
me
go
to
the
rear
component.
Under
the
cover
of
my
solution,
and
here
I
have
two
different
options:
the
first
one
uses
the
aad
HTTP
client
type,
which
is
a
new
one
which
will
be
released
in
preview
pretty
soon
and
through
this
type.
A
A
Here,
for
example,
I
want
to
search
for
the
users
so
I'm
using
the
users
endpoint
of
the
graph
v1
and
I'm,
selecting
just
few
properties
of
every
single
users
which
will
match
a
filtering
criteria
based
on
the
given
name
equal
to
a
value
that
I
will
ask
through
the
UI
of
my
web
part
or
the
surname
or
the
display
name.
So
this
is
just
an
open
data
protocol.
Query
filter,
so
I
make
a
get
request
for
this.
Url
and
I
will
get
back
as
usual.
A
I
would
say
whenever
you
consume
an
HTTP
based
API
I
will
get
back
a
JSON
object
which
I
can
parse
and
which
I
can
use
to
do
proper
mapping
between
the
array
of
users
matching
the
search
criteria.
If
any
and
a
fully
typed
array
that
I
can
use
to
do
data
binding
of
my
result
in
the
UI
of
the
client
web
part.
A
This
is
one
option
using
the
aad,
HTTP
client
and,
as
I
said,
that
you
can
use
it
for
first
parties
or
third
party
API
so
for
the
Maxo
graph
or
for
any
other
third
party
API.
Moreover,
if
your
target
is
just
and
only
the
micrograph,
you
can
even
use
the
MS
graph
client
type,
which
is
yet
another
new
type
in
which
will
be
introduced
in
the
upcoming
release
of
SPF
EXO
and
with
the
MS
graph
client.
You
will
create
a
client
object,
ready
to
go
ready
to
consume
the
my
graph.
A
Only
as
you
can
see,
you
still
need
to
use
the
service
scope
of
the
SPF
ex
context.
You
will
need
to
provide
the
service
key
of
the
match
of
graph
and
using
these
kind
of
fluent
API,
where
you
mix
fluent
metal
and
strings
like
here,
and
here
and
here
you
define
that
you
want
to
use
the
API
for
the
users
in
version
1.0,
you
want
to
select
those
properties
of
every
single
user.
A
Matching
the
filtering
criteria
provided
right
here
and
the
filtering
criteria
will
be
that
will
still
be
an
open
data
protocol
filter,
based
on
a
string
that
you
have
to
provide.
Then
you
make
an
HTTP
GET
request
and
you
get
back
as
like
as
before.
It
is
an
object
that
you
need
to
map
to
a
result
which,
in
our
scenario
in
our
sample,
will
be
bounded
to
a
list
to
a
detail
list
of
office
UI
fabric.
So
that's
it
from
a
development
perspective.
A
Once
we
have
done
that,
you
will
need
to
bundle
your
solution
and
to
package
your
solution
so
that
you
will
get
back
an
SP
pkg
file
that
you
can
simply
deploy.
You
can
simply
install
in
the
app
catalog
of
your
tenant.
So
let
me
go
to
the
app
catalog
of
my
target
tenant
and
let
me
get
the
SP
pkg
file
just
to
show
you
what
will
happen,
drag
and
drop
the
file
on
the
app
catalog
and,
as
usual,
you
will
see
the
prompt
UI
to
deploy
the
package
in
your
application
cattle.
A
But,
as
you
can
see
here
in
the
lower
part
of
the
screen
of
the
pop-up
dialog,
you
also
have
please
go
to
the
storage
principle.
Permissions
management
page
to
approve
pending
permissions,
why
it
is
happening
because
in
the
package
solution
that
JSON
file,
we
declared
one
or
more
web
api
permission
requests,
and
because
of
that,
we
will
need
to
go
to
the
admin
UI
of
sharepoint
online.
So
let
me
do
that
so
we
will
need
to
use
the
new
admin
center,
which
is
under
preview
right
now.
A
So
click
on
this
guy
and
in
the
UI
we
can
access
the
app
management
link
through
which
we
can
see
all
of
the
permissions
already
applied
or
those
still
pending
approval.
And,
as
you
can
see
here,
we
have
three
permissions.
We
are
already
which
are
already
active
and
two
more
which
are
still
pending
approval.
You
can
select
any
of
the
pending
approvals,
permissions
requests
and
you
can
approve
or
reject
them
from
it
admin
perspective.
A
So
basically,
a
diver
can
create
the
PAC,
as
you
give
it
to
an
admin
and
admin
will
deploy
the
package
in
their
catalog
and
approve
the
permissions
either
using
the
web
UI
of
the
admin
center
of
sharepoint
or
using
a
bunch
of
powershell,
because
you
can
do
that
also
using
powershell.
You
can
even
revoke
a
permission
that
you
already
provided.
You
can
remove
any
already
approved
permission
if
you
want
so
that
you
have
full
control
of
all
of
the
custom
permission
scopes
both
for
the
micrograph
and
for
any
other
third
party
API
at
Tennant
level.
A
A
What
will
happen
under
the
cover
will
be
that
in
the
azure
active
directory
tenant
under
the
cover
of
your
system
fight
tenant,
there
will
be
a
sharepoint
online
client
service
principal
registered
with
a
of
permissions
configured
as
like
as
it
is
for
any
other
application
registered
in
is
ready
and
the
permissions
registered
for
that
specific
application
will
be
the
permissions
allowed
to
any
application
that
will
consume
the
graph
or
an
inter-party
api
using
the
sharepoint
framework.
That's
the
overall
idea.
A
So
let
me
switch
to
my
browser
and
let
me
show
you
how
you
can
use
this
client-side
solution,
but
before
doing
that,
let
me
start
with
gulp
serve
no
browser,
my
solution.
As
soon
as
the
solution
will
be
ready
and
running,
we
will
be
able
to
switch
to
the
sharepoint
workbench,
for
example,
in
sharepoint
online
and
play
with
the
client-side
web
part.
We
just
created.
A
So
here
we
are
in
SharePoint
Online
here,
I
already
have
my
client-side
web
part
inserted
in
a
workbench
page,
as
you
can
see
the
client-side
web
part
as
a
search
text
box,
which
is
the
one
I
used
to
search
for
any
specific
target
user
and
by
clicking
on
the
search
button.
I
will
fire
either
the
search
using
the
ad
HTTP
client
or
the
MS
Graf,
client
and
I
can
select,
which
one
I
want
to
use.
A
Using
the
configuration
panel
of
the
client-side
web
part
I
can
select
the
Ald
client
or
the
MS
Graf
client
by
clicking
on
the
search
button,
a
an
authentication
process
will
start
which
will
leverage
ad
I
LJ
s,
so
Active
Directory,
authentication
library
for
JavaScript
under
the
cover
to
retrieve
an
open
authorization
access
token
which
will
be
used
to
consume.
In
this
scenario,
demographer
or
whatever
else,
third
party
API.
So,
let's
play
with
it
and
let's
see
how
it
works,
we
are
searching
for
user.
A
One
click
on
search,
a
pop-up
dialog
will
pop
up
to
get
me
who
out
access
token.
We
have
the
result
from
the
graph
we
can
switch
to
ms
graph
client
as
well.
We
can
make
another
search
and
that's
it.
It
works
like
a
charm.
So
let
me
go
back
to
the
source
code
and
I
think
that's
it.
We
saw
how
you
can
use
both
the
ms
graph
client
or
the
aad
HTTP
client
to
consume
the
max
of
graph
or
any
third
party
API.
A
Real
enterprise-level
solutions,
adding
a
bunch
of
REST
API
in
the
backend
I
mean
third
party
API
is
secured
using
Azure
ad
and
open
authorization,
and
that's
great
so
I'm
really
looking
forward
to
having
this
capability
in
preview.
For
anybody
else
on
the
network
and
Thank
You
Vera
stage
back
to
you.
C
Because
this
is
so,
this
is
using,
what's
called
Monaco
editor,
which
is
kind
of
the
base
for
visual
studio
code.
So
we
get
nice
things
like
you
know.
When
we
have
problems
here,
you
can
start
to
see
it
highlights
the
line
with
as
a
problem.
If
you
hover
over
the
squiggly
right,
you're
gonna
get
a
hint
as
to
what's
going
on,
does
have
this
little
guy
over
here
in
the
preview
pane
so
giving
you
more
hints
exactly
what's
kind
of
going
on
with
the
JSON
or
the
column
formatting
errors
itself.
C
So
you
can
correct
that
and
you'll
notice
that,
as
you
correct
things
and
as
you
type
don't
think
begin
to
show
up
as
expected,
so
I
can
see
field
start
to
see
the
display
right
there.
Now,
because
this
is
using
editor,
we
get
a
lot
of
other
code
features
here
right
we
can
get
code
folding,
we
also
get
a
command
palette.
So
if
you're
gonna
hit
f1
you're
gonna
get
access
to
a
ton
of
stuff,
so
I
can
type
them
like
fine.
C
Here,
I
get
a
nice
fine
window,
so
I'm
trying
to
are
all
those
automation
points
are
I.
Can
also
expand
that
and
do
a
replace
whatever
I
need
right.
We
also
get
some
theming
options
here.
I
can
kind
of
change
that
around.
So
where
does
this
data
come
from?
Well,
if
we
take
a
look
over
here,
expand
that
over
here
all
of
that
is
totally
customizable.
So
if
you
want
to
add
some
additional
items
right
here,
so
you
know
you
want
generous
butter.
No,
it's
always
butter
right.
C
You
could
put
you
know
generous
dude,
that
kind
of
thing
all
right
so
to
get
exactly
the
kind
of
values
you
want,
but
because
column
format.
It
also
lets
you
reference
other.
You
know
items
within
your
row.
You
can
add
additional
columns
here
and
you
can
set
those
types
to
whatever
you
need
all
right.
So
you
want
to
do
a
date/time.
You
want
to
change
those
up
or
you
can
do
a
person
and
you
can
set
the
the
email
address
or
what
are
the
other?
C
You
know
property
if
you
want
to
set
all
that
to
make
sure
that
you're
getting
exactly
what
you
want
over
here
as
you're
working
on
your
code,
okay,
alright!
So
one
of
the
other
things
you
can
do,
though,
so
you
can
always
start
from
scratch,
but
you
can
also
open
items
so
say:
you've
got,
you
know
an
existing
cone
for
maybe
someone
else
put
it
together.
You
like
it,
but
you
want
to
switch
it
up
just
a
little
bit.
So
what
you
can
do
is,
you
could
say,
open
from
a
local
list.
C
C
An
even
easier
way
to
get
going
with
this
stuff
is
to
use
one
of
these
wizards
and
templates
there's
currently
ten
of
them,
but
those
are
fully
extendable
and,
if
you're
looking
for
a
way
to
contribute.
That
is
an
awesome
way
to
contribute.
Please
do
so
you're
gonna
pick
your
column
type,
you
know
so
we'll
say
in
this
case
we'll
do
a
temple
like
number
trending.
Alright,
so
a
template
is
gonna.
Give
you
a
nice
starter
set
of
data.
C
That
we'll
take
a
look
at
one
here.
So
a
wizard
provides
you
with
a
custom
interface
so
that
you
can
edit
the
values
as
needed,
and
things
will
update
directly
on
the
screen.
You
don't
even
need
to
see
the
code
if
you
don't
want
to.
Of
course
you
can
it's
fully
available
to
you
can
even
take
off
from
the
code
as
needed
and
you're
good.
B
C
So
awesome
way
to
learn,
but
now,
when
you're
all
done,
there's
a
couple
of
different
ways,
you
can
save
this.
So
if
you
want
to
save
it,
you
can
of
course
download
it'll
generate
a
JSON
file
and
put
that
in
your
downloads
folder.
You
can
also
copy
that
to
your
clipboard.
You
can
save
it
to
a
local
library.
So
you
just
pick
your
library
here
and
we've
got
my
field.
I
Jason,
just
save
that,
but
even
more
powerfully,
you
can
apply
this
directly
to
all
of
the
list.
C
So
if
we
go
back
to
that
list,
I
used
earlier-
and
we
say
my
stuff:
let's
pick
the
progress
field,
this
time,
we're
gonna,
save
that
they
take
a
look
here
and
refresh
there.
We
are
so
very
simple
for
an
end
user.
You
didn't
have
to
write
code.
You
just
customize
that
exactly
what
you
wanted
it
and
you're
good
to
go
right.
C
C
There
we
go,
we
didn't
need
to
do
anything
else.
We
refresh
that
again
there
we
are
so
Todd's,
happy
everybody's
happy
and
we're
good
to
go
a
couple
of
notes
on
this
and
how
this
was
put
together,
it's
from
a
code
perspective
and
where
this
is
located.
You
can
find
this
in
the
SP
dev
Solutions
repository.
So
if
you
guys
haven't
check
this
repository
out,
it
is
full
of
really
awesome
stuff.
C
These
are
so
in,
in
contrast
to
the
existing
SP
dev
FX
webparts
repo,
which
are
largely
aimed
at
developers
right
to
give
examples
of
very
specific
integrations
or
how
to
do
something.
These
are
fully
complete
solutions,
so
check
these
out
they're
going
to
give
you
again
because
they're
open
source,
you
can
still
learn
from
them
right
really
dive
into
the
code
as
needed,
but
a
lot
of
these
are
ready
to
go
because
they
are
fully
they've
got
a
full
lifecycle
taken
care
of
now.
B
Creased
on
that
one
where's
our
here
now
back
that
my
Wi-Fi
network
and
mesh
is
back
on
and
horrible
crashing
now
and
so
on
this
one
just
the
kind
of
a
position
this
properly
as
well.
So
absolutely
if
any
of
the
people
who
are
in
this
call
have
contributed
already
in
SPF
effects
webparts,
but
your
solution
is
suspending.
It
is
getting
more
polished,
it's
more
ready,
it's
more
and
ready
to
use
sample
solution.
B
You
can
relocate
this
and
the
wet
part
in
here,
and
because
this
is
meant
to
be
more,
let's
say,
polished
set
of
web
parts.
These
have
not
been.
All
of
this
have
been
have
not
been
also
updated,
always
to
the
latest
version
of
SharePoint
framework,
so
some
of
this
stuff
is
still
using.
For
example.
One
point
three
point:
four,
not
one
point
four
I
know
that
Chris
the
stuff
is
using
one
point,
four
because
haze
over
its
updating
his
stuff,
but
like
that
these
are
really
good
and
column.
B
Formatting
has
Chris,
has
grader
and
made
a
critic
great
you
up
also
on
a
documentation
side
around
this
one.
So
there's
a
nice
readme
and
there's
additional
dogs
which
are
explaining
how
to
web
part
is
work
so
SP
dev
solutions
on
the
SharePoint
organization
and
great
timing
from
beau
at
the
same
time
as
Chris.
So.
C
No
I,
just
a
from
a
code
perspective.
This
again
take
a
look
at
it,
but
this
is
built
on
reacts,
the
serac
web
part,
but
it's
heavily
using
react,
Redux,
which
you've
never
looked
at
that
if
you're
doing
anything
fairly
complicated
with
state
management,
Redux
you're
gonna
want
to
look
into
it.
It's
not
as
scary
as
it
seems,
there's
a
few
great
videos
and
demos
out
on
there.
C
B
And
I
paste
it
in
the
s/pdif
column,
formatting
link
also
the
ironn
window.
This
is,
and
that's
basically
for
opens
first
column
format
in
JSON
files,
so
you
can
use
Chris's
tool
and
Chris's
web
part
to
create
JSON
files
and
then
contribute
them
in
the
SPF
column,
form
thing
repository,
that's
one
way
of
contributing,
also
on
the
for
the
community
and
there's
some
new
stuff
on
that
side
as
well,
but
really
really
create
web
part.
It's
super
polished.
It's
a
sin.
B
B
And
here
we
go
I'm
just
double-checking
that
I'm
not
missing
it.
They
didn't
never
get
nowhere,
enochian
a
clearly
that
guy
doesn't
know
anything
because
he's
showing
his
hands
not
me.
But
if
there's
any
open
questions
or
open
things
which
we
did
not
probably
go
through
and
during
today
and
please
use
on
window
potential,
you
can
unplan
unmute
yourself
as
well
and
create
stuff
again
on
this
month.
B
Absolutely
we
seem
to
always
have
every
single
month,
there's
always
great
great
great
contributions
and
around
obviously
there's
involvement
of
the
guidance
and
sample
from
engineering
side
as
well
and
the
documentation,
but
also
excellent
community
contributions.
So
going
the
going
through
at
least
the
monthly
summary
will
give
you
the
height
lines
of
what
has
happened
in
the
previous
month,
because
we
do
know
that
not
that
many
people
have
a
chance
to
follow
up
on
what
we
do
on
day
to
day
basis.
B
Just
double-checking
and
that's
a
good
point
from
around
the
asset,
one
thing
as
it
packaging.
So
basically
the
web
part
is
using
the
one
point
four
default.
So
if
you
have
a
office,
resistor
5c,
then
pop
its
data
and
enabled
it's
going
to
serve
the
assets
directly
from
CDN.
If
it's
not,
then
it's
going
to
serve
two
assets
directly
from
the
site:
site,
collection,
app,
catalog
or
potentially
from
a
site.
B
And
that's
a
good
point
from
Chris
and
that's
something
which
I'm
not
sure
if
we,
if
you
never
actually
mentioned
that
mark
mentioned
that
in
the
in
the
some
of
the
videos.
But
if
you
have
enabled
office
365
public
CDN,
the
enabling
and
when
you
enabled
office
365
proxy,
then
we
do
set
the
default
origins,
the
for
the
public's
again
and
if
you're
not
actually
enabled
office365
public
CDN
before
the
one
point
for
going
live.
B
When
we
introduced
this
new
site
assets,
CDN
origin,
that
city,
an
additional
origin
was
not
created
by
default
automatically
in
the
CDN.
So
now,
if
you
need
to,
if
we
want
to
use
to
office,
365
public
CDN,
just
disable
and
enable,
and
that
will
create
the
client
side
as
its
default
origin
or
you
can
add
a
new
origin
within
your
tenant
by
using
the
SB,
sorry,
add
SB,
tenant,
CDN
origins,
comic
line
or
office,
365
C,
SEO
I.
That's
actually
capable
of
doing
that
as
well.
B
Those
common
format,
error
solution,
works
in
the
SharePoint
2016
on-premises
nope,
because
it's
using
one
point
four.
So
at
the
one
point
the
SharePoint
2016
feature
back
to
is
basically
using
the
SharePoint
framework
1.1
version
of
the
SharePoint
framework.
So
it
is
something
which
might
be
evolving
in
SharePoint
final
16
in
the
future.
B
Most
likely
will
not
super
fast,
and
we
can
promise
that
that's
going
to
happen
in
shape
or
2019,
there
will
be
a
new
version
supported
in
on-premises
and
the
reason
why
we
support
1.1
in
on-premises
is
that
there's
an
on
premise
that
there
is
a
server
side
dependency
on
SharePoint
framework.
So
you
cannot
use
the
1.4
on
on-premises
without
updating
the
server
side
as
well,
and
we
haven't
actually
updated
the
server
side.
Well,
there
has
not
been
any
additional
feature
packs
for
SharePoint
2016
since
to
feature
back
to.
C
B
So
calling
other
permissions
besides
groups
and
reports
using
Kravitz
it
reclines
it's
already
life.
No,
it
isn't
so
that's
something
which
isn't
available
yet
it
will
be
available
relatively
soon.
If
you
follow
up
on
our
social
media
channels,
a
Twitter
and
Facebook
and
our
box,
you
will
see
whenever
the
the
additional
scopes
and
the
additional
configuration
options
is
fully
supported
and
available
there.
So
you
will
absolutely
follow.
We
will
follow
up
on
the
guidance
will
have
videos
and
everything
else
available
at
that
point.
That
was
a
preview.
What
polisher
today
on
the
upcoming
capability?
B
There
might
be
some
changes
around
details
of
that
one
in
the
before
we
actually
goes
like
any
prediction
for
column
folding
in
a
list
views
webparts
to
be
available.
Well,
we
know
to
ask
one
thing:
might
be
that
you
actually
would
go
to
the
SD
depth
and
docks
issue
list
and
request.
And/Or
have
a
question
there,
because
then
we
can
easily
reroute
that
to
the
owners
of
the
column
formatting
capability,
and
they
will
see
that
hey,
there's
a
demand
making
this
happen.
Now.
B
B
Please
let
us
know
also,
please
use
the
tech
communities
for
asking
questions.
We
tried
to
follow
up
on
them
as
well
and
also
there's
way
too
many
channels
to
keep
up
with
there
with
the
things
this
one
was
a
great
great,
great,
no
doubt
monthly
webcast.
We
have
the
recording
saved
a
double
check
from
my
camel
on
as
a
mic.
B
Thank
you
for
saving
our
recording,
so
I
have
to
start
my
Hester
ending,
so
we're
able
to
combine
that
using
Grahams
the
Camtasia
magic
and
most
likely
will
have
a
fully
functional
full
recording
available
tomorrow
within
24
hours
in
the
YouTube
channel,
and
have
a
look
on
the
Twitter
tweets
when
the
recording
is
available,
if
you're
interested
on
sharing
this
one
for
anybody
else.
But
thank
you
everybody
for
joining.
Thank
you,
Chris,
Alex
and
Paulo
for
your
demos
and
thank
you.
Everybody
else
for
your
contributions
for
this
monthly
summary.