►
Description
SharePoint Framework Community call on December 17. Two demos delivered – Build Microsoft Teams me experience with SharePoint Framework and Microsoft Graph Toolkit and Introduction to PnP Search Web Parts version 4.0 release – New capabilities and features. Releases include - PnPjs v2.0.13 and PnPjs v2.1.0-beta, CLI for Microsoft 365 beta v3.4, React Controls – v2.3.0 and v1.2.1 (SharePoint On-Prem), and PnP SPFx Generator v1.15.1. SharePoint Framework v1.12 release ETA is January. Six new/updated samples rolled out in the last 2 weeks. The host of this call is Patrick Rodgers (Microsoft) | @mediocrebowler. Q&A takes place in chat throughout the call.
Demos:
• Build Microsoft Teams me experience with SharePoint Framework and Microsoft Graph Toolkit – Rabia Williams (Microsoft) | @williamsrabia
• Introduction to PnP Search Web Parts version 4.0 release – New capabilities and features – Franck Cornu (aequos) | @FranckCornu
Learn more:
• See the full blog post for this call at: http://aka.ms/m365pnp-blog
• Download invite for bi-weekly SharePoint Framework call at: https://aka.ms/spdev-spfx-call
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp-videos
A
A
So
we've
got
updates
on
sharepoint
framework
updates
on
the
patterns
and
practices
program.
We've
got
new
community
sample
updates.
We'll
do
our
picture
time
and
we've
got
two
great
demos.
Today,
the
first
from
ravia
on
building
a
microsoft
teams
me
experience
and
frank
cornu
introducing
the
pnp
search
web
parts
version
four
so
excited
to
see
both
of
those
shortly
here
in
the
call,
but
first,
let's
get
through
some
of
the
starter
stuff
here
so
often
we
get
asked.
How
can
you
participate
more
opportunities
to
participate?
A
We
got
demos,
demos,
demos,
love
to
have
you
demo
on
the
call.
So
if
you've
got
a
web
part
application,
customizer,
really
anything
spfx
related
or,
of
course
anything
from
the
patterns
and
practices
program
or
ideally,
both
would
love
to
have
you
do
those
demos
in
the
call?
So
whoever
you
are,
wherever
you
are
please
reach
out,
would
love
to
get
your
demos
booked.
We
are
sometimes
booked
out.
You
know
two
or
three
calls
into
the
future,
but
never
fear.
We
will
get
you
scheduled
in
and
we'll
love
to
host
your
demo.
A
I
think
that
and
we'll
continue
to
say
I
think,
that's
the
one.
The
best
parts
of
these
calls
is
seeing
the
great
stuff
all
of
you
out
there
in
the
community
are
building.
You
can
also
contribute
on
github
that
could
take
the
form
of
reporting
issues.
We
also,
of
course,
welcome,
pull
requests,
pull
requests
are
a
great
way
if
you
have
a
little
change,
you
want
to
see
or
a
big
change
to
get
that
in
a
little
bit
faster,
absolutely
love
those
and
to
get
those
in.
A
We
get
a
lot
of
we're
seeing
a
lot
of
great
first
time.
Contributors
come
in
recently,
which
is
fantastic.
So
thank
you
to
all
of
you
for
making
those
changes
and
making
everything
better
for
everyone,
and,
of
course,
you
can
also
help
out
with
issues
and
questions.
If
you
see
something
you
happen
to
know,
the
answer
to,
please
do
jump
in
and
let
your
voice
be
heard.
Likewise,
you
can
provide
feedback
on
all
of
the
pnp
things.
So
how
are
all
these
calls
that
we're
doing
how
our
documentation?
A
Where
can
we
help
and
positive
feedback,
is
okay
too,
because
if
we're
doing
something
you
like,
we
could
always
do
maybe
a
little
bit
more
of
it.
So
just
let
us
know
how
things
are
going
and
we'll
do
our
best
to
continue
to
improve
the
program
over
time
now
our
pedro
links.
So
we
have
developer
videos
which
are
focused
on
specific
developer
scenarios
or
tasks,
maybe
creating
a
web
part.
Maybe
setting
up
graph
connections
maybe
doing
different
tasks
around
pages
provisioning.
A
Those
sorts
of
things
are
going
to
be
the
developer,
focused
videos,
and
then
we
also
have
the
community
videos,
which
are
typically
the
recordings
of
these
community
calls
and
other
community
events.
It's
a
great
resource,
if
you
happen
to
miss
a
week
of
this
call
or
any
of
the
other
calls
great
way
to
catch
up
on.
What's
been
going
on
open
source,
we've
got
across
these
sort
of
programs
or
friends
of
pmp.
We've
got
sharepoint
pmp
office,
dev
and
microsoft.
Graph
all
have
open
source,
github
organizations
and
all
of
those
welcome.
A
Your
feedback.
Welcome
your
participation
and
you
are
encouraged
to
check
all
four
of
those
out
tons
of
great
material
tons
of
great
samples,
tons
of
great
resources
across
those
four
places.
Obviously
sharepoint
for
sharepoint
pnp
for
pnp
office,
dev
for
office
dev
stuff,
and
then
all
the
microsoft
graph
stuff
can
be
found
at
github.com,
microsoft,
graph
sample
galleries.
We've
got
samples
for
spfx,
webparts
extensions
list,
formatting
and
teams
do
encourage
you
to
check
those
out.
A
A
Ms
m365
pnp
is
the
landing
page
for
the
microsoft
patterns,
microsoft,
sharepoint
patterns
and
practices
program,
and
that
gives
you
links
out
to
all
of
our
different
program
offerings
all
of
our
videos,
all
of
our
libraries
and
resources
and
tooling,
it's
all
linked
from
there
and
all
explained
from
there.
So
do
check
out
ak.msm365pnp.
A
A
Some
missed
community
call
videos
if
you
miss
us,
but
we
will
see
you
back
in
january,
so
thank
you
all.
I
just
want
to
take
the
opportunity
to
say
thank
you.
Thank
you.
Thank
you
for
all
the
support.
Great
stuff,
great
community
work
from
everybody
this
year
in
2020,
it's
one
of
the
real
bright
spots
of
the
year
for
me
and
want
to
thank
all
of
you
for
your
participation
and
being
part
of
what
we're
building
and
with
that
I
will
hand
things
over
to.
B
David,
thank
you
patrick
well,
for
those
that
are
new
on
the
call
and
new
to
the
community.
It's
good
to
know
that
the
patents
and
practices
initiatives
are
completely
inclusive
and
open
source,
which
means
that
we
welcome
all
sorts
of
contributions
as
well
as
taking
advantage
of
using
the
resources,
but
we
know
that
sometimes
using
as
well
as
contributing
can
come
with
a
little
bit
of
a
barrier
to
understanding
how
to
do
all
of
that.
Things
like
interacting
with
github,
etc,
can
be
a
little
frustrating
and
intimidating.
So
the
sharing
is
caring.
B
Initiative
is
here
to
provide
you
sessions
that
will
walk
you
through
using
hands-on
guidance
opportunities.
We
will
work
along
with
you
in
making
things
like
your
first
time
ever
github
contribution
if
you'd
like
to
contribute
to
community
docs
start
using
the
spfx
samples,
we'll
show
you
tips
and
tricks
on
using
nvm
to
assist
with
that
and
a
whole
host
of
other
things.
B
Our
newest
topics
are
spfx,
developer,
workstation
setup.
So,
if
you're
really
new
to
development
and
want
to
see
what
the
essentials
recommended,
optional
tools
are
join
in
on
that
session
and
then
starting
in
january,
we're
kicking
off
some
amas.
Now
these
are
going
to
be
thematic,
topical
amas,
which
means
that
each
ama
will
be
dedicated
to
a
different
pnp
initiative.
B
We'll
have
the
subject
matter:
experts
and
the
owners
of
those
initiatives
present
for
you
to
ask
any
and
all
questions
you'd
like
to
ask
about
that
initiative,
and
then
that
topic
will
change
each
month,
so
we'll
start
out
with
community
docs
in
january
and
then
move
into
one
of
the
other
pnp
initiatives.
As
we
go
into
the
future
months
great
opportunity,
we
experienced
a
little
bit
of
that
open
office
hours
yesterday
on
the
watch
party
and
I
think
the
real
the
community
really
loved
it.
B
So
it's
a
great
opportunity
for
us
all
to
continue
to
collaborate
together,
aka
dot,
ms
forward,
slash
sharing
is
caring
is
where
you
can
learn
more.
As
patrick
mentioned.
The
next
two
weeks
are
clear:
to
give
everyone
an
opportunity
to
relax
and
rest
and
spend
time
with
family
and
we're
in
the
process
of
scheduling
january
events.
So
keep
an
eye
out
there,
and
we
want
to
thank
everybody
and
look
forward
to
seeing
you
in
a
session
soon.
Patrick
back
to
you.
A
Great
thanks
david,
and
these
have
been
fantastic
sessions.
We've
seen
awesome
feedback
from
these
and
seen
a
lot
of
first-time
contributors
come
out
of
these
sessions.
So
if
you're
looking
for
a
great
way
to
get
started
and
learn
a
little
bit
make
some
connections
sharing
is
caring.
Sessions
are
fantastic.
I
encourage
everybody
if
you
you'd
like
to
check
those
out
and
now
pass
things
over
to
vasa
for
our
sharepoint
framework
updates.
C
Cool,
so
it's
quickly
just
recapping
the
growth
is
still
there.
We
are
growing,
which
is
actually
quite
strange,
we're
hitting
on
the
mid
december,
but
we
still
did
the
all-time
highest
sharepoint
framework,
day-to-day
usage
on
the
mondays
or
third
party
extensibility
worldwide,
which
is
quite
insane
the
growth
curve.
This
autumn
has
been
just
out
of
this
world.
C
So
as
an
example,
the
web
part
can
request
what
is
my
wife
and
then
based
on
the
wife
of
the
web
part.
It
can
actually
behave
and
render
itself
slightly
differently
all
of
these
kind
of
things.
The
other
thing,
which
is
a
big
thing,
is
that
we
will
support
complex
microsoft
team
solution,
spfx
solution.
That
really
means
that
you
can
actually
embed
your
own
manifest.
So
microsoft
teams
manifest
inside
of
the
sbp
kj
f1.
C
So
you
can
basically
then
have
a
much
more
complicated
manifests
for
the
solutions
which
are
targeted
for
microsoft
teams
and
then
we're
looking
into
also
having
potentially
already
1.12
a
service
line.
Change
is
related
on
automatic
microsoft,
team
solutions.
So
whenever
there's
a
solution
in
spfx
which
will
be
contains
microsoft
team
solutions,
it
will
be
automatically
synced
to
the
microsoft
teams
app
catalog,
so
it
will
be
automatically
available
without
any
complex,
let's
say
syncing
or
manual
steps
over
there
and
then
we're
looking
into
having
1.13
and
1.14
within
the
spring
2021.
C
So
there
will
be
a
lot
of
actually
updates
in
pipeline
because
of
the
2020
year
being
slightly
more
slightly
complex
for
everybody.
We
haven't
had
too
many
updates
and
too
many
releases
this
year,
but
we're
getting
back
on
track
on
that
now.
A
lot
of
a
lot
of
also
teams
improvements
coming
up
store
acquisition
is
being
planned
on
so
being
able
to
target
spfx
solutions
which
are
only
for
microsoft,
teams
and
available
for
microsoft,
team
store
and
also
building
meetings,
meetings,
extensibility
for
microsoft
teams
using
sharepoint
framework.
C
We
also
have
a
new
team
in
which
is
now
focusing
on
our
store
and
modernizing
the
store
end
to
end
and
catalog
end
to
end
so
we're
finally
getting
rid
of
all
of
the
classic
experiences
related
on
adding
behavior
and
and
all
of
that,
so
making
sure
that
people
can
actually
find
what
is
shipped
on
the
store
and
how
to
get
stuff
on
things
and
one
of
the
things
which
we've
been
getting
a
lot
of
feedback
is
that
we
need
to
be
better
on
the
communication.
So
basically,
what
are
the
changes
and
improvements?
C
What
are
we
introducing
also
in
a
blog
post
format,
so
not
just
covering
them
bi-weekly
in
this
course,
but
also
being
super
structural
on
the
blog
post
area
and
we're
starting
that
starting
from
january?
So
we
already
have
a
decisions
related
on
that
one.
But
thank
you,
everybody
for
feedback
related
on
these
things,
and
that's
all
from
me
for
now
so
join
back
to
you,
patrick.
A
D
Thank
you,
patrick,
so
we
released
2.0.13.
We
did
that
on
monday,
so
that
is
out
in
the
world.
We
have
lots
and
lots
of
bug
fixes
as
usual,
with
some
documentation
updates.
We
also
added
msl
auth
for
local
dev
and
test
stuff.
So
that
means
that
instead
of
using
the
add-in
model
for
testing,
you
can
now
use
an
m
cell
authentication.
So
that
makes
testing
a
little
bit
more
simple.
We
also
have
again
some
more
taxonomy
updates
for
those
beta
endpoints
and
then
again
to
remind
everyone.
We
have
the
2.1.0
beta
release.
D
We've
been
working
hard
on
that.
We
are
now
including
node
15,
webpack
five
module
resolution
support
in
there.
So
for
all
the
esm,
module
people
and
node,
you
really
would
love
it
if
you
could
test
that
out,
because
we
are
targeting
that
release
for
january.
So
testing
now
will
help
make
sure
that
that's
a
great
release.
It
is
a
big
change,
so
any
testing
we
can
get
will
really
help
us
out.
A
A
so
release
the
new
beta
3.4
with
logging
and
using
base64
encoded
certificates,
auto
calculating
certificate
thumbprints
support
for
using
passwordless
pfx
certificates,
support
for
specifying
app
id
and
tenant
in
options.
Sped
things
up,
some
bug
fixes
and
more
so
great
tool
to
have
in
your
tool
belt
available
natively
in
the
azure
cloud,
shell,
you
can
always
install
the
latest
beta
with
npm
install
dash
g
at
p.
A
P,
slash,
cli,
dash
microsoft
365
at
next
certainly
encourage
you
to
check
out
the
cli
that
continues
to
grow
and
get
better
every
week
and
that's
a
big
place.
We're
seeing
a
lot
of
people
contribute,
which
is
fantastic,
love
to
see
that
love
to
see
the
participation
around
the
cli
and
see
that
continue
to
grow
and
get
better
and
with
that
we'll
go
to
the
reusable
spf
x
controls.
A
So
the
react
controls
230
is
out
with
the
dashboard
control
for
microsoft
teams,
toolbar
control
for
teams,
a
web
part
title
updated
to
fix
some
styling
issues
and
some
various
other
fixes.
Those
again
are
the
controls
designed
to
be
used
within
the
body
of
your
web
parts
or
application
customizers.
A
The
react
controls
one
two
one
which
are
the
ones
that
can
be
used
for
on-premises
have
some
updates
as
well
so
list
view,
drag
and
drop
a
taxonomy,
picker
error,
message,
improvement
and
some
rich
text
hyperlink
fixes
so
great
to
see
the
work
continue
on
that
as
well
for
folks,
developing
on-premises,
sharepoint
and
then
the
react
property
controls.
2-2-0
have
some
new
things
as
well:
new
teams,
picker
property
paint,
control
and
localization
fixes
want
to
thank
all
our
contributors
here
as
well.
A
A
If
you
haven't
checked
this
out,
it's
built
on
top
of
the
out
of
the
box,
microsoft
sharepoint
framework
generator,
so
you
get
a
quote-unquote
real
sharepoint
framework
project
with
just
a
bunch
of
enhanced
options
to
get
your
project
set
up
using
a
bunch
of
frameworks
that
aren't
available
in
the
out
of
the
box,
one
so
there's
a
microsoft
graph
toolkit
support
added,
which
is
fantastic
to
see
and
great
to
see.
The
graph
toolkit
continue
to
grow
and
get
better.
They
just
had
their
2.0
release.
A
So
another
thing
to
check
out
as
well
is
the
graph
toolkit
fixed
issues
with
angularjs
and
then
working
on
angular
support
getting
in
that
as
well.
Working
on
source
map
support,
angular,
11
updates,
some
improvements
for
vue
and
babylon.
Js
are
all
things
in
the
future,
so
do
check
out
as
well.
The
pnp
spfx
generator
to
give
you
some
great
ways
to
set
up
your
project
in
a
nice
standard
fashion,
using
options
not
available
in
the
out
of
the
box
stuff
and
for
the
modern
search.
I
believe.
E
A
F
Abdaraman
mujahid
has
updated
the
calendar
as
well
as
the
list
form
web
part
where
there
used
to
be
a
limitation
of
100
items
in
lookups,
so
he's
fixed
that
swami
nathan
has
updated
the
pmp
controls
sample,
and
then
we
have
a
new
web
part
from
rabia
williams.
That
shows
you
how
you
can
do
a
simple
implementation
of
target
audience
using
a
generic
control
and
we
have
a
new
feedback
web
part
from
perry
kencam.
F
A
Awesome,
thank
you,
hugo
and
love.
Seeing
these
samples
continue
to
grow
and
grow
and
grow
and
get
better
another
testament
to
all
the
great
work
by
all
of
you
out
there
in
the
community
and
now
optional
picture
time.
So,
if
you're
interested
in
turning
on
your
cameras
and
being
part
of
our
optional
picture
time,
please
do
that.
A
C
Let's
wait
one
more
second
to
get
the
full
house
there's
50
seats
on
the
on
the
video
feed
and
I
hopefully
will
yeah
now
it's
getting
better
better
and
I
will
hit
the
record
so
I
will
actually
do
a
video
recording
of
this
one,
because
then
we
can
get
a
key
for
animation,
that's
always
cool,
so
let's
actually
do
some
waving
and
I
will
share
the
gif
again
in
the
youtube
channel.
This
is
really
cool
to
see
all
of
the
people.
Okay,
awesome!
Excellent!
Thank
you.
Thank
you.
C
H
Yeah
thanks
so
much
patrick,
I'm
just
gonna
share
my
screen,
so
this
is
going
to
be
super
super
quick.
So
this
is
the
me
experience,
personal
tab
that
I
built,
which
is
now
in
the
teams
repo
in
for
pnp.
So
this
is
based
off
on
the
article
that
multi
released
a
couple
of
months
back
on
creating
a
me
experience,
building
a
personal
teams
app
and
there
was
absolutely
no
sample
to
back
this
article,
which
is,
which
was
something
that
I
know
a
few
folks
who
are
asking
in
our
chats
as
well.
H
So
what
I
did
was
I
went
ahead
and
developed
this
spfx
personal
app.
It
has
three
tabs
planning,
insights
and
settings.
Basically,
this
planning
and
insights
are
built
using
the
microsoft
graph
toolkit
you
can
see
here.
Planning
has
agenda,
it
has
my
tasks.
Sorry,
it
has
my
tasks.
It
has
my
meetings
and
my
documents.
My
recently
used
documents.
So
it's
it's
all
centric,
it's
related
to
what
I
want
to
do
or
what
I
am
interested
when
I'm
at
work.
H
So
that's
the
me
experience
and
insights
are
basically
around
all
the
files
of
the
documents
that
I'm
interested
in
trending
around
me
shared
with
me
again
using
the
get
component
in
microsoft,
graph,
toolkit
and
settings.
Basically
just
to
show
you
you
can
store
your
own
settings
using
graph
open
extensions.
You
can
probably
add
more
configurations.
H
Contributions
are
always
welcome
in
these
repositories.
So
if
you
want
to
add
more
of
settings,
then
you
could
go
ahead
and
open
up
pr
for
that.
So
this
is
what
I've
built
and
what
can
show
you
is
the
manifest
file.
So
we
have
for
each
of
those
tabs.
We
have
three
separate
web
parts
and
what
I've
done
is
I've
added
them
into
the
static
tabs
for
each
of
those
web
parts?
H
So
that's
basically
how
you
can
get
the
tabbed
effect
for
the
personal
app
and,
as
you
can
see
here,
every
single
component
here
is
built
using
the
graph
toolkit
which
is
which
made
it
made
it
really
simple.
So
we
have
the
agenda
one.
We
have
task
and
we
have
the
get
which
basically
gives
you
all
the.
H
So
this
is
one
of
my
favorite
component
in
graph
toolkit,
because
if
you
don't
have
a
particular
component
in
the
graph
toolkit
mind
you
it's
also
open
source,
you
could
go
ahead
and
add
new
components,
but
if
you
don't
find
one,
then
you
could
go
ahead
and
add
your
own
template,
which
is
files
one
here
you
can
see
and
I'm
passing
the
data
that
I
received
from
the
get
component
and
then
pushing
it
out
so
yeah.
That's
basically
what
I've
done
here
and
in
this,
so
what
I
have
done
is.
H
H
So
to
do
my
crud
operations
on
settings,
I
have
used
the
services
for
graph,
which
is
basically
here,
so
you
can
find
all
this
in
the
repository
a
big
shout
out
to
hoa,
because
this
this
this
sample
is,
has
staining
enabled,
which
is
basically
something
inspired
from
one
of
his
samples.
As
well
so
yeah,
that's
basically
it
go
ahead
and
check
out
my
blog
or
you
could
go
to
the
repository
and
have
a
look
at
the
source
code.
Thank
you.
So
much.
C
Well,
robia,
don't
don't
stop
sharing
that
was
super
fast
much
faster
than
I
certainly
needed.
So
let's
go
back
on
the
solution.
I
will
ask
some
questions
and,
let's
clarify,
why
are
we
doing
things
and
all
of
that
so,
first
of
all
on
the
craft
services,
you
did
a
graph
extension.
So
did
an
open
graph
extension.
Why
did
you
do
that?
What
what
is
what
is
actually
can
we
recap
on
why.
H
Good
question
so
personal
tabs
do
not
have
a
settings
or
a
configuration
panel
for
you
like
you,
would
see
in
a
teams
one.
So
if
you
have
a
teams
tab
you
basically
and
you're
using
spfx,
then
you
can
get
the
web
part
configurations
in
same
as
you
would
get
in
your
sharepoint
pages.
But
personal
tabs
do
not
have
that.
There
are
different
ways
you
could
implement
these
settings,
but
I
thought
this
was
easier
using
an
open
extension
because
it's
very
similar
to
what
you
have
the
user
profile
properties
in
sharepoint,
but
more
graph
eccentric.
C
And
that's
the
kind
of
one
one
kind
of
a
consideration:
you
mentioned
the
user
profile
properties
in
sharepoint,
which
is
kind
of
a
cool
thing.
We,
if
you
come
from
a
sharepoint
world,
you
know
about
it.
You
can
add
an
additional
property
against
their
stuff
there,
but
you
cannot
automate
that
that's
really
the
challenge.
Yeah.
H
C
H
C
And
the
concept
itself
is
absolutely
brilliant:
people
can
pull
it
down,
they
can
extend
that
they
can
read
back
and
set
them,
publish
that
to
the
store
by
the
way,
if
you're
interested
everything
is
mit
licensed
it's.
This
is
what
we
want
you
to
do,
but
the
fact
that
you
created
the
manifest
manually-
why
is
that?
Can
we
recap
that
decision.
H
Yeah
so
because
we're
adding
more
tabs
here
so,
for
example,
I
I'll
open
up
here
so
yeah,
so
this
one
is
our
manifest,
so
we
need
to
because
we
need
to
add
all
these
web
parts
in
to
the
static
tabs.
We
need
to
go
ahead
and
manually
do
it
at
the
at
the
moment.
This
is
the
only
way
we
could
do
it
and
yeah.
So
that's
exactly
why
we
have
chosen
this
path.
H
C
Then
enable
people
like
rabia
and
the
developers
to
include
the
complex
manifest
like
this
kind
of
a
complex
configuration
in
the
manifest
and
deploy
that
to
that
catalog
and
then
automatically
sync,
that
to
teams,
so
you
don't
have
to
manually
get
the
manifest
package
as
a
zip
file,
together
with
the
color
the
images
and
then
get
it
installed
to
the
teams,
which
has
to
be
done
right
now
with
the
solution.
So
yeah
not
a
super
option.
H
Yeah,
no,
that's
fine!
I
was
just
gonna
point
to
the
documentation
that
waldek
added
here,
so
it's
all
captured
here
all
the
things
that
you
need
to
keep
in
mind
when
you
are
considering
these
tabs
so
yeah.
I
would
suggest
everyone
in
this
call
to
go
and
have
a
look
at
this
very
comprehensive
article.
C
C
I
I
I
will
go
through
a
quick
introduction
about
the
v4
and
the
pit
motor
search
solution
in
general
and
jump
to
the
demo
for
the
new
features.
So
first
of
all
is
to
to
start
what
is
the
the
solution,
the
pnp
module
for
for
those
who
don't
know
already
it's
a
set
of
sharpness
online
web
parts.
It's
only
a
solution
available
for
support
online.
Only
it's
a
set
of
web
parts
allowing
to
to
create
like
highly
flexible
search
experiences
within
the
modeling
experience,
the
sharepoint
modern
experience.
I
So
it
includes
multiple
web
parts
like
the
search
results,
such
filters
verticals
and
the
search
box,
so
you
can
put
it
together
to
create
the
whole
search
center
for
extent.
For
instance,
the
the
main
goal
of
the
solution
is
to
enhance
the
capabilities
of
the
out-of-the-box
web
parts,
for
instance
the
iot
content
web
part,
which
is
quite
limited
right
now
in
the
out-of-the-box
web
part.
So
the
the
gold
is
free
to
offer
you
a
set
of
web
parts
to
customize
your
results.
I
I
I
want
to
just
thank
all
the
people
who
contributed
to
this
solution
since
the
since
the
beginning,
so
this
solution
was
first
released
in
2017,
so
the
it's
yeah
the
longer
time
the
current
version
is
version
3.16
and
today
I
will
show
you
the
new
version,
which
is
the
version
4
to
present
to
you
today,
so
about
the
version
4
just
to
get
started.
There
is
really
distinction
between
the
v3,
the
current
v3
version
and
the
v4,
since
they
are
not
really
compatible.
I
The
reason
is
the
v3
was
like,
let's
say,
hold
it's
an
old
code
base,
so
it
is
quite
complicated
to
to
maintain
and
to
to
add
new
features,
and
so
on.
So
we
decided
to
completely
review
the
architecture,
it's
very
complicated,
to
maintain
the
v3
right
now,
so
we
decided
to
completely
reorganize
the
code
with
architecture
and
also
we
had
to
integrate
the
new
microsoft
search
api.
I
So
we
needed
a
way
to
to
do
it
correctly
in
the
code
and
that's
why
we
we
took
the
decision
to
completely
start
from
scratch,
basically,
but
keeping
some
feature
from
v3.
Not
all
features
from
v3
are
in
the
v4.
Yet
there
is
a
lot
of
features
in
the
v4,
but
not
com.
It's
not
complete
compared
to
the
v3.
I
First
of
all,
if
you
want
to
download
the
latest
release,
so
it's
currently
in
preview
so
go
to
this
url
pnp
modern
search
within
the
the
microsoft
search
organization,
and
you
will
see
the
v4
preview.
So
it's
a
preview
version
you
can.
It
can
change
so
don't
use
it
for
now
in
your
production
environment.
So
just
for
testing
purpose
and
it
allows
us
to
gather
feedback
and
fix
each
issues
before
the
official
release.
There
is
a
documentation
also
available,
so
we'll
just
jump
into
the
documentation
to
to
give
you
an
overview.
I
So
documentation
has
been
completely
written,
so
it's
the
main
documentation
of
the
reports
targets
the
v4
currently,
but
thanks
to
michael,
we
have
now
a
v3
documentation
included
in
the
portal.
So
if
you
use
the
v3,
you
can
still
see
the
documentation
associated
so
just
go
to
the
v3
tab
here
and
we'll
you
will
get
the
the
the
v2
documentation
for
for
the
current
version.
I
So
let
me
go
back
to
my
slides
so,
like
I
said,
the
documentation
is
online,
so
go
check,
go,
take
a
look
on
this
and
your
feedback
and
issues
are
welcome.
If
you
find
any
issues,
please
let
us
know,
especially
on
the
v4,
we
are
trying
to
to
fix
them
a
lot
of
issues
before
the
the
official
release
so
feel
free
to
to
go
to
this
url
and
raise
your
your
issues
about
the
new
feature.
I
So
I
tried
to
summarize
all
the
features
we
we
added
to
the
v4
pair
web
parts,
so
the
first
one
is
the
search
for
the
web
part.
So,
basically,
like
I
said
we
refactor
the
old
code
base
to
be
more
modular
and
essentially
we
added
the
microsoft
search
api.
So
now
the
web
parts
in
the
main
web
part
you
have
the
shop
on
search
and
you
have
the
microsoft
search
api.
So
I
will
show
you
in
in
a
minute,
but
this
is
really
the
main
difference.
I
I
will
say
we
also
added
a
slot
feature
to
to
define
the
field
mapping
between
the
layouts
and
the
data
source.
I
would
show
you
also
this
in
in
a
minute
we
improved
some
layouts
and
added
some
options
and
we
support
now
the
microsoft
graph
toolkit
within
the
templates.
So
for
those
who
already
use
the
pnp
modern
phones,
we,
you
know
this
is
the
handlebars
templates
behind
the
scene.
I
So
now
in
the
html
markup,
you
can
use
the
microsoft
graph
toolkit
and
I
will
show
you
a
concrete
example
of
that
in
a
few
minutes
and
also
we
added
a
new
connection,
extensibility
options.
So
basically,
these
are
the
same
web
parts,
but
the
way
they
work
together,
it's
quite
different,
so
I
will
show
you
again
regarding
the
search
filter
web
part.
We
added
the
like
the
search
result.
We
added
the
ability
to
create
templates
for
filters.
So
you
now
you
have.
You
have
access
to
the
underlying
html
markup.
I
It's
an
underbar
template
just
like
the
search
results.
So
now
you
can
customize
this
web
part
as
well,
and
we
added
new
filters
and
templates
for
the
for
refiners.
Basically,
regarding
the
search
verticals,
pretty
much
the
same
thing
except
the
behavior
has
been
refactored,
so
it's
not
really
the
same
as
before,
because
we
had
to
support
the
new
microsoft
search
data
source.
So
I
will
show
you
also
and
the
search
backward
part.
We
added
the
multiple
suggestions
provider
to
the
extensibility
library.
I
I
I
So
to
use
the
v4
you
have
to
to
deploy
the
two
packages
and
also
these
packages
can
be
deployed
at
tenant
level
or
site
collection
level.
For
instance,
here
I
mean
an
isolated
site
collection
and
I
have
the
v4
and
v3
together
within
the
same
site
collection.
So
you
can
deploy
both
version
together
without
any
conflict
because
they
don't
share
the
same
ids,
the
web,
part,
ids
and
so
on.
These
are
not
the
same.
So
that's
why
I
said
that
these
are
not
compatible.
It
says
read.
I
This
is
really
two
completely
different
packages,
so
you
can
deploy
it
together
with
the
same
app
catalog.
So
when
you
deploy
this
package,
you
will
still
have
the
option
to
have
to
add
the
web
parts
on
your
page,
but
the
difference
is,
for
instance,
I
type
search
result.
As
you
can
see,
there
are
a
lot
of
search
result,
web
parts
actually
or
pmp
modern
central
parts.
So
you
have
the
new
one
with
the
pnp
prefix
here.
I
This
is
the
new
ones
and
the
old
ones
are
only
the
search
box,
such
features
and
so
on.
So
you
can
add
them
both
on
the
page.
I
recommend
you
to
just
use
one
version
on
the
page
for
just
reason,
but
you
can
still
use
the
v3
if
you
want,
so
I
will
start
with
the
first
one,
the
pnp
search
results,
which
is
the
the
main
component
of
the
of
the
set.
I
So
if
I
go
to
the
property
pane,
as
you
can
see,
the
first
choice
you
have
to
make
is
either
to
use
the
sharpcon
search
or
the
microsoft
search
api.
So
if
I
select
the
sharp
one
search,
this
is
pretty
much
the
same
options
we
had
in
the
v3
version,
except
a
couple
of
things.
Like
the
query
text,
connection
to
the
search
box
has
been
moved
to
another
property,
paying
configuration
page.
I
So
if
I
go
to
the
new
one,
I
won't
go
through
the
sharepoint
search
option,
because
this
is
a
pretty
unknown
stuff,
so
I
will
jump
to
the
microsoft
search
api,
so
this
is
for
now.
This
is
really
simple,
very
basic.
The
options
we
have.
Basically,
you
can
search
for
entity
types.
So
this
is
the
supported
entity
types.
I
suggest
you
to
to
read
the
documentation
about
microsoft.
I
Search
some
of
entities
are
not
compatible
together,
so
you
have
to
make
sure
you
have
the
correct
combination
between
the
entities,
for
instance
the
drive
items
external
item
and
so
on
and
for
specific
entity
types
like
external
items,
make
sure
you
authorize
the
correct
permission
with
your
tenant,
their
pe
permission
to
get
this
kind
of
entities
and
again,
if
you
have
any
any
question
about
it,
it's
really.
I
suggest
you
to
really
read
the
doc
on
microsoft
search
api.
It's
all
explained
what
you
can
do
with
entities
and
so
on.
I
So
the
options
are
pretty.
Like
I
said,
pretty
simple
to
selected
fields,
the
drive
items.
We
will
add
more
options
in
the
future,
but
we
want
to
stop
with
a
restraining
set
of
features
to
to
begin
and
yeah.
So
the
first
page
data
source,
like
I
said-
and
if
I
go
back
to
the
next
page,
we
will
see
the
the
layout.
I
I
So
let's
say
I
want
to
use
a
query
text.
I
can
use
a
static
value
or
a
dynamic
value,
for
I
will
use
a
static
value.
For
instance,
if
I
type
the
whitehead
character,
as
you
can
see
here
it
would,
it
will
write
the
he
will
put
the
query
here.
So
this
query
text
is
used
in
the
microsoft
search
and
sharpen
such
data
sources
like
mentioned
here.
I
So
it's
a
bit
different
of
the
from
the
v3
so
make
sure
you
are
you
use
the
the
correct
option
to
pass
your
your
query
text.
Another
feature
that
we
add
is
the
slot
feature.
As
you
can
see,
you
have
a
layout
slot
for
all
data
sources,
the
slots.
Basically,
I
will
just
use
another
layers
to
make
it
more
relevant.
I
The
layout
slots
are
basically
a
way
to
match
your
fields
in
built-in
layouts
the
data
source
fields
in
built-in
layouts.
So
let's
say
you
have
your
data
source
and
you
want
to
use
another
field
for
the
title
slot.
So
slots
are
in
the
built-in
layout,
and
so
this
is
placeholders
basically,
so
you
can
map
any
data
source
field
on
this
particular
placeholder.
For
instance,
in
the
title
I
can
choose
to
use
the
name.
I
So
this
is
the
response
of
my
search,
query
or
I
can
choose
to
use
whatever
else
and
as
you
can
see,
I
just
changed
the
value
dynamically
without
going
in
the
handlebar
templates.
So
it's
a
quick
way
to
to
make
like
reusable
templates
between
sharpen
search
and
microsoft
search
using
the
slots,
and
if
I
go
to
the
specific
end
of
that
template
here,
to
see
what's
going
on
here,
the
detail
is,
for
instance,
and
I
go
to
the
column
the
specific
column
here.
I
So
I
go
to
the
subwoofers
and
now
I
can
select
a
result
source,
so
the
default
one
is
people
for
instance,
so
I
will
just
look
up
for
all
the
people
in
my
organization
and
I
switch
to
the
people
layout
and
I
have
a
special
option
here
so
personal
calendar
over
enable
this
option,
as
you
can
see,
enable
enabling
this
option
will
see
the
actual
picture
and
a
card
detail
card
for
all
the
people.
Basically
behind
the
scene.
These
are
microsoft,
graph,
toolkit
integration.
So
to
show
you
the
integration.
I
If
I
go
to
the
template,
as
you
can
see
here,
this
is
a
microsoft
graph,
toolkit
integration,
so
it
means
you
can
use
this
kind
of
component
anywhere
within
your
handlebars
template.
This
is
a
concrete
example.
The
pre-built
example
for
the
people
layout,
but
basically
you
can
inject
any
context.
Any
data
from
the
handlebar
context
in
your
microsoft
graph
toolkit
components.
I
So
it's
a
cool
option
to
create
beautiful
templates.
If
you
want
a
custom
template
but
remember
when
you
use
this
kind
of
component,
you
have
to
authorize
of
permissions,
for
instance,
for
the
people
layout.
As
you
can
see
here,
you
have
to
authorize
this
attribute
permission
for
your
tenants
to
to
get
it
worked.
So
when
you
will
deploy
the
package,
you
will
be
asked
to
authorize
this
this
ipv
permission.
These
are
not
mandatory,
of
course,
but
if
you
don't
to
write
them,
this
feature
won't
work,
obviously,
okay.
I
So
this
is
for
the
microsoft
graph
toolkit
integration
next
for
the
extensive
video
accessibility
option.
So,
like
I
said
all
the
connections
are
made
through
the
last
to
the
specif
in
a
specific
page
in
the
property
pane,
so
I
use,
for
instance,
an
input,
quiz
text
and
static
value.
But
if
I
want
to
use
a
search
box,
I
will
just
add
a
search
box
on
my
page
here.
I
It's
a
one-way
connection,
so
I
go
to
the
search
result,
the
connection
page
and
now
I
can
map
the
dynamic
value
and
from
here
I
can
either
choose
the
search
box
or
page
environment,
for
instance,
a
query,
string,
parameter
and
so
on
and
inject
it
to
my
search
filter.
So
this
is
pretty
much
the
same
as
v3.
You
can
still
use
the
default
value,
for
instance
during
the
page
load
or
grab
the
value
from
a
search
box.
I
I
So
this
is
for
the
search
box.
Pretty
simple.
Now
I
will
connect
another
web
part
which
is
the
vertical
web
part.
So
we
started
the
vertical
report
and
we
let
the
filter
away,
possibly
for
the
end,
the
vertical
bypass
has
changed
for
the
v4,
so
I
will
add
another
search
results
here
and,
for
instance,
I
will
choose
another
data
source,
for
instance,
microsoft
search
and
I
will
map
to
the
search
box
here
to
dynamic
value,
search
box,
search,
query,
yeah
great
and
then
I
will
add
a
vertical
web
part.
I
So,
basically,
the
vertical
web
parts
controls
visibility
of
connected
search
results
web
parts,
so
I
can
still
configure
my
tabs
here.
So,
for
instance,
here
I
created
a
people
directory
and
here
showcase
of
microsoft
search.
You
can
still
use
the
fish
react
fabric
or
so
effluent,
icon
name.
If
I
want,
but
as
you
can
see,
there
is
no
more
query
template
or
are
such
options
within
the
verticals.
It's
only
tabs
and
a
link
if
you
want
to
redirect
to
a
specific
link.
I
So
I
go
there
and
now
from
my
search
web
parts.
I
can
use
this
tabs
to
connect
to
control
like
the
visibility,
so,
for
instance,
the
people
who
are
part
here
will
only
be
displayed
if
the
people
tab
is
selected
and
this
particular
web
part.
The
such
the
microsoft
search
report
will
be
displayed
only
if
the
microsoft
search
tab
is
controlled
and,
as
you
can
see
in
edit
mode,
you
will
prompt.
You
will
be.
I
A
message
will
be
a
display
saying
the
current
tab
is
not
the
one
you
select
you
selected
in
the
web
part,
so
in
display
mode
this
won't
be
displayed.
So
if
I
save
my
page
you
can.
You
can
now
build
like
search
experiences
here,
just
by
clicking
tabs
and
displaying
the
correct,
pnp
search
result
you
want,
according
to
the
tab,
so
you
this
way
you
can
really
build
complex
queries
and
layouts
for
specific
tab,
and
this
was
a
limitation
for
the
v3,
because
the
v3
only
had
the
option
to
configure
the
query
template.
I
I
Now
I
will
jump
to
the
other
way
parts.
The
filter
wipers,
the
refinery
parts.
So
I
will
head
it
here.
Pnp
filters.
This
one
changes
a
lot
actually,
because
now
I
can
connect
filters
from
multiple
web
parts.
So
it's
a
one-to-many
configuration.
So,
as
you
can
see,
I
have
the
option
to
connect
the
such
the
two
search
results
and,
as
you
can
see,
you
have
the
id
here
of
the
web
part.
I
So
if
you
don't
know
which
is
the
one
the
correct
one,
you
can
still
use
the
id
and
if
you
go
here
on
the
lattice
page,
you
have
the
instance
id.
If
you
want
to
make
sure
this
is
the
right
web
part
to
connect
okay,
so
I
go
there.
I
connect
my
two
web
parts
and
I
will
edit
my
filters.
So,
basically,
you
can
use
the
fields
from
your
data
sources,
so
this
these
are
only
the
fields
available
in
the
current
response:
okay,
for
instance,
if
you
created
a
custom,
managed
property
or
a
referral
stream.
I
This
won't
show
up
here
and
you
have
to
type
the
field
and
press
enter
to
use
it
in
the
filters
okay.
So
this
is
not
the
complete
list
you
see
here,
it's
just
an
help
for
you
to
select
the
right
field.
So
let's
say
I
will
use
the
file
type
and
I
I
will
select
a
template.
So,
as
you
can
see,
these
are
pretty
much
the
same
check,
box,
combo
box
and
so
on.
I
will
use
the
check
box
for
name
for
the
instance
and
a
couple
of
other
options.
I
External
defaults
and
another
option
is
the
multi-value
control
in
the
v3
v3.
You
add
one
template
for
multi
or
single
filter
behavior.
Now
you
have
only
one
template,
but
it's
an
option
in
the
template
to
select
if
it's
multi
values
or
not.
So
if
I
use
the
single
value
here,
so
I
connected
the
two-way
connection.
So
I
connect
from
to
my
search
result
and
from
the
search
result.
I
need.
I
still
need
to
connect
to
the
filter
web
parts
to
send
actually
the
refiner
to
the
filter
web
part.
I
Okay,
yeah
the
people
don't
have
filed
up
actually
yeah
my
mistake,
yeah.
I
will
select
another
data
source
actually
like
sharepoint
people,
reason
sharpened
without
much
better.
Here
we
go
sorry
for
the
dumb,
the
dumb
configuration
this
couldn't
work
anyway.
Okay,
so
we'll
go
to
a
more
friendly
layout
yeah.
So,
as
you
can
see,
you
can
filter
a
web
part
here
using
the
the
template
and
the
selected
field.
You
want
and
connect
to
multiple
web
parts.
So
just
for
my
other
configuration
quickly
come
on.
I
I
So
if
I
choose,
for
instance,
all
condition
now,
you
will
add
the
option
here
to
select
multiple
and
apply
multiple
filters
to
the
your
web
parts.
So
it's
a
new
way
to
handle
fits
filters
compared
to
the
vitra
e3
configuration
another
things
I
want
to
cover
in
this.
In
this
session
I
have
only
five
minutes
left,
so
I
will
go
quick.
Is
the
extensibility
feature
so
in
the
latest?
I
Last
page,
sorry
of
the
configuration,
the
property
pane,
you
have
the
extensibility
configuration
and
from
here,
if
I
click
to
configure,
you
will
see
your
extensibility
library
and
the
manifest
id.
So
the
manifest
id
com
comes
from
your
library,
specifics
project
that
you
can
build
to
enhance
capabilities
of
the
built-in
web
parts.
So
in
the
modern
search
organization
you
have
now
a
pnp
modern,
search,
extensibility
sample.
I
Okay,
if
you
go
to
the
developer
branch
still
work
in
progress,
but
you
will
have
spfix
projects
here.
It's
a
library,
component
project-
and
from
here
you
can
add
your
own
extension.
Extensions
can
be
custom,
web
components,
custom
suggestions,
providers
for
the
search
box,
custom,
handlebars
helpers
and
we
are
trying
to
implement
the
layouts
configuration
the
extension
layout.
So
you
can
use
it
as
a
replacement
of
the
custom
renderers
you
add
in
v3.
So
basically
it
will
allow
you
to
add
your
own
tile
here
within
the
web
part.
I
It's
a
quick
demo.
This
sample
provide
you
some
built-in
methods
that
you
can
just
use
to
register
your
old
components.
If
you
want
to
to
know
how
to
to
do
this
in
the
documentation,
you
have
an
extensibility
tab
here
with
a
step-by-step
tutorial
to
create
all
kinds
of
extensions,
so
web
components,
suggestion
provider
and
so
on.
So
the
goal
is
really
for
you
to
to
create,
like
extension,
in
a
separate
project
and
use
it
in
the
main
web
part.
I
So
this
is
a
cool
way
to
enhance
the
the
the
co-work
part
with
your
customization
and
according
to
your
to
your
requirements,
so
you
can
use
it
for
your
own
project
and
you'll
be
fine
as
well.
I
think
cat
cover
pretty
much
I'm
running
out
of
time,
so
a
quick
recap
use
the
v4
preview
version
from
github
use
it
in
your
tournament
use
the
issue
tab.
I
If
you
have
some
feedback
and
issues
with
the
v4
and
let
us
know
what
you
think
of
the
of
this
version-
and
probably
this
will
go
out
probably
next
year,
early
next
year
january,
probably
we'll
still
have
some
issue
to
fix,
but
it's
pretty
much
stable
now,
but
we
have
some
issue
to
fix.
So
let
us
know
what
you
think
of
this
of
this
solution.
A
All
right,
thank
you
very
much,
fantastic
demo.
There
really
great
to
see
the
progress
on
the
search
web
parts
coming
back
together.
I'm
excited
to
get
that
out
there
for
folks,
a
lot
of
work
has
gone
into
that
a
lot
of
great
innovation
has
gone
into
that
so
great
great
great.
To
see
that,
finally,
getting
out
there
encourage
everyone
to
try
that
check
that
out.
Let
us
know
what
kind
of
feedback
you
have
and
with
that
I
will
just
say
thank
you
again
for
an
amazing
year
in
community
and
patterns
and
practices
work.
A
It's
been
wonderful
working
with
all
of
you
out
there
and
amazing
to
see
all
the
great
work
everybody's
doing
the
great
samples,
the
great
solutions
and
just
all
the
fantastic
community
involvement
from
everybody.
So
thank
you.
Thank
you.
Thank
you.
I
cannot
say
thank
you
enough,
so
I
will
not
try
because
we'll
just
go
out
the
rest
of
the
recordings
saying.
Thank
you
so
we'll
have
this
recording
available
about
24
hours.
Follow
us
on
twitter.
Remember!
Our
next
calls
are
in
the
new
year.
A
Our
next
spf
x
call
will
be
january
14th
and
our
next
general
dev
call
will
be
january
7th.
So
the
next
two
thursday
calls
are
cancelled
january
monthly.
Community
call
for
sharepoint
will
be
january.
12Th
look
forward
to
seeing
all
of
you
in
the
new
year.
Here's
a
list
of
all
our
other
community
calls
that
will
continue
through
into
the
new
year
as
well,
and
with
that
I
will
just
again
say
thank
you
to
all
of
you
have
a
great
holiday
season.