►
Description
SharePoint Developer (SP PnP) Community call recording from 13th of November 2018. Summary of the activities happened in the past month around SharePoint development guidance, roadmap updates, future plans for the SharePoint development.
Demo – David Warner - List Formatting deployment and development with VS Code
Demo – Patrick Rodgers - How to simplify your JavaScript development towards SharePoint REST APIs with PnPjs latest capabilities
Detailed agenda an links to specific sections available from https://developer.microsoft.com/en-us/sharepoint/blogs/
You can download recurrent invite for the monthly SharePoint community calls from http://aka.ms/spdev-call.
A
Oh,
this
is
a
SharePoint
dev
ecosystem
monthly
community
call
for
November
2018
is
November
13th,
and
this
is
our
monthly
call
when
I
thank
everybody
for
joining
again.
Apologies.
If
you
had
a
little
bit
of
difficulty
getting
in
this
morning,
we
were
scrambling
to
fix
a
broken
Skype
meeting.
Invite
so
apologies
for
that.
The
aka
link
should
now
be
updated
and
working
for
folks
and
based
on
the
number
of
people
joining.
It
seems,
like
that's
probably
the
case.
So,
let's
get
started
our
agenda
for
today.
A
Some
of
the
really
want
to
highlight
some
of
the
great
contributions
from
folks
we
got
in
last
month's
release
and
then
at
the
end,
we'll
have
a
little
bit
of
time,
I
think
for
Q&A,
but
we
shall
see
first
off.
We
always
like
to
start
with
a
little
bit
of
a
description
about
the
SharePoint
developer
group,
the
the
patterns
of
practices,
community
and
sort
of
the
way
that's
set
up
and
the
number
we
have
a
number
of
calls
we'll
talk
about
those
here
and
a
little
bit,
but
as
well
sort
of
our
structure.
A
So
you
can
kind
of
imagine,
there's
this
loose
group
of
folks
in
the
middle
of
that
onion
diagram
there,
that
you
could
call
the
core
team
and
then
outside
of
that
we've
got
the
special
interest
groups
and
then
around
all
of
that
we're
all
part
of
the
entire
SharePoint
development
community.
So
some
links
there
over
on
the
Left,
SP,
P
and
P
community
will
get
you
into
the
Microsoft
tech
community
for
I'm.
Sorry,
no
excuse
me
that
gets
you
to
the
patterns
and
practices.
A
Community
page
that's
got
details
on
all
the
things
we
do
in
patterns
and
practices.
The
first
call
the
first
item
there.
The
bi-weekly
SharePoint
framework
call
is
our
first
special
interest
group
call
and
these
special
interest
groups
allow
us
to
do
a
little
bit
of
a
deep
I've
in
two
different
topic
areas.
Right
now,
we've
got
two
of
those
we've
got
the
client-side
development
SharePoint
framework
call,
and
then
we
have
a
general
development
call,
which
is
that
second
one
there.
A
So
you
can
find
the
links
to
both
of
those
you're,
of
course,
welcome
to
join
either
or
both
of
those
depending
on
your
interest
areas
and
then
as
well.
We've
got
the
monthly
community
calls
with
which
you
are
in
one
now,
and
so
those
are
sort
of
a
rollup
discussion
about
all
things
sharepoint
across
all
of
the
development
spaces,
so
whether
it's
PowerShell,
whether
it's
JavaScript
SharePoint
framework,
whatever
we
will
cover
all
that
in
the
monthly
calls.
I've
got
a
question
here.
The
SharePoint
framework
call
is
on
Thanksgiving
in
the
US.
Yes,
it
is.
A
We
are
going
to
have
that
call
because
not
everybody
is
in
the
US,
but
understand
it'll,
probably
be
lighter
attendance
for
folks.
So
no
worries,
if
you
can't
make
it
will,
of
course
get
it
recorded
and
will
be
out
there
in
the
YouTube
channels
for
folks
to
watch
after
the
fact.
But
it's
it's
just
a
little
too
difficult
to
reschedule
something.
You
know
if,
like
a
Wednesday
or
something
like
that
with
that
gets
this
many
participants,
so
is
gonna,
be
on
Thanksgiving.
A
So
getting
into
some
of
our
monthly
metrics
I'll
go
through
some
of
these
numbers.
But
really
this
slide
is
all
about
saying.
Thank
you
to
all
of
you
out
there
in
the
community
for
helping
us
grow,
what
we
do
and
being
part
of
what
we
do
by
by
your
contributions
by
your
participation
and
by
you
know,
just
sort
of
being
part
of
the
entire
SharePoint
development
community.
So
some
some
high-level
statistics
just
to
give
you
an
idea.
We've
got
one
hundred
and
seventy
eight
thousand
minutes
of
watch
time
in
YouTube.
A
That's
coming
off
of
27
thousand
views.
We've
got
fifty-two
thousand
unique
visitors
in
github,
that's
a
two-week
rolling
average
as
well
as
253
thousand
views
of
our
github
content.
Again,
that's
a
two
rolling
average
and
then
our
Microsoft
documentation,
Doc's
top
microsoft.com
around
SharePoint
development
is
getting
almost
a
million
views
a
month
now.
So
that's
up
to
960
thousand
views.
A
So
that's
really
a
testament
to
all
of
you
and
the
growth
of
SharePoint
develop
the
continued
growth
of
SharePoint
development
across
all
the
topics
and
especially
SharePoint
framework,
and
then
we're
seeing
some
really
impressive
stuff
around
the
reusable
components
and
those
reusable
components
are
really
everything
that
we
in
P&P
do.
So
that's
the
PowerShell
libraries,
that's
the
sison,
libraries,
the
JavaScript
libraries,
that's
the
reusable
controls,
that's
the
CLI!
A
That's
the
new
yeoman
generator,
which
we
talked
about
on
the
last
special
interest
group
for
client-side
development
last
Thursday,
so
we're
seeing
10
billion
requests
coming
through
all
of
those
things
into
office,
365
we're
seeing
and
that
doesn't
actually
even
capture
the
stuff,
that's
being
used
on
premises.
So
that's
even
bigger
number:
we've
got
17,000
almost
18,000
unique
tenants
or
using
something
out
of
patterns
and
practices,
and
the
the
most-used
capability
continues
to
be
the
provisioning
engine
for
I,
think
obvious
reasons
being
its
incredible
capabilities
and
how
it
really
simplifies
the
deployment
for
folks.
A
But
everything
else
is
creeping
up.
We're
seeing
increased
usage
across
everything
patterns
of
practice
is
doing,
and
again
all
of
this
is
just
a
roundabout
way
to
say
thank
you
to
all
of
you
out
there
for
being
part
of
this,
helping
us
grow
and
helping
us
get
better
by
your
contributions
and
your
feedback.
So
thank
you
to
all
of
you
out
there
very
much
so
how
about
Shefford
framework
how's
the
adoption.
A
So
these
are
two
graphs
that
show
growth,
but
what
they're
saying
is
usage
per
user
and
usage
per
tenant
is
both
going
up
and
the
reason
we
show
these
and
talk
about
these
is
we
get
questions
a
lot
on
both
from
individuals
and
from
companies?
Are
people
actually
using
SharePoint
framework?
Should
we
invest
in
SharePoint
framework?
A
Should
we
begin
transitioning
to
SharePoint
framework,
and
the
answer
is
absolutely
yes
on
those
things
you
should
definitely
begin
to
transfer
to
SharePoint
framework
have
a
look
at
what
SharePoint
framework
can
do
for
you,
both
in
the
cloud
and
for
newer
versions
of
SharePoint
on-premises
as
well.
Definitely
check
that
out
we're
seeing
tremendous
growth.
So
this,
what
this
means
in
kind
of
a
big
picture
sense
is
continuing
investment
for
Microsoft
to
grow.
A
It
continue
an
investment
in
the
community
and
continued
investment
in
new
features
for
the
foreseeable
future,
so
definitely
time
to
jump
over
to
SharePoint
framework
begin
learning
that,
if
you
have
not
already,
if
you're
looking
for
documentation
and
guidance
on
SharePoint
development,
definitely
check
out
SP
dev
Docs,
that's
a
kms
/
SP,
dev
Docs.
That
will
take
you
to
the
Microsoft
SharePoint
development
documentation,
and
this
is
a
SharePoint
documentation
for
developers
all
up.
A
So,
if
you're
new
to
SharePoint
framework,
this
is
going
to
have
information
on
getting
starting
point
framework,
how
to
set
up
your
development
environment
tutorials
to
walk
through
on
setting
up
your.
You
know.
First
web
part,
your
first
extension
how
to
deploy
those
things
and
get
started
as
well
as
more
advanced
topics
on
their
documentation.
Around
SharePoint
capabilities
itself,
such
as
the
rest
services
web
hooks
as
well.
You'll
have
documentation
there
on
SharePoint
add-ins
on
manage
code
development,
so
the
old
w
is
not
old.
A
Does
the
still
existent
WSP
model
if
your
on-premises,
as
well
as
overview
and
general
guidance
around
sharepoint
development,
so
we're
working
on
getting
everything
consolidated
there
and
you
know,
of
course
not
everything.
Is
there
not
everything
is
perfect.
So
if
you
see
gaps,
please
let
us
know.
We
appreciate
the
feedback.
We
do
try
and
get
those
things
updated
and
then
every
time
you
report
an
issue
or
comment
on
some
of
that
documentation
that
actually
gets
turned
around
and
logged
in
github.
A
So
we
are
able
to
track
those
things
and
get
those
resolved
just
as
quickly
as
we
can
again
can't
always
get
things
updated
immediately,
but
we're
doing
our
best
and
we
appreciate
the
feedback.
So
we
you
know,
are
all
working
to
grow
and
make
things
better
across
the
documentation
for
everybody.
So
appreciate
folks
feedback
there,
as
always
like
to
mention
we
hope
you're
not,
but
if
you
are
running
into
issues
around
SharePoint
framework
or
around,
you
know
deploying
your
SharePoint
framework
solutions
or
upgrading
your
SharePoint
framework
solutions.
A
Do
please
report
those
akms,
slash,
SP
dev
issues
will
take
you
to
a
github
issues
list
and
that
is
monitored
by
their
SharePoint
engineering
team
themselves.
To
get
those
resolved,
gets
you
feedback
on
your
issues
and
make
sure
that
we're
getting
responses
to
people
so
that
we
can
again
make
everything
better
for
everybody.
So
issues
range
from
bugs
requests
for
enhancements,
or
you
know
just
sort
of
general
comments,
though
general
comments
are
generally
better
for
user
voice
or
for
the
Microsoft
tech
community.
A
But
you
know
if
you're,
seeing
a
real
blocker
just
inside
SharePoint
itself,
you
can
report
it
there
and
we'll
do
our
best
to
get
it
routed
to
the
right
team
and
did
want
to
mention.
Obviously
you
know
lots
of
people
reporting
issues,
so
we
are
doing
our
best
to
catch
up
on
those,
and
you
know
work
on
an
internal
plan
on
how
to
triage
those
a
little
bit
better
and,
as
all
of
you
know,
it
always
comes
back
down
to
resource
availability
and
how
we
can't
ask
our
time
and
get
the
right
focus
there.
A
But
we
are
working
on
that
and
we
do
try
and
be
as
responsive
as
we
can.
So
if
you
are
seeing
problems,
definitely
please
report
those
issues
and
we
will
do
just
our
best
to
get
those
resolved
as
quickly
as
we
can
so
now.
Sharepoint
framework
1.7
is
now
available
that
was
released
into
GA,
so
some
big
things
there
coming
out
of
this
release,
so
dynamic
data
sharing
between
components
is
now
in
GA,
which
is
a
big
step
forward.
A
There
support
in
SharePoint
2019
in
the
yeoman
generator
I'm
sorry
should
support
for
SharePoint
2019
in
the
OMA
generator
domain,
isolated
webparts,
which
I
think
is
a
super
great
addition
here
and
that's
gonna,
get
you
some
enhanced
security
for
scenarios
where
you
need
certain.
You
know
that
sort
of
extra
security
for
your
web
part-
or
perhaps
you
want
to
have
your
own
as
your
Active
Directory,
app
ID
for
some
functionality
in
one
web
part,
but
maybe
don't
want
to
grant
those
permissions.
A
You
know
to
every
SharePoint
framework
web
part
that
might
get
deployed,
so
the
domain
isolated
web
parts
are
a
great
way
to
accomplish
that
as
well.
You've
likely
a
lot
of
you
have
seen
the
demos
or
the
posts
around
the
Microsoft
teams
experience,
so
you
can
now
actually
show
and
deploy
your
SharePoint
framework
content
in
teams
as
a
tab,
which
is
super,
powerful
and
sort
of
hints.
I
guess
I
can
say
this
out
loud
hints
towards
the
direction
we
might
be
going
with
a
lot
of
our
office
development.
A
So
definitely
have
a
look
at
that
support
for
teams
apps
in
SharePoint.
So
that's
kind
of
a
two-way
support
back
and
forth.
We've
got
list
subscriptions
have
come
in
and
then
something
that
could
get
that
hasn't
gotten
a
ton
of
press
but
I
think
is
gonna
prove
to
be
really
valuable.
Moving
forward
is
the
single
page
apps.
So
that's
sort
of
immersive
experience
for
single
page
apps,
I.
Think
folks,
you'll
be
able
to
do
a
lot
of
really
cool
stuff.
A
With
that
you
know
kind
of
opens
up
some
new
scenarios
and
I
think
we'll
see
some
really
cool
things.
So
if
you
do
some
cool
stuff
with
one
point
seven
and
would
like
to
demo
your
work,
please
let
us
know
we'd
love
to
get
you
on
an
upcoming
call
for
a
demo
again,
I've
I
always
say
it
and
I'll
continue
to
say
it.
A
We've
got
all
of
our
products
are
now
updated.
Products
in
quotes
are
now
updated,
open
source
things
are
now
updated,
so
the
JavaScript
library,
this
Isan
stuff
is
updated.
The
PowerShell
is
updated.
The
provisioning
code
within
the
core
libraries
is
updated,
so
we've
got
all
our
latest
fiction.
Bla
latest
fixes
and
want
to
thank
again
everybody
that
contributed
across
all
of
the
many
things
we're
doing
it's
kind
of
when
you
take
a
step
back
and
look
at
the
growth
and
look
at
what
we've
been
able
to
do
again.
A
That's
all
up
to
all
of
you
in
the
community
supporting
it
and
helping
us
by
reporting
issues
and
submitting
your
contributions
to
github
and
helping
us
grow
it.
So
it's
really
impressive
and
if
you're
not
using
all
of
the
things,
definitely
I'd
encourage
you
to
try
out
the
different
areas
in
patterns
and
practices.
You
might
find
some
new
capabilities
that
might
help
you
on
some
of
your
projects,
so
we're
doing
our
best
and
appreciate
all
of
your
help
and
your
best
to
get
us
there.
A
So
thanks
to
everybody
again
out
there
in
the
community
and
then
we
have
an
ongoing
a
weekly
sorry,
let's
find
somebody
there
and
meet
cute.
So
please
do
remember
to
mute
as
you
join
the
call.
It
really
helps
with
the
recording
and
so
SharePoint
dev,
weekly
I
guess
we're
calling
these
a
podcast
or
a
webcast.
But
these
are
super
informal,
fun,
I'd
say
around
about
thirty
minutes.
But
if
you,
if
you've
ever
been
on
a
call
to
vase
of
30
minutes
is,
is
just
a
loose
idea.
A
But
these
are
a
cool
summary
of
kind
of
what's
been
going
on
that
week
in
SharePoint
development,
so
it
might
be
talking
about
new
releases
might
be
talking
about
a
certain
area
of
SharePoint.
It
might
be
talking
about
a
specific
demo,
but
it's
a
fun
informal
kind
of
weekly
chat,
so
it's
usually
visa
and
Waldeck
and
then
a
special
guest.
This
last
week,
Valon
was
on
there
and
in
in
previous
weeks
we've
had
Paulo.
A
Wake
up,
early
yeah
well
have
about
one
and
a
half
year
old,
so
I
wake
up
early,
all
the
time,
as
always
just
stay
up
late.
That
would
be
powerful.
Thank
you
for
your
assistance
within
last
month.
So
I'm
not
gonna,
read
all
these
names
because,
as
there's
just
too
many
of
you
folks
but
I
think
I've
said
thank
you
about
a
dozen
times
so
far
and
we'll
continue
to
do
that.
But
thank
you
all.
You
really
do
make
our
work
possible
and
you
make
this
community
possible.
A
So
thank
you
to
everybody
and
for
folks
looking
to
get
involved.
Please
do
a
great
way
to
get
involved
is
to
jump
in
report.
An
issue
submit
a
pull
request.
You're
involved
already,
just
by
joining
these
calls
and
seeing
the
community
grow
is
really
rewarding
for
us
and
hopefully
wording
for
all
of
you
who
are
benefiting
from
and
contributing
to
the
growth
of
that
community.
So,
thank
you,
everybody.
Thank
you.
Thank
you.
Thank
you
really
can't
say
that
enough,
and
we
very
much
appreciate
it
from
all
of
you
as
well.
A
We
do
want
to
call
out
some
of
the
companies
that
specifically
allow
their
folks
or
give
their
folks
time
to
contribute
to
patterns
and
practices
and
help
to
grow
that
as
well,
either
by
incorporating
that
into
their
training
or
allowing
their
folks
dedicated
time
to
contribute
back
to
patterns
and
practices.
So
I
want
to
thank
all
of
these
companies
for
their
time
and
allowing
their
folks
to
work
on
the
patterns
and
practices.
So
these
are
folks
who
have
sent
us
their
logos
and
are
allowing
us
to
use
their
logos
here.
A
If
you
work
for
a
company
or
own
a
company
and
your
company
is
giving
you
dedicated
time
to
work
on
patterns
and
practices,
and
they
would
like
their
logo
included
here,
happy
to
do
that.
Please
reach
out
to
us
and
we
will
get
you
guys
get
your
logo
set
up
on
this
slide
and
as
well
into
the
Thanks,
but
we
just
sort
of
need
your
clear
kind
of
written
permission.
That
can
be
something
like
we
give
you
permission
to
use
our
logo
on
the
slide,
that's
great,
but
just
something
in
the
logo.
A
You
would
like
us
to
use,
and
we
can
get
that
up
here
as
well.
So
thank
you
to
all
these
companies
for
allowing
their
folks
time
to
contribute
back
to
patterns
and
practices.
So
very
much
appreciate
that
and
then
I
want
to
thank
as
well
folks.
These
are
folks
internal
to
Microsoft
that
are
helping
one
way
or
another
either
you'll
see.
Some
of
these
names
are
the
folks
actually
creating
the
SharePoint
framework,
for
example,
or
creating
other
features
of
SharePoint
or
our
marketing
folks
or
pm'n.
A
Folks
and
some
of
the
rest
of
us
just
happen
to
work
at
Microsoft
and
contribute
and
be
part
of
patterns
and
practices.
So
thanks
as
well
to
all
of
you
inside
Microsoft,
who
are
helping
out
to
either
make
it
make
SharePoint
a
thing
or
help
us
grow
and
make
patterns
and
practices
better.
So
thank
you
to
all
of
you
as
well.
A
So
a
quick
note,
one
of
the
things
we've
been
talking
about
in
the
core
team
is
around
this
idea
of.
Are
we
hat?
Are
we
doing
too
many
calls
now,
if
you
kind
of
oversaturated
things,
so
we
have
the
the
bi-weekly
special
interest
group
calls.
We've
got
this
monthly
call.
We
have
now
the
weekly
SharePoint
dev
podcast,
which
is
as
much
a
call
but
as
more
content
and
as
well.
We
have
the
videos
that
come
out
fairly
frequently.
So
is
this
just
too
much
content?
A
A
If
you
care
to
take
it's
like
I,
think
a
question
and
a
fill
in
the
box.
A
survey
I,
don't
you
know,
give
us
your
credit
card
number
or
anything
but
check
that
out.
We'd
appreciate
your
feedback.
Definitely
if
your
feedback
is
keep
them
all
I
would
love
to
hear
that
if
your
feedback
is,
you
know
we
could
drop
one
or
the
other.
You
know
we'd
love
to
hear
from
you
again.
Everything
is
feedback
driven.
So
this
is
us.
This
was
just
sort
of
came
up
and
discussion
and
the
result
of
that
discussion
was
well.
A
Let's
just
ask
the
community
and
you
know
so.
This
is
us
asking
you
in
the
community
I
appreciate
everybody
saying
keep
them
all
here
in
the
I''m
window.
If
you
could
just
take
a
minute
and
go
to
the
SP
dev
call
feedback,
link
there
and
just
say
keep
them
all.
That
is
great,
so
we'll
do
our
best
there.
So
you
know
appreciate
everybody's
enthusiasm
and
if
folks
want
us
to
keep
them,
we're
definitely
gonna
keep
the
calls
like
that's.
You
know,
like
I,
said
we
thought
we'd
ask
and
we
didn't
know.
A
Maybe
people
would
say
we
have
too
many.
It
takes
up
too
much
time
or
what
so
you
know
we
definitely
will
keep
them.
If
that's
where
the
feedback
lens
questionnaire,
is
there
a
way
to
get
some
live
support
to
our
questions
and
the
answer?
There
is
really
just
no
not
through
patterns
and
practices.
We
just
can't
a
scale
for
that.
So,
depending
on
what
your
question
is,
you've
got
Microsoft
premier
support,
depending
on
what
your
relationship
with
Microsoft
is.
You
might
have
some
free
hours
there
you
know,
but
we
really
can't
scale
to
just
give.
A
People
live
free
support
to
questions
so
I
mean
I.
Understand
why
folks
would
want
that,
but
it's
really
just
not
something
we
can
scale
to,
because
at
the
end
of
the
day,
we'd,
essentially
just
P,
providing
free,
consulting
services
and
I.
Don't
know
I've
not
taken
a
lot
of
business
classes,
but
I
don't
believe
that
scales.
Well,
is
a
business
strategy
checking
with
pets.com
and
they're
no
longer
here.
So
here
we
go
the
demos,
so
first
demo
up
is
David
David.
If
you
are
ready
to
go
and
want
to
take
over
the
presentation,
show.
B
Awesome,
thank
you
most.
Everybody
on
this
call
knows
me
by
now,
but
for
those
that
don't
my
name
is
David.
Warner
I
work
for
catapult
systems,
try
to
be
active,
really
enjoy
SharePoint
in
the
PNP
community,
pretty
positive
about
it.
It's
it's
really
been
very
useful.
So
if
you
haven't
been
involved,
definitely
definitely
try
to
get
involved
today.
We're
going
to
talk
about
list
formatting
everybody
here
knows
that
I'm
pretty
much
a
big
fan
of
its
I've
done
a
lot
with
with
Chris
and
trying
to
contribute
and
developing
with
list.
Formatting
can
be
pretty
basic.
B
There's
a
lot
of
tools.
Chris
has
created
a
really
fantastic
web
part
for
that
and
there's
other
tools
that
are
out
there
as
well.
But
when
you
get
down
to
the
basic
principle
of
creating
a
list,
formatting
definition,
whether
that's
for
column,
formatting
or
view
formatting,
there
are
some
challenges
in
the
deployment
process
right,
and
so
what
we're
going
to
do
today
is
we're
going
to
look
at
what
those
challenges
without
a
development
deployment
processes.
That's
automated.
B
What
are
some
of
the
benefits
with
it
and
then
we're
gonna
combine
a
couple
tools:
PowerShell
and
Visual
Studio
code
to
perform
that
automation
again
very
basic
strategy
here,
but
we're
gonna
see
how
it
can
maybe
make
the
experience
a
little
more,
a
little
more
seamless,
so
the
challenges
of
non
autumn,
automated
deployment,
cumbersome
copy/paste,
you
could
imagine
the
rinse
wash
repeat
process,
it's
not
hard
you're
working
with
the
vs
code,
and
you
should
be
working
with
in
vs
code
because
you
get
all
of
the
intellisense.
So
you'll
be
writing
it
you'll
copy
you'll
paste.
B
Maybe
you'll
have
to
browser
and
vs
code
up
side
by
side
and
you'll
switch
over
to
your
browser
and
you'll
paste.
It
you'll,
apply,
you'll,
say:
you'll,
see
it.
You'll
switch
back
and
you'll
start
rinse
watching,
repeat
that's
cyclical
process
right
and
it's
a
little
cumbersome,
then
with
sight
column
propagation,
because
you
can
apply
a
list
formatting
or
column,
formatting
definition
to
a
sight
column.
Then
you
might
need
to
go
to
the
column,
but
as
I
call
them
apply
it
propagate
it.
Down,
switch
over
to
your
list
refresh
and
rinse,
wash
repeat
right.
B
So
it's
a
little
a
little
bit
challenges
there.
Could
there
are
better
ways
and
there
could
be
better
ways.
The
benefits
of
an
automated
deployment
is
exactly
the
opposite
of
what
I
described.
No
beep
ace
needed
will
see.
The
JSON
definition
will
be
automatically
deployed
to
the
ListView
or
psych
column
right.
We
can
choose
on
how
we
want
to
do
that
and
then,
in
the
case
of
a
psych
column,
we
get
propagation,
so
you'll
update
the
site
column
and
then
you
don't
have
to
worry
about
going
to
the
site.
Column.
B
You'll
just
go
straight
to
your
browser,
refresh
and
you're
good
to
go
so
the
tools,
as
I
mentioned,
that
we're
going
to
use
in
this
sample
this
PNP
powershell.
So
it's
gonna
use
PowerShell,
and
it's
going
to
use
the
PNP
tools.
It's
going
to
deploy
the
list.
Formatting
definition
to
any
one
of
those
three
we're
gonna
focus
on
a
ListView
today
view
formatting
definition
and
within
visual
studio
code.
We're
gonna
use
custom
tasks
to
do
that.
B
So
we're
gonna
see
how
we
can
create
a
custom
task
that
custom
task
is
going
to
execute
a
PowerShell
script
and
then
that
will
deploy
everything
out
to
SharePoint
for
us.
So
let's
take
a
quick
look
at
the
list
that
we're
going
to
work
with.
This
is
just
a
simple
list
at
the
students
grades.
Now
this
is
using
a
view
formatting,
that's
actually
in
the
list,
formatting
repo
right
now.
So
if
you
wanted
to
go
out
and
see
it
and
play
with
it,
you
could.
But
this
is
the
the
list
in
the
raw
right.
B
It's
just
a
simple
list.
It's
representing
student
grades
and
what
it
does
is.
It
gives
each
student
a
numeric
grade
for
each
quarter
right,
so
you
got
a
99
or
an
80
or
hundred
Chris
is
way
better
than
I
am
at
school.
So
he's
got
a
better
grade
overall,
but
this
principle
obviously
could
be
applied
to
any
trending
number
across
time,
whether
it's
quarters
or
halves
or
monthly,
whatever
the
case
may
be,
so
we've
got
a
view:
formatting
definition
that
we've
applied.
B
This
is
the
one
that's
out
in
the
repo,
and
you
can
see
what
it
does
is.
It
provides
a
grade
to
each
quarter
and
that
grade
is
based
on
the
average
numeric
grade
right,
so
it
combines
in
quarter
to
combines
quarter.
One
quarter
two
numeric
grade
gives
you
the
average
assigns
a
grade
gives
you
the
average
for
one
through
three
assigns
a
grade
so
on
and
so
forth.
Alright,
so
you
can
see
exactly
how
it's
it's
trending,
it's
just
a
nice
card.
Look
to
do
that.
B
Moving
on
to
the
next
section,
it
does
utilize
the
Excel
style
formatting,
which
is
nice,
but
it
still
can
be,
which
makes
it
less
verbose,
but
it
still
can
be
a
little
bit
long
right.
You
can
get
a
little
bit
long,
so
we'll
go
ahead
and
close
that.
So
what
we're
gonna
do
is
we're.
Gonna
show
how
we
can
just
make
a
simple
change.
B
I've
got
one
here
for
my
student
grade
view
and
then
the
student
name,
we're
gonna
focus
on
the
grade
view
today
and
then
I've
got
PowerShell
scripts
that
represent
the
deployment
to
the
various
entities.
We're
a
formatting
definition
can
be
applied,
so
you've
got
lists,
call
them
you've,
got
ListView,
you've
got
sight
column
and
how
you
exit
code
execute
those
is
through
the
use
of
custom
tasks.
So
let's
jump
over
to
vs
code
and
see
how
that
looks
so
the
JSON
definition
as
I
mentioned,
it's
the
same
one.
B
You
saw
there,
it's
it's
fairly
verbose,
and
so
here
we're
looking
at
over
500
lines
of
code
right
as
you
separate
it
out
so
again.
Working
on
this
from
beginning
to
end
can
be
a
little
difficult.
What
we're
going
to
do
is
take
a
look
at
the
PowerShell
script,
so
the
PowerShell
script
is
very
simple.
It
can
be
more
robust
than
this,
but
in
its
most
simplest
form.
What
it
does
is
you
provide
for
the
view
you
provide
your
connection,
information,
your
list
name,
your
view
name
and
then
a
path
to
your
JSON
definition.
B
Right
now,
you
could
get
more
robust
in
this
there's
lots
of
different
ways
to
do
this,
I'm
just
keeping
it
very
simple
so
that
it's
understandable
and
repeatable,
and
then
what
you
do
is
the
real
magic
happens
down
here.
So
it
takes
the
list
formatting
JSON
from
the
JSON
file.
It's
it
connects
to
the
view.
B
B
Now
each
of
these
are
verbose
and
whether
or
not
they're
connecting
to
a
specific
view
or
listening,
and
so
you
would
update
the
PowerShell
for
each
time,
you're
connecting
to
a
specific
view,
list,
column,
sight,
column,
etc,
a
little
problematic,
but
not
major
you're,
usually
working
on
a
definition.
It's
it's
going
to
be
complex
in
you,
that's
where
you're
gonna,
you
know,
spend
some
time
with
it.
B
We
just
want
to
go
ahead
and
select
configure
tasks
and
it's
going
to
say,
create
a
task
JSON
file
from
a
template
right,
so
it
asks
us
which
type
of
tasks
this
is
what's
built
in
so
we'll
go
ahead
and
select
that
we're
just
gonna
go
ahead
and
select
the
default
here.
Msbuild
and
you
see
what
it's
done.
B
I
already
had
a
list
formatting
one
here,
but
I
wanted
to
show
you
exactly
how
you
can
create
it
from
scratch
and
what
it's
done
is
it's
built
this
default
kind
of
template
for
us
and
we
don't
need
any
of
this.
I've
already
got
one
that
I'm
gonna
go
ahead
and
go
over,
but
you
can
see
how
easy
it
is
to
create
so
I'm
gonna
open
this
guy,
which
is
the
true
tasks,
definition
for
us
and
I'm,
going
to
paste
it
in
here
and
then
we'll
quickly
review
it.
B
So
you'll
see
that
for
each
one
of
my
power
scripts
I've
got
a
custom
task,
a
label
which
is
what
will
show
up
when
we
want
to
execute
it
and
it
connects
to
the
different
PowerShell
scripts.
So
we
see,
we've
got
a
site,
column,
a
list
column
and
a
list
view.
Of
course.
This
is
the
one
we're
gonna
focus
on
today,
because
our
PowerShell
script
is
going
to
connect
to
this.
To
this
view,
formatting
definition
and
it's
going
to
connect
to
my
SharePoint
site
and
it's
going
to
play
it.
So
it's
very
easy.
B
So
we've
put
this
in
here:
we've
got
three,
so
I'll
go
ahead
and
close
that
now
we
want
to
go
ahead
as
I
mentioned
and
just
apply
some
simple
text
shading
or
shadowing
to
the
student
name,
so
I'm
gonna
go
ahead,
make
my
change.
We're
gonna
go
ahead
and
give
it
a
try
with
just
a
couple
of
pixels
and
orange.
So
I'll
save
that
and
then
to
execute
that
task.
You
just
reengage
the
command
palette
and
select
run
task
again.
B
You
can
search
on
tasks
and,
if
you're
running
this
quite
a
bit,
it's
going
to
nicely
populate
to
the
top
there.
For
you
and
so
we'll
go
ahead,
select,
run
tasks
and
what
you
see
is
now
it's
it's
aware
it
sees
the
tasks
that
JSON
it's
aware
of
the
tasks
that
I've
defined.
That
I
want
to
do,
and
it
gives
me
the
choice.
B
Obviously
I've
been
running
through
my
demo
to
make
sure
it
works,
so
list
of
you,
formatting
is
bubbled
up
to
the
top
as
a
recently
used
task
will
go
ahead
and
select
that
and
we
get
a
get
an
option
about
scanning
outputs
and
all
the
different
things
that
we
could
do
to
scan
the
output.
In
this
case,
we
don't
necessarily
need
to
do
that,
so
you
can
just
simply
say
continue
without
scanning
the
task
output.
B
Now
what
happens
is
it
brings
up
the
terminal
down
here
and
it
executes
the
PowerShell
script
and
then
the
PowerShell
script
just
has
a
nice
little
output
of
everything
ran
right.
Listview
formatting
definition
has
been
updated,
so
we're
gonna
go
back
to
our
list
here,
we're
gonna
refresh
and
we
see
okay,
great,
it's
been
executed
and
it's
deployed
it
a
little
hard
on
the
ice
write.
All
this
may
be
a
little
hard
in
the
eyes,
but
I'm
matching
my
color
scheme.
B
So
we're
gonna
go
back
into
vs
code
and
we're
just
gonna
go
ahead
and
change
this
to
silver
save
hit
f1.
You
can
see
how
fast
we
can
do
this
cuts
you
in
that
scan.
You
could
tell
it
to
never
stand
if
you
wanted,
so
you
wouldn't
get
that
request
BAM.
It's
done.
We
go
back
to
our
browser
again
refresh
and
we
see
the
gray
is
a
little
easier
on
on
the
eyes
down,
and
so
now
you
could
further
enhance
this
envious
code.
Now
I
won't
get
into
this
example.
B
Just
for
for
purposes
of
time,
because
I
know
Patrick
has
some
demo
too.
You
could
also
tie
these
tasks
to
keyboard
shortcuts
right.
So
if
we
didn't
want
to
have
to
engage
the
command
palette,
we
absolutely
could
execute
a
custom
task
while
we're
using
a
keyboard
task
which
makes
it
even
faster,
and
that
way
you
just
ctrl
shift
F
11,
which
is
what
I
use
because
it's
available
and
it
works
great
and
it
deploys
everything
else.
So
you
can
see
the
nice
seamless
process
here.
B
You
can
also
get
more
robust
with
your
PowerShell
script,
to
open
the
browser
for
you
refresh
the
browser
for
you
automatically.
So
if
you
were
to
keep
them
side
by
side,
you
don't
need
to
go
back
over
to
the
browser
and
refresh
you
could
really
get
that
PowerShell
script
to
be
more
robust.
To
do
all
all
of
the
work
literally-
and
all
you
have
to
do-
is
keep
them
side
by
side
and
see
the
updates.
As
you
go,
it's
it's
really
powerful.
B
So
going
back
to
the
slides,
we
see
that
the
tools
and
commands
are
set.
Pnp
filled,
set
P
and
P
view
now.
You'll
notice
that
it's
a
yes
for
PowerShell,
but
it's
a
no
for
CLI,
and
so
anyone
who
doesn't
use
PowerShell
and
CLI
may
be
going
well
David
thanks
for
the
not
so
productive
productivity
tip.
You
loser.
What
about
us?
We're
not
using
PowerShell,
don't
have
to
because
waldek
rocks
so
setting
up
this
demo
in
this
strategy,
I
reached
out
to
waldek
and
inquired
on
CL
eyes
capability.
This
was
last
week.
B
So
there's
all
happened
in
last
few
days,
which
is
amazingly
awesome,
shows
the
power
of
the
community.
Spo
fieldset
SPO
list
view
set,
did
not
exist
in
the
CLI
at
that
time
they
hadn't
included
it
yet,
and
it
was
just
kind
of
over
glossed
over,
so
he
and
I
work
together,
mostly
when
I
say
he
and
I.
B
He
did
a
lot
of
the
work
in
getting
it
into
the
beta,
so
it
is
now
available
in
the
beta
and
then
he
and
I
synced
up
today
this
morning
actually
and
recorded
a
demo
on
how
that
can
be
done
with
the
CLI
and
Morse
code,
and
all
of
that,
so
it
really
is
pretty
awesome
and
now
across
the
board.
How,
across
the
community,
we
have
so
much
contribution,
and
you
can
see
with
you-
can
utilize
this
strategy
with
PowerShell
and
CLI
so
nobody's
excluded.
It
shows
the
power
of
the
community.
B
There's
gonna,
be
some
samples
that
are
input
or
going
to
be
uploaded
into
the
github
repo
for
list.
Formatting
I
believe
Chris
had
just
mentioned
me
and
said:
there's
going
to
be
a
tools
folder
there
and
I've
got
the
CLI
code
from
waldek
and
I've
got
the
PowerShell
code
myself,
so
we'll
get
those
uploaded
into
the
repo
and
that's
the
demo.
Thank
you
guys.
B
A
A
One
person
can
so
I'm,
just
gonna
assume
everybody
can
then
so
what
I
want
to
talk
about
today
is
some
of
the
updates
that
came
out
in
the
latest
PP
j
s
release
so
want
to
set
the
stage
a
little
bit.
So
what
we've
got
here?
This
is
a
SharePoint
framework
web
part,
pretty
simple
web
part.
This
is
I've
run
the
yeoman
generator
got
my
web
part
here,
and
the
only
change
I've
made
into
this
file
is
imported.
The
setup
function
from
the
common
library-
and
this
would
work
as
well.
A
You
could
do
it
from
the
SP
or
from
graph.
It
all
actually
ends
up
behind
the
scenes
in
the
same
place,
but
I've
grabbed
set
up
I've,
given
that
a
different
name.
So
it's
a
little
clearer
and
I'm
running
the
PNP
set
up
here,
I,
add
on
a
knit
method
to
the
web
part
and
what
this
does
you'll
see
this
in
the
documentation
as
well.
But
this
gives
the
library
the
context
of
your
SharePoint
framework
web
part
and
inside
SharePoint
framework.
A
A
Object
in
terms
of
URLs
and
stuff
like
that,
so
it's
very
important
not
just
when
you're
using
the
P
and
PJ's
stuff,
but
when
you're
writing
your
own
webparts
and
even
if
you're,
not
using
P
and
pjs,
you
always
base
everything
you
do
on
the
values
found
in
the
this.com
text,
object
and
that's
going
to
make
sure
as
sharepoint
framework,
possibly
expands
that
you
are
operating
where
you
think
you're
operating
with
the
right,
urls
and
so
forth.
So
we
passed
that
into
the
library
there.
A
The
PMP
set
up
and
then
that's
the
only
change
I've
made
into
this
file
and
then
I've
gone
here,
and
this
is
again.
This
is
just
the
component
that
gets
automatically
output
for
you
when
you
create
a
new
web
part
and
I've
updated
that
with
some
things
and
let's
walk
through
those
now.
The
first
thing
I
did
is
I've
got
just
a
site
script.
A
You
know
fragment
here.
It
doesn't
really
do
anything
amazing,
it's
just
as
an
example.
It
creates
a
list
named
employees
and
adds
a
field
to
it
and-
and
that's
all
well
and
good,
but
we'll
see
what
we're
using
that
for
here
in
a
second
and
then
our
render
method
I've
just
got
I.
Have
this
component
called
func
Runner
that
just
takes
an
action
and
runs
it
and
updates
itself
once
that
promise
is
fulfilled.
So
take
a
quick
look
at
that
just
so,
you
can
see
what's
happening
in
our
render.
A
So
it's
a
really
simple
little
component,
but
it's
nice
I
find
it
nice
for
testing
things
very
quickly
and
also
for
doing
demos
like
this,
because
you
don't
have
to
worry
about
formatting
you're,
really
just
concentrating
on
the
requests
getting
made.
So
I've
got
four
of
those
here
and
I
want
to
step
through
each
of
those
one
of
the
things
I
want
to
highlight.
A
This
is
a
super
simple
request,
but
what
this
is
actually
going
to
show
and
we'll
go
through
all
the
code
and
then
we'll
look
at
the
page
and
actually
see
the
stuff
run.
But
what
this
is
going
to
show
is
so
we're
gonna
connect
to
the
Microsoft
graph
from
a
SharePoint
framework.
Webpart
using
you
know
the
Azure,
Active
Directory
stuff
and
one
of
the
big
improvements
this
wasn't
actually
in
this
was
in
SharePoint
framework
1.6
and
we've
now
taken
advantage
of
it
in
the
latest
PN
pjs,
where
they'll
no
longer
be
pop-ups.
A
A
So
there's
some
new
stuff
in
there
called
the
aad
token
provider
and
you
can
grab
that's
what
we're
using,
but
you're
gonna
see
this
graph
request
work
with
no
pop-ups
and
no
other
effort
on
my
part
as
the
user,
when
this
actually
runs
and
we'll
be
able
to
get
the
list
of
groups.
One
of
the
other
things
I
wanted
to
highlight.
A
So
if
you
used
batching
in
the
SP
library-
and
you
want
to
use
batching
with
the
graph
library,
it's
the
exact
same
format,
the
exact
same
way,
you
build
your
queries,
so
we're
creating
a
batch
off
of
that
route.
Graph
object,
which,
let
me
show
you
we're
importing
graph
from
at
P
and
P
slash
graph
and
that's
the
root
of
your
fluent
API
chain.
Is
that
graph
object
in
exactly
the
same
way
that
the
SP
object
is
the
root
of
your
SharePoint
fluent
API
chain?
A
So
you
get
your
batch
off
of
create
batch
and
then
you
just
supply
it
to
each
of
these
things.
So
what
this
is
actually
saying
is:
I
want
and
I'm
not
doing
anything
with
these
results.
You
can
see
that,
but
what's
happening
here
is
we're
saying
I
want
to
get
the
groups
in
the
batch
and
I
want
to
get
my
drives
in
in
that
batch
and
calling
that
get
operation
essentially
will
queue.
The
request
into
the
batch,
something
to
note
a
lot
of
you
myself,
included
like
to
use
a
weight.
A
You
can't
use
a
weight
with
the
batching,
because
what
will
end
up
happening
here
is
this
a
weight
so
get
still
returns
a
promise.
So
I
can
do
things
like
then,
and
I
can
process
the
results
for
my
individual
requests
once
the
batch
runs
right
so
I'll
have
those
results
there,
but
get
still
returns
a
promise,
and
if
you
will
wait
here,
you'll
never
get
past
this,
because
you'll
be
stuck
waiting
for
that
promise.
To
finish
so,
when
you're
doing
batching,
you
need
to
use
the
then
syntax
to
process
your
results
individually
there.
A
So,
just
something
to
keep
in
mind
if
you're
doing
the
batching
and
that's
I
believe
called
out
in
the
documentation
as
well,
so
we're
gonna
get
those
things
in
the
batch.
So
we've
just
passed
our
batch
there
and
then
once
you've
loaded
up
your
requests
into
the
batch
one
of
the
other
things
we
added
again
from
community
feedback.
Some
great
feedback
was
in
graph.
You
have
a
limit
of
20
requests
per
batch,
so
will
actually
automatically
handle
that
for
you.
A
So
if
we
had
23
requests-
and
we
add
them
all
of
the
batch
that'll
actually
get
executed
as
two
batches
under
the
hood,
the
first
will
run
as
20
and
the
last
will
run
as
three
so
just
another
nice
feature
we've
added
in
there,
so
you
just
like
working
with
the
ESPE
library
called
batch,
execute
and
that
itself
returns
a
promise
and
batch
done.
We're
just
sort
of
this
is
what
our
result
is
gonna
be.
A
This
is
actually
what's
gonna,
show
up
in
our
little
funk,
Runner
component
and
then
two
other
great
additions
in
the
last
release
to
the
SharePoint
libraries
were
the
addition
of
site
scripts
and
site
designs.
Endpoints,
so
this
was
a
community
contribution,
great
stuff,
to
see
come
in
super
valuable
and
it
makes
it
really
easy
to
create
and
use
site
scripts
and
then
apply
those
using
site
designs.
A
So
there's
two
new
and
end
points
or
chaining
points
off
of
the
SP
object,
the
first
being
site
scripts
and
the
next
being
site
designs,
but
so
we're
just
gonna
create
a
site
script,
and
you
can
see
here.
This
is
where
I'm,
using
just
this
site
script
content
from
up
above.
So
this
is
where
you
would
insert
whatever
your
site.
Script
was
so
there's
a
lot
of
great
community
tools
out
there
now
for
building
these
sites.
A
Scripts
I
definitely
recommend
using
those
they're
super
great
check,
those
out
or
build
them
by
hand
if
you
like,
but
here
you
can
see
we're
not
doing
any
batching
or
anything.
So
we
can
use
a
weight
just
in
the
way
you
would
expect
and
then
what
we're
doing
is
calling
create
site
script,
giving
it
a
great
name.
So
we
should
call
this
demo
site
script.
A
So
we're
gonna
get
those
back,
so
you
can
actually
see
that
having
been
created,
then
let
me
jump
back
here
just
to
double-check,
this
nope
nobody's
saying
that
they've
lost
the
presentation,
so
that's
always
good,
so
they're,
looking
at
the
site
designs
here,
so
we're
actually
just
to
make
each
of
our
little
things
independent
or
actually
we'll
make
this
site
script,
five,
we're
creating
another
site
script
or
actually
creating
a
new
site
design
or
applying
that.
So
the
format
for
this
is
you
create
a
site
design.
A
You
pass
it
an
object
that
has
a
bunch
of
properties.
You're
gonna
be
familiar
with
this
if
you've
done
site
script,
site
designs
without
the
P
and
PGs
library,
but
so
we
give
it
an
array
of
ID's
of
site
scripts
to
apply
as
part
of
that
design.
So
this
can
be
one
or
more
site
scripts
per
design.
We
give
it
a
title:
I'll
give
that
a
different
number
and
then
as
well.
A
You
give
it
a
web
template
to
which
these
would
apply,
and
then
I'm
also
here,
so
we're
awaiting
Korean
death
design,
we're
awaiting
getting
the
URL
for
our
sites
or
getting
that
off
of
the
SP
library
and
then
we're
gonna
apply
the
site
design
through
another
method
using
the
site,
design
ID,
which
we
get
because
it
was
just
created
as
well
the
web
data.
This
is
our
web
data
from
this
web
request.
That's
gonna
be
the
URL,
the
absolute
URL
to
our
web,
so
that
we
can
apply
the
design
to
the
correct
web.
A
Great,
so
I
talked
about.
Let's
actually
see
this
run,
whoops,
that's
our
call
there
so
need
to
up
and
I
did
should
show
you.
I
did
run
gulp
serve
no
browser
here
before.
So
this
is
my
online
workbench,
and
let
me
just
refresh
this
just
to
make
sure
we
are
on
latest
here
and
find
our
web
parts.
This
is
gonna,
be
our
November
monthly
web
part.
So
you
can
see
each
of
our
little
things
is
going
to
be
running
there
and
they're
gonna
come
back
in
the
order.
They
come
back,
so
those
are
loaded.
A
The
graph
ones
are
loading
up
at
the
top.
We
can
see
we
created
a
site
design
and
we
got
all
our
site
designs.
So
this
is
all
the
site
designs.
Currently,
in
our
site,
we
created
a
I'm.
Sorry,
these
are
all
the
site
scripts.
This
is
the
site
design.
We
applied
that.
So
you
can
see.
This
is
the
format.
It
comes
back
as
outcome
outcome,
text
and
so
forth.
I
guess
we've
got
a
few
little
errors
in
there
whatnot
and
then
we
can
actually
see
up
here.
Our
graph
stuff
worked.
A
So
this
is
all
the
groups
that
are
in
my
little
tenant
and
then
our
batch
actually
ran
so
want
to
come.
Look
and
I
think
we'll
have
missed
it,
because
this
wasn't
running
so
I'm
gonna
have
five
again.
So
if
you
look
at
the
f5
tool,
they're
at
five
tool,
the
f12
tool
you'll
actually
be
able
to
see
in
here
as
things
spin
up,
do
here's
our
actual
batch
request
to
the
batch
endpoint.
So
you
can
actually
see
we
are
batching
our
two
requests
and
we
actually
are
getting
our
two
responses
back.
A
You
know
that
I
needed
to
do
to
log
into
the
graph,
that's
all
being
handled
by
the
great
work
done
by
the
SharePoint
framework
team
in
1.6
for
the
improved
authentication
experience,
and
you
get
that
by
just
providing
us
that
SP
context
we
talked
about
at
the
start
there
to
the
setup
method
and
then
one
thing
we
get
back
a
lot
is
with
IE
11
things,
don't
necessarily
work
as
well.
We
see
some
errors
with
IE
11,
so
this
is
IE
11,
we're
running
the
exact
same
code
and
so
like,
for
example,
here
we've
got.
A
You
need
for
the
P
and
P
J's
stuff
to
work
in
IE
11,
and
using
this
you
can
run
your
code
in
I,
11
and
everything
should
I
think
work
as
you
would
expect
so.
I've
made
this
change
and
we'll
take
a
look.
So
everything
is
spun
back
up,
we're
ready
and
so
I'm
going
to
refresh
this
page,
and
when
this
refreshes
we
should
hopefully
see
everything
once
again
work,
and
so
now
we
can
see
we
got
our
site
script,
this
site
design.
All
of
these
things
now
worked
yay
except
oops.
A
A
If
so,
the
way
the
Azure
Active
Directory
stuff
works
is
it
opens
up
a
little
I
frame
and
it
goes
and
does
the
authentication
for
you
and
get
some
tokens
on
your
behalf,
but
there's
a
situation
so
I
set
this
up
this
way
to
fail
in
IE,
11,
I'm,
actually
logged
in
with
two
separate
accounts,
my
Microsoft
corporate
account
and
my
personal
tenant
account,
and
so
you're
gonna
get
this
error
in
that
case,
request
is
ambiguous.
Multiple
user
identities
are
available
in
the
current
request.
A
So
if
you
see
this
error,
this
is
actually
there's
a
open
bug
for
this.
In
the
SharePoint
framework
repository
and
one
of
the
reasons
I
bring,
this
up
is
since
we
use
a
lot
of
the
SharePoint
framework
stuff
under
the
hood.
We
are
dependent
on
it.
So
if
you
see
bugs,
please
let
us
know,
but
just
a
heads
up,
we
might
redirect
you
to
a
SharePoint
framework
depending
on
what
those
bugs
are.
If
that's
a
capability
we
happen
to
be
taking
advantage
of.
A
So
have
a
look
at
that,
but
you
can
see
this
was
just
a
highlight
that
we
are
dependent,
but
the
real
point
of
this
is
an
I
11
using
the
polyfill
stuff.
Everything
worked
as
expected,
and
so
one
final
note
on
that.
This
is
actually
the
polyfill
library
is
separate
from
the
other
libraries
in
that
it's
not
going
to
version
each
month.
A
So
once
you've
got
that,
that
should
be
all
you
need
unless
we
have
to
add
something
at
which
point
we'll
up
version
that
but
we'll
let
people
know,
but
that's
not
something
that
will
update
monthly
unless
there's
something
we
need
to
specifically
to
add.
The
question
is
ie
8
supported
no
an
escape
navigator,
also
not
supported,
so
both
of
those
are
not
supported.
Ie
11
is
supported.
There's
a
discussion
right
now,
I
guess
there's
some
performance
or
other
issues
around
ie
11
with
some
of
the
modern
page,
stuff
and
SharePoint
framework.
A
There's
an
open
issue
about
that.
Just
a
heads
up,
but
this
polyfill
package
is
just
about
getting
the
P
and
P
J's
stuff
working.
So
one
final
thing
I
wanted
to
highlight:
we
did
get
another
great
community
contribution
made
some
great
I'm,
not
gonna,
run
any
code,
but
just
want
to
sort
of
show
you
we've
got
some
great
air
handling
and
retry
around
some
of
the
transient
errors
on
node
that
we'd
see
with
the
node
client,
so
that
was
again
another
great
community
contribution
there.
A
So
you
should
should
see
some
improved
performance
when
using
the
node
client.
So
if
I
can
find
this
and
we'll
switch
back
to
the
PowerPoint,
that
was
my
demo
there.
So
hopefully
you
folks
will
see
that
and
try
out
some
of
the
great
new
stuff
in
P
and
PJs
and
again
want
to
thank
everybody
from
the
community
that
helped
to
build
those
new
capabilities.
It's
really
some
great
new
stuff
and
look
forward
to
having
some
more
stuff
for
you
in
the
next
monthly
release.
A
A
Okay
looks
like
I
did
not
miss
any
questions
directed
at
me
great.
So,
thank
you
all.
For
the
time
there
appreciate
everyone
joining
the
call
again,
if
you
have
feedback
on
the
number
of
calls,
we
have
would
love
to
hear
that
feedback
on
the
survey.
Please
let
us
know
everybody
have
a
great
rest
year
week
and
we
will
talk
soon.
Thanks
all.