►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 6th of June. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI, Reusable SPFx controls and PnP SPFx Yeoman extension.
Detailed covered content from SharePoint Dev Blog at http://aka.ms/spdev-blog.
- Demo – Hugo Bernier – Move from no-framework to React based implementation (17:57)
- Demo – Bob German (Microsoft) – SPFx Teams tab accessing Microsoft Graph for the business scenarios (31:35)
- Demo – Luis Mañez (ClearPeople) – SPFx Teams tab using custom schema extensions with MS Graph (41:44)
You can download an invite to this bi-weekly call from https://aka.ms/spdev-spfx-call.
You can find more details around the open-source and community work from http://aka.ms/sppnp
A
A
Just
as
soon
as
we
can.
We
are
waiting
on
a
couple
key
features
which
we
are
hoping
will
be
in
place
around
the
end
of
the
summer
and
we'll
talk
about
our
summer
schedule
here
in
a
little
bit,
but
we're
hoping
that's
gonna
coincide
nicely
with
moving
to
teams.
A
lot
of
folks
often
ask
how
to
get
involved
more
in
the
patterns
and
practices
program,
and
specifically
sometimes
these
calls
so
a
great
way
to
get
involved
in
these
calls
is
to
do
a
demo.
I
know
all
of
you
out
there.
A
The
community
are
working
on
really
neat
and
really
cool,
exciting
solutions
for
your
companies
and
your
customers
and
we'd
love
to
see
those
demoed
on
here
where
possible,
so
that
could
be
a
webparts
application
customizers
something
around
provisioning,
really
anything
you
create
around
SPF,
X
or
client-side
development
and
then
as
well.
Anything
involving
any
of
the
sort
of
at
P
and
P
family
of
things
so
p.m.
PJs,
the
CLI,
your
user
controls
or
the
yeoman
generator.
So
any
or
all
of
those
combined
with
an
SPF
X
solution
makes
really
great
demos.
A
So
really
I
would
encourage
all
of
you
to
reach
out
get
on
the
schedule.
We
can't
guarantee
necessarily
you'll
be
on
the
next
call,
the
or
the
immediately
next
call,
but
we
will
get
you
on
just
as
soon
as
we
can,
depending
on
how
the
schedule
looks
for
upcoming
calls.
So
if
you'd
like
to
do
a
demo,
please
I,
encourage
you.
Reach
out
to
myself.
Reach
out
to
visa
will
get
you
scheduled
up
and
excited
to
see
those
demos
from
everybody
out
there
in
the
community
as
well
II.
A
A
You
know
that
other
folks
might
have,
because
it
really
sometimes
helps
people
get
answers
faster
than
maybe
waiting
for
one
of
us
on
the
core
team
to
get
around
to
having
some
time
to
answer
it.
So
if
you
have
had
a
chance,
you
want
to
help
out
those
are
great
ways
to
get
involved
as
well
contributing
on
github
and
then
finally,
you
could
always
provide
feedback
around
any
of
the
things
we
do.
So
how
are
our
calls?
How
are
is
the
documentation?
A
We
can
always
have
better
documentation,
but
are
there
specific
areas
where
we're
lacking
and
how
else
can
we
help
where
what
would
be
beneficial
to
all
of
you
out
there
in
the
community?
Is
it
more
getting
started?
Videos
a
topic,
we'll
talk
about
again
a
little
bit
later
in
this
call,
and
then
you
know
other
areas
and
of
course
positive
feedback
is
okay
too.
We
do
not
mind
hearing
some
positive
feedback
from
folks
one
intervention
going
into
the
summer.
A
We
did
this
last
year,
I
believe
and
I
think
maybe
the
year
before,
but
this
year
again
we're
gonna
have
a
summer
break
for
July.
This
gives
all
of
us
on
the
team
a
chance
to
have
a
break.
A
lot
of
us
are
on
vacations
and
gives
all
of
you
a
chance
to
have
a
break
from
the
calls
as
well,
because
I
know
a
lot
of
folks
out
there.
Listening
are
also
have
vacations
and
family
time
schedules,
and
so
we're
just
gonna.
Take
a
break
for
July.
A
Github
activity
will
continue
as
normal,
so
we'll
continue
with
releases.
We'll
continue
trying
to
process
issues
we'll
continue
working
on
the
various
projects,
but
we
will
not
be
hosting
any
of
the
calls.
So
that
goes
for
the
monthly
community
calls
these
special
interest
group
calls
and
as
well.
The
weekly
video
series
that
visa
and
Waldeck
put
out
will
also
go
on
hiatus
for
July,
so
just
a
heads
up
we'll
come
back
as
normal
in
August
with
a
whole
bunch
of
new
material
and
as
well.
A
Some
of
you
will
be
looking
at
your
invites
for
this
call
and
others
and
those
all
are
gonna
end
at
the
end
of
June.
We'll
have
new
invites
and
everything
ready
to
go
for
the
1st
of
August,
so
stay
tuned,
we'll
get
that
announced
through
all
the
normal
channels,
but
stay
tuned
for
that
and
we'll
get
that
pushed
out
and
we're
really
hoping
at
that
point.
Those
invites
will
be
for
teams
so
keeping
our
fingers
crossed
there,
and,
with
that
I'll
hand
things
over
to
visa.
B
Yeah
no
points
no
point
trying
to
take
over
things:
sis,
let's
go
to
a
following,
slides,
just
a
recap
on
the
assets,
because
so
where's
new
people
on
their
school.
So
she
have
on
their
documents
a
game
as
books,
videos.
We
have
no
more
than
10,000
subscribers
into
video
channel
and
in
a
relatively
soon
as
well,
and
then
the
dev
issues.
Please
keep
reporting
any
divisions
using
the
SP
dev
issues
list
respective
doc,
socialists,
but
if
you
chemists
their
issues,
you'll
find
they're,
actually
updating
the
slide.
B
So
I
do
apologize,
but
it
is
looking
still
exactly
the
same:
every
single
Monday
last
Monday.
So
to
this
week's
Monday,
we
did
a
overall
record
again
on
SPF
X
usage.
I
do
not
know
why,
but
Monday
is
by
far
the
number
one
usage
day
of
SPF
X
in
a
week,
for
whatever
reasons,
but
then
I
say
Wednesday
is
pretty
much
the
same.
Thursday
Friday
is
go
slightly
done
and
then
you
can
say
the
weekends
impacted
in
here,
but
it
is
500
number
one
extensibility
model
in
office
365
and
they
use
it
is
growing
enormously.
A
B
So
you
can
actually
start
doing
operations
and
admin
operations
using
Microsoft
graph
in
future,
which
is
a
great
thing
as
well,
but
in
church,
if
we're
gonna,
start
the
monthly
release
cycle
in
June
and
we're
still
kind
of
a
wandering
on
that
one.
The
final
decisions
that
will
happen
today,
the
team's
integration
improvements,
availability
of
library,
components
coming
in
1.9
office
and
ends
with
SharePoint
framework
loofah
little
code,
the
preview
quite
soon
it
might
be
that
it's
kind
of
happen,
unfortunately,
after
summer,
not
before
summer.
B
So
I
can't
actually
promise
that
right
now
season
government
standard
is
a
number
one
item
in
the
users
list
and
we
are
actively
working
on
that.
Hopefully
we'll
get
the
build
systems
to
work.
Probably
for
that
one
but
I
think
that's
a
quick
recap
on
the
roadmaps
and
then
let's
go
to
one
more
slide,
my
aside
quickly,
which
is
basically,
we
heard
a
lot
of
feedback
in
built
shipment
conference
and
European
collaboration
and
actually
other
sources
as
well,
that
it
would
be
great
if
we
would
have
more
getting
started
material.
B
So
quite
often
when
you,
if
you
are
a
new
person
and
a
developer
and
arrived
on
this
course,
and
we
might
actually
talk
about
things
which
are
obvious
for
us,
but
not
obvious
for
new
people
and
that's
basically
causing
them
a
challenge
for
people
to
learn
how
to
get
started
and
how
to
get
how
to
how
to
catch
up.
The
other
peoples
have
been
doing
SPSS
for
a
long
time
or
modern
SharePoint
for
a
long
time.
So
what
we're
doing
now
is
up
to
twenty
thirty
forty
getting
started
videos.
B
We
will
basically
start
pushing
this
gradually
out.
I.
Think
from
July,
so
one
five
videos
in
a
week
on
average
timeframe,
and
these
are
basically
then
targeted
to
be
really
basic,
a
getting
started
level.
So,
if
you're
looking
into
how
what
they
see
some,
how
do
I
do?
How
do
I
start
using
system
NuGet
packages?
We
will
actually
have
a
video
on
that
one.
How
do
I
start
using
sign
designs?
B
These
are
the
steps
how
to
do
that
and
really
concentrating
on
the
introduction
level
and
knowledge
so
that
the
people
who
are
not
aware
can
easily
catch
up
on
things,
so
that
should
be
highly
beneficial.
Also,
what's
just
specifically
note
that
one
bullet
point
there
we're
seeing
a
massive
uptake
on
on-premises,
extensibility
and
on-premises
development,
interest
related
on
SPF
X
and
in
gerontology
about
2019
development
platform.
A
Alright,
so
quick
updates,
then
on
the
p.m.
PJs
client-side
libraries,
we
did
release
one
three
three
on
June
3rd.
That's
a
coincidence
didn't
mean
to
have
all
those
threes
in
a
row
but
really
beat
addition
to
support
client
certificate
off
from
case
awesome
and
toe,
unfortunately,
didn't
have
a
full
name
on
github,
so
I'm
not
sure
entirely
who
to
credit.
But
that's
the
github
handles
a
really
neat
addition.
There,
the
support
certificate
off
that's
from
the
server
side,
node.js
library
and
then
as
well
andrew
fixed
in
the
polyfill
package.
A
We
we
didn't
have
object
on
sign
in
there
and
then
a
couple
other
small
additions
there
so
check
out
that
release
nothing
groundbreaking,
but
certainly
helpful.
If
you
need
the
support
certificate,
authentication
in
nodejs
I
did
one
to
remind
folks.
We
do
have
some
great
graph
support
in
the
library
check
out
the
P
and
P
slash
graph
library
easily
integrates
with
SPF
X
to
handle
all
the
authentication.
It
builds
on
the
great
work
done
by
the
SPF
X
team,
for
forgetting
tokens,
has
the
current
user
and
really
I
know.
A
We
talked
on
this
call
it's
about
SharePoint
for
any,
where
we
talk
a
lot
about
SharePoint,
but
we
do
have
great
graph
support
in
the
library
as
well
so
check
that
out.
Simon
has
done
a
lot
of
the
work
to
build
that
out,
so
really
excited
to
see
that
grow
so
definitely
check
that
out.
I
encourage
you
to
use
that
to
help
ease
your
graph
experience
and
then
as
well
wanted
to
mention
version.
A
So
if
you
want
to
help
out,
there's
check
out
the
readme
under
the
dev
v2
branch,
that's
got
some
instructions
there
on
how
to
get
started,
and
then
one
of
those
three
will
help
reach
out
and
help
get
you
started
and
then,
if
you're
interested,
but
but
maybe
I'm,
sure,
on
exactly
how
to
get
started
or
what
to
do
definitely
check
out
the
call
next
Friday
at
10:00
Eastern
couple
links
there
to
the
current
one
dex
documentation.
Is
it
PNP,
github,
Daioh,
slash,
P
and
PJs?
A
You
can
follow
the
PM
pjs
hashtag
on
twitter
and
of
course
you
can
follow
me
at
mediocre.
Bowler
on
Twitter
for
updates
around
P
and
PJs
I
do
want
to
mention
the
main
numbers
continue
to
climb
really
impressive,
and
this
is
again
a
huge
thank
you
to
all
of
you
out
there
in
the
community
that
are
using
this
in
your
projects.
Using
this,
your
companies
and
your
customers,
so
we're
over
3.2
billion
requests,
B
billion
with
a
B
for
the
month
of
May
and
we're
into
nine
point,
seven
thousand
so
9700
tenants.
A
So
almost
ten
thousand
tenants
are
now
using
P
and
PJs,
and
that's
thanks
to
all
of
you
using
it
out
there
in
your
projects
and
I
really
just
want
to
say.
Thank
you.
It's
been
a
really
great
journey.
Seeing
this
growth
and
this
growth
again
is
what
is
really
driving
our
commitment
to
get
the
the
full
documentation
refresh
for
version
two
to
really
try
and
better
support.
I
think
we
do
a
great
job
supporting
folks,
but
do
a
better
job
of
supporting
if
buddy
out
there
in
the
community
using
the
library.
A
So
just
wanted
to
say.
Thank
you.
Thank
you.
Thank
you
to
everybody
out
there
for
this
continued
growth
of
PJs
and
then
office,
365
CLI
updates
a
new
beta
release,
one
to
two
with
commands
for
updating
user
roles
and
groups
and
teams,
improved
SPF,
X
project
upgrade
support
listing
office,
uses
five
groups,
applying
standard,
SharePoint
themes
and
the
support
for
specifying
owners
when
creating
sites.
A
So
some
great
additions
to
that
beta
check
that
out,
if
you're,
using
the
CLI
and
then
in
progress
first
preview
of
v2
is
simplified,
login
experience
and
you
can
try
that
by
installing
at
PNP
slash
office,
365
CLI
at
TW
o,
you
can
always
install
the
latest
beta
from
NPM.
That's
going
to
be
the
the
one
1x
branch
beta
is
gonna,
be
the
at
PNP
at
next
command.
A
There
you
see
and
then
for
more
information,
a
kms
o
35
CLI
hashtag
on
twitter,
get
ur
channel
and
as
well
the
docs
link
down
there
at
the
bottom
right
corner.
So
if
you
haven't
tried
out,
the
CLI
definitely
check
that
out
great
cross-platform
support
for
SharePoint
framework
development
and
SharePoint
Online
administrative
tasks,
kind
of
all
up
no
updates
this
week
for
the
reusable
controls,
but
didn't
want
to
mention,
of
course,
a
great
way
to
simplify
your
SharePoint
framework
development
experience
by
building
on
these
controls.
A
A
So
a
great
way
to
jumpstart
your
development,
more
information
to
links
down
there.
The
first
one
goes
to
the
property
controls.
The
second
one
goes
to
the
content
controls
and
these
are
all
for
reacts.
So
these
are
react
based
controls.
So,
if
you're
doing
react
based
developments,
this
is
a
great
way
to
jump
in
and
have
a
lot
of
awesome.
Community
functionality.
A
So
this
has
been
another
great
community
effort,
lots
of
contributors
on
this
and
it's
really
grown-
to
provide
a
very
rich
set
of
options
in
a
very
easy
way
to
import
a
lot
of
the
other
PNP
resources
into
your
project,
whether
that's
the
CLI,
the
controls
or
p.m.
PJs.
Just
provides
a
great
way
to
do
that
and
as
well
provides
a
great
way
to
use
other
frameworks
that
aren't
supported
by
the
out-of-the-box
generator.
But
at
the
end
of
the
process
you
get
an
out-of-the-box
SharePoint
framework
project.
A
It
has
all
the
same
standard
Microsoft
dependencies
under
the
hood,
but
it
just
has
some
additional
options
during
setup.
So
really
a
great
project
here
definitely
check
that
out.
It's
a
fun
project
and
it's
a
it's
a
cool
project.
If
you
want
another
way,
if
you're
into
yeoman
generator
development
and
want
to
help
out,
this
is
a
great
place
to
get
involved,
you
can
always
install
the
latest
version
from
NPM
and
p.m.
installed
G
at
peace.
A
Effects
and
a
kms
/
PNP
generator
takes
you
to
the
docks
for
more
information,
hashtag
PNP,
SP
FX
on
Twitter
and
we've
gone
really
fast,
because
now
we've
got
three
great
for
you
and
the
first
one
is
going
to
be
Hugo
and
Eric.
So
I
think
Hugo
is
the
one
presenting
this.
So
if
you
want
to
take
over
the
presentation,
okay,.
D
All
right
well
well,
this
is
loading
for
those
of
you
who
are
not
familiar
with
what
this
demo
is
about.
Eric
and
I
have
got
together.
Eric
had
a
good
question
and
one
of
the
previous
calls,
which
was
hey
I've
got
a
you
know.
I
have
a
JavaScript
web
part
and
I
would
love
to
see
detailed
instructions
on
how
to
convert
a
JavaScript
web
part
into
a
react
web
part.
So
that's
what
we
did
and
it
would
be.
You
know
if
you've
ever
seen:
Monty
Python
skit,
where
the
scientists
are
building
the
world's
funniest
joke.
D
D
D
You
know
the
the
article
and
the
code
are
actually
found
in
the
SP
dev
effects
web
part
samples,
but
there's
a
blog
post,
that's
arguably
too
long,
but
the
blog
post
actually
walks
you
through
every
single
step
of
creating
the
SPF
X
web
part
copying
the
code
and
making
some
conversions.
Luckily,
I'll
save
you
the
reading
I
will
actually
do
that
right
now
in
front
of
you.
So
why
would
I
take
a
web
part
and
convert
it
to
react
and
why
wouldn't
I
use?
D
You
know
angular
or
knockout
and
honestly
react
is
not
necessarily
any
better
than
any
of
the
other
frameworks.
But
the
one
thing
that
we
are
getting
with
react.
That's
would
be
a
bit
more
harder
work
if
I
was
using.
No
framework
is
that
you
are
getting
a
separation
of
duties,
you're
able
to
separate
the
components,
the
presentation
component,
the
services
that
retrieve
the
data
you're
able
to
do
that
and-
and
you
know
it
makes
it
obviously
easier
to
test
the
other
advantage
that
you're
getting
is
instead
of
rendering
the
entire
web
part
every
time.
D
Any
changes
happen
you're
able
to
actually
render
smaller
sections
of
the
web
part
just
by
the
way.
These
frameworks
work,
but
probably
the
most
important
reason
why
you
would
use
react
is
with
react.
You
have
the
fabric,
UI
components,
you
have
the
pnp,
reusable
components
which
are
readily
available
in
a
react
and
sadly
knock
out
an
angular
don't
get
as
much
love
when
it
comes
to
the
fabric,
UI
components.
D
So
the
only
difference
between
the
web
part
that
Eric
built
versus
my
web
part
is
I
used
the
yeoman
generator
and
at
the
end
here,
when
it
says
which
framework
do
you
want
to
use,
I
chose
react
when
Eric
chose
no
framework,
so
this
is
kind
of
what
the
JavaScript
new
version
of
the
web
part
right
looks
like
and
by
the
way,
you'll
see
at
the
bottom
of
very
slides
I'm,
showing
whether
it's
the
JavaScript
or
the
react
component.
So
this
is
the
JavaScript
version.
D
This
is
the
version,
the
react
version
of
webpart
and
the
components
are
broken
down
like
this,
but
if
you
compare
them
side-by-side
and
hopefully
I'm
not
going
so
fast
that
the
the
Skype
is
not
able
to
keep
up
here,
you'll
see
there's
a
few
there's
a
few
things
that
are
different.
But
you
know
there's
also
a
lot
of
commonalities
between
the
JavaScript
version,
which
is
on
the
left
and
the
react
version
which
is
on
the
right.
First
of
all,
it
generates
a
webpart
component.
D
It
also
generates
the
JSON
of
the
manifest
for
both
web
parts
and
even
renders
Canada
localized
strings
for
both
components
where
it's
a
little
bit
different
is
that
in
the
JavaScript
web
part,
all
the
code
to
render
the
body
of
the
web
part
is
inside
the
this
webpart
object
here.
But
in
the
react
version
it
actually
creates
a
component
which
has
kind
of
the
the
tsx
file,
which
is
responsible
for
rendering
the
body
of
the
web
part
itself.
D
So
if
you
look
at
the
JavaScript
version
of
the
render
code,
you'll
see
here
that
it's
actually,
it's
actually
rendering
the
HTML
inside
inside
the
web
part-
and
this
is
the
HTML
that
we
want
to
show
in
parallel.
If
I
show
you
the
react
version
of
this,
the
render
code
inside
the
web
part
itself
is
actually
very
simple,
because
all
it's
doing
is
it's
saying,
create
call
that
my
component,
that
we
saw
earlier
and
pass
it
the
information
that
we
need,
which
is
the
username
and
the
HTTP
client.
D
So
we
can
make
requests
and
Patrick
and
Mesa
if
I'm
going
too
fast.
Please
let
me
know
I
know,
there's
a
lot
of
stuff
to
get
to
cover
today.
So
this
is
the
react
version
of
the
same
rendering
code,
and
you
know
what
you'll
notice
is
inside
the
component
itself.
I
have
the
same
code
that
renders
the
the
HTML,
if
I,
put
the
two
side-by-side.
This
is
the
JavaScript
version
on
the
left
and
the
react
on
the
right,
you'll
notice.
A
few
things.
First
of
all
react
is
not
happy
with
CSS
the
CSS
word
class.
D
It
wants
class
name
in
comparison
on
the
JavaScript
side,
it's
using
the
word
class
here.
So
when
we
want
to
pass
the
CSS
class
name,
we
have
to
use
class
name.
The
other
thing
that
you'll
notice
is
I'm
actually
populating
the
data
by
just
passing
a
state
object
and
just
putting
the
values
in
the
state
objects
directly
in
HTML.
In
parallel
the
the
JavaScript
version.
D
Show
you
the
state
how
I
use
the
state
a
bit
later,
but
you'll
notice
here
that
I
actually
have
I'm
saying,
if
is
loading,
show
the
loading
you
know
render
some
loading
placeholder
and
if
I'm,
not
loading,
the
and
I
have
a
user
profile
then
show
the
user
profile.
The
values
is
loading,
and
is
user
profile
are
coming
from
the
state
variables
that
I've
created
in
react,
and
this
is
something
that
the
react
does
actually
really
well
for
us.
D
So
the
other
thing
that
I
want
to
show
here
is
that
at
the
bottom
of
Eric's
render
code,
we
have
get
github
data.
However,
in
the
react
code,
I'm
not
calling
yet
github
data
in
the
render
method,
I'm
actually
calling
it
in
two
places.
One
is
the
first
time
the
component
is
mounted
I
call
get
github
user
data
and
if
the
properties
of
the
web
part
are
changed
or
so
the
username
property
is
changed,
I
also
recall
get
github
data.
D
Everything
else
is
actually
handled
a
bit
later
by
the
get
github
data
method.
If
you
look
at
the
yet
github
method
in
Eric's,
JavaScript
code
he's
basically
doing
what
I
was
talking
about
earlier.
He
finds
every
single
element
by
ID
and
then
he,
somewhere
later
here,
he
actually
populates
that
code
with
the
values
that
you
retrieved
from
the
JSON
in
comparison
and
the
react
version
all
I'm
doing
here
is
I'm
actually
calling
my
service
that
I've
created
to
get
the
user
profile
now
I
didn't
have
to
do
that.
D
But
one
of
the
values
again
as
I
said
of
react,
is
that
you
can
componentize
your
elements
and
so
by
creating
a
separate
service,
object
that
I.
That
has
all
the
logic
to
call
github
and
retrieve
the
data.
It
makes
it
a
lot
easier
and,
as
you'll
see
later,
if
I
want
to
change
the
look
and
feel
of
the
web,
part
I
I've,
really
limited
the
amount
of
code
and
I
have
to
change.
So,
if
I
look
at
the
what
am
I
trying
to
show
you
here,
they
get
at
the
github
service.
D
I'm
really
doing
the
same
thing.
That
Eric
was
doing
where
I'm
actually
calling
with
this
here,
I'm,
actually
creating
a
URL
and
I'm
calling
with
the
HTTP
client
I'm
calling
the
web
service.
But
what
you'll
notice
is
when
I
receive
the
data?
I
receive
it
as
a
github
user
profile.
Now,
how
did
I
create
this
class?
D
D
D
I
was
really
not
proud
of
the
look
and
feel
that
web
parts,
so
what
I
did
here
is
it's
a
version
that
uses
the
PNP
components
if
I
again,
if
I
change
the
user
here
you
know,
do
the
same
code
that
we
did
before,
except
that
the
the
rendering
of
the
web
part
is
localized
to
that
one
tsx
files
that
we
we
demonstrated.
So
there
was
a
super
quick
review
of
the
code
again.
D
A
Awesome
thanks:
you
go
a
really
cool
demo.
They're
excited
to
see
that
and
I
think
a
great
comparison
between
kind
of
doing
stuff,
with
them
without
Reaktor
are
really
kind
of
applicable
to
any
other
sort
of
framework,
so
yeah
very
valuable
demo,
and
thank
you
very
much
for
that
and
for
sharing
that
with
us,
Bob
I
believe
you
are
up
next.
If
you
want
to
take
over
a
presenting
yeah.
C
Well,
let
me
I
can
hear
me,
that's
a
yes!
Oh
there
you
go
so
I'm
halfway
there.
Let
me
see
if
I
can
get
the
correct
monitor
to
share
out.
Multi-Screen
is
always
fun,
so
yeah
I
appreciated
that
demo
too.
There's
people
I
want
to
show
that
too,
because
it's
always
the
the
reactor's
thing
is
always
a
bit
of
a
of
a
blocker
for
some
people
or
some
people
kind
of
object
to
using
a
framework
like
that.
So
thanks
for
doing
that
so
yeah,
so
this
demo
actually
has
been
around
for
a
bit.
C
It
actually
started
at
the
developer.
Kitchen
last
summer
has
evolved
somewhat
since
then,
although
it
could
use
a
bit
of
cosmetic
work,
I
think,
but
that's
alright
and-
and
the
idea
here
is
there's
there's
some
patterns
that
I've
noticed
in
custom
solutions
for
collaboration
over
the
years
and
one
of
them
I
call
the
360
degree
collaboration
pattern.
The
idea
is
to
give
users
who
are
collaborating
a
360
degree
view
or
or
mashup
of
the
business
that
they're
doing
of
some
particular
business
entity.
C
So,
for
instance,
a
property
management
company
might
have
a
complete
view
of
a
property.
Consulting
company
might
have
a
complete
view
of
a
of
a
consulting
project,
etc,
etc.
So
so
that's
the
basis
of
the
demo.
In
this
case
we've
got
some
insurance
adjusters
and
if
you've
never
dealt
with
these
folks,
you're
really
I
mean
they're,
mostly
nice
folks,
but
there's
you're
still
lucky,
because
usually
something
bad
happened
that
you
have
to
go,
call
and
say:
hey.
C
My
I
had
a
problem
in
my
building
or
my
car
or
something
and
the
adjuster
comes
out
and
decides
how
to
pay
your
claim.
They
also
inspect
new
buildings
and
new
construction.
So
here
they're
working
together
in
Microsoft
teams
and
they're,
using
the
team's
Channel,
the
team's
meeting
facility
for
coordinating
their
work.
So,
for
instance,
Katie's
gonna
go.
C
So
I
can
see
what
my
team
is
doing
by
just
looking
at
the
calendar,
and
these
have
the
advantage
that
they
go
into
the
channel,
so
everybody
in
the
team
can
see
them,
but
they
also
go
into
your
personal
calendar
if
you're,
if
you're
listed
over
here,
but
this
is
a
really
hard
way
to
see
what's
going
on
in
the
team.
So
hence
this
field
visits
tab,
which
is
which
is
the
demo.
C
So
this
is
written
in
SharePoint
framework,
of
course,
or
else
I
would
not
be
on
this
call
and
you'll
notice
that
what
it
did
was
it
it
went
and
found
everything
on
the
calendar
broke
it
down
by
user
selected
Katie,
because
she's,
the
currently
logged
in
user
and
now
here's
that
hungry
coyote
imports
and
I
can
see
everything
that's
going
on.
So
this
is
the
360-degree
view.
The
idea,
being
anything
you
need
to
know
about
in
order
to
prepare
for
this
visit
is
all
in
one
place,
so
this
is
mainly
using
the
graph
API.
C
This
is
kind
of
POC
quality
code,
meaning
I
I
think
it's
structured
for
that.
You
could
add
on
to
it
and
production-wise
it
without
starting
over
again,
if
you
wanted
to.
But
basically
you
know
the
data
is.
This
is
mock
data
here
these
activities.
These
documents
are
in
SharePoint,
they're
tagged
with
the
customer
ID
of
the
customer.
The
photos
are
also
in
SharePoint.
Similarly
tagged,
I've
got
the
weather
current
weather
conditions
at
the
customer
location.
C
The
customer
database
is
our
old
friend
the
Northwind
database
exposed
in
it,
so
data
server
I
can
even
see
where
the
thing
is
so
everything's
here
and
that's
kind
of
the
concept.
So
what
is
this
demo
show?
Well
first,
it
shows
how
to
take
a
sure
point
framework
webpart
and
make
it
work
in
teams.
So
this
does
work
in
both
environments.
C
Another
thing
it
shows
us
how
to
call
the
graph
API
and
how
to
actually
interact
with
the
team
and
the
office
365
group
and
the
SharePoint
site
that
are
inside
of
that
team.
So,
what's
interesting
about
this,
I
often
get
questions
from
developers
who
I'm
helping
out
hey
how
come
I
can't
I-I've
got
this
team's
API
and
it
won't.
Let
me
talk
to
the
team.
How
do
I
get
to
the
rest
of
the
team,
and
so
the
answer
is
well
there's.
C
C
Then
the
other
thing
that
you
can
do
here
is
Katie
obviously
has
a
scheduling,
conflict
so
help
I
have
a
schedule
conflict.
Can
someone
take
this
and
and
she
can't
I-
don't
have
spellcheck
in
there
yet
but
anyway,
here
it
is
here's.
The
message
now
has
turned
up
in
the
channel.
If
I
switch
over
to
my
user
you'll
see
that
I
can
see
this
coming
from
Katie
and
if
I
click
on
the
item,
it's
gonna
deep
link
me
back
into
the
tab
and
it's
actually
gonna
select
the
same
meeting
that
she
mentioned
so
now.
C
I
don't
have
to
think
how
many
emails
the
saves
going
back
and
forth
with
Katie.
Where
is
the
meeting?
Who
am
I
supposed
to
talk
to
and
hey
it's
all
here
right
with
one
click.
So
that's
the
concept.
There's
a
blog
series
on
this,
which
the
first
article
explains
the
concept
of
360-degree
collaboration.
Then
the
second
one
talks
about
how
to
use
the
api's
and
if
I
had
a
little
more
time,
I
don't
I'm
trying
to
kind
of
catch
up
here,
so
I'm
not
going
to
go
into
it.
C
But
this
goes
into
some
detail
on
how
to
use
the
team's
api
to
get
enough
information
to
call
the
graph
api
and
then
finally,
deep
linking
is
covered
in
this
third
article,
which
basa
I
have
updated
the
article
based
on
something
that
you
and
waldek
said
the
other
day.
This
deep
link
format
is
indeed
a
documented
and
supported
link
format.
What
is
missing
is
the
SharePoint
framework
part.
C
So
here's
the
here's,
the
link
format
and
yes,
it's
a
complex
format
that,
let's
see
there's
a
way
to
do
it
the
SDK
and
have
a
pop
up,
but
there's
also
this
format
here,
which
I
documented
in
my
blog
article
and
yeah,
it's
all
official
and
they
can't
they're
not
going
to
change
it
without
letting
us
know,
because
you
know
this
is
all
part
of
the
official
documentation.
However,
what
you'll
notice
is
that
there
are
this
documentation
only
covers
configurable
tabs
and
static
tabs.
C
Well,
it
turns
out
that
SharePoint
framework
uses
the
entity
ID
which
it
kind
of
has
to,
because,
when
you
add
your
tab
to
teams
the
configuration
experience,
that's
when
the
entity
ideas
is
decided,
so
that's
already
there
and
you
can't
really
change
it,
but
the
sub
entity
ID
does
not
seem
to
be
used
by
SharePoint
framework.
So
I
guess
the
the
confirmation
that
this
is
fully
supportive.
C
I
just
have
to
use
that
in
my
deep
link
and
then
the
sub
entity
ID,
which
I'm
going
to
use
myself
to
to
pre
load
the
correct
meeting
at
runtime
and
I'm,
passing
all
those
things
into
my
route
into
my
root
component
in
SPF
X,
so
I
think
I'm
gonna
stop
here,
I'm
just
happy
for
any
input.
I
would
love
to
collaborate
with
a
visual
designer
to
make
this
look
better.
I
am
very
humbled
by
my
lack
of
design
skills.
A
Yeah
we'll
get
that
shared
out
super
great
demo
again,
so
no
pressure,
Luis,
you
are
up
for
a
third
demo
today
on
the
call
take
care
of
the
presentation.
Thank
you
Bob
for
that
really
appreciate
it
and
III.
Don't
know.
I
used,
table
tags
and
I
get
yelled
at
in
layout,
so
I
got
nothing
nothing
for
you.
C
E
E
Couple
of
minor
changes
in
in
duets.
Ladies
I'm
gonna
shoot
me
the
poor
request
later
today
or
or
tomorrow.
So
one
thing
I
miss
when
creating
a
team
is
the
ability
to
have
taps
to
it
in
a
managed
way.
So
what
I
told
in
this
sample
is
an
SPFs
web
part
and
that
do
see
some
custom
scheme
extension
in
the
graph
api
to
a
store
and
different
tasks
that
are
coming
from
a
terms
in
sharepoint.
So,
let's
take
a
look.
The
web
part
has
been
deployed
into
into
a
teams
in
the
themes
tab.
E
Is
loading
this
natural
attack
for
this
specific
team-
and
this
is
just
in
the
taxonomy
picker
component
from
the
PMP?
We
have
controls.
So
thank
you
to
the
community.
So
here
you
can
grab
the
different
tasks
for
this
specific
term
set
in
this
pace
and
you
can
save
the
data
in
this
specific
specific
team,
for
this
demo
is
only
up
to
three
types,
but
you
can
you
can
change
that
and
the
a
specific
term
set
is
confusing
the
settings.
E
The
work
part
so
I'm
just
a
strain
with
the
terms
that
ideas
always
pointing
to
a
specific
terms
in
SharePoint,
so
the
types
are
managed
somehow
in
some
way
in
certain
point
now,
also,
obviously
using
the
magic
by
DSP
FX
framework.
Everything
is
working,
fine
in
even
SharePoint
as
well.
This
is
another
another
team.
With
this
couple
of
of
terms
sets
of
terms
so
I
think
was
also
interesting
to
have
the
ability
to
find
to
use
these
tabs
for
finding
similarities
in
19.
So
that's
another
button.
E
So
in
this
case
is
getting
the
first
stock,
but
you
can
change
the
query
and
make
it
as
complex
as
you
want
in
this
case.
Is
gonna
grab
the
guides,
so
if
I
know
Graham
there's
a
couple
of
themes
with
the
guides
term.
One
is
this
theme
and
the
other
one
is
the
one
that
I
was
so
doing
to
into
sharp
one.
So
again
here,
it's
gonna,
so
do
the
same
clapping
of
themes
with
the
guides,
tear
our
money
and
so
in
the
rest
of
the
the
rest
of
the
terms.
E
E
You
can
use
graph
explorer,
as
I
was
sewing
in
there
in
a
minute
by
the
way,
so
you
can
use
the
graph
Explorer
create
opposed
to
this
scheme.
Extensions
endpoint
and
you
need
to
submit
up
get
somebody
like
that.
One
when
you
are
second
an
ID,
this
owner
is
by
the
way
anybody
client
ID
in
an
agile,
Active,
Directory
application.
E
Then
you
have
to
say
what
kind
of
target
you
want
to
assign
today
to
the
extension.
It
can
be
group
user
mail
calendar,
these
kind
of
things,
and
it
is
in
graph.
Not
all
of
them
are
support
yet,
but
most
of
them,
and
then
you
can
set
the
different
properties
for
the
suspension,
the
different
fields
and,
fortunately,
so
far,
there's
no
any
kind
of
a
right
support.
E
Considering
if
you
take
a
look
to
some
of
the
out-of-the-box
extensions
in
graph
schemas
tension
in
graph
like
this
one,
for
example,
you
can
find
something
like
device.
I
think
one
device,
ID
2
3,
always
one
was
two
three
so
since
like
ballot
approach
for
for
this
kind,
this
kind
of
things.
So
if
we
jump
into
into
the
code
I'm
not
gonna,
go
much
deeper,
cuz
we're
running
out
of
time,
but
we
have
reactors
VFX
web
part
on
here.
E
E
We
need
to
do
like
three
different
parties
to
the
graph
API
so
for
getting
the
specific
tax
already
a
story
in
the
team.
What
we
are
doing
is
calling
the
the
group
endpoint.
We've
got
a
specific
group
idea
that
has
coming
from
there
from
the
context
and
with
the
graph
HTTP
client,
also
from
the
context
from
the
word
part
and
requiring
getting
the
ID
display
name,
a
specific
customers
to
my
stance
and
everything
about
the
schemas
tension.
You
can
create
open
extensions
and
his
team
extensions
in
graph
and
the
scheme.
E
E
If
we
want
to
update
a
specific
extension
in
the
in
the
group,
we
need
to
again
using
a
graphics,
TTP
client
to
do
a
budget
request
and
save
in
the
body
with
extreme
extension
on
the
different
values
that
you
want
to
set
for
of
the
four
inches
Pacific
or
specific,
tough.
And
finally,
if
we
want
to
search
for
other
teams
having
the
the
same
task,
it's
something
like
this
column.
E
Here
we
call
it
a
group
set
point
and
again
we
can
use
the
specific
field
that
one
in
the
schema
extension
in
the
filter
in
a
novela
filter,
query
and
then
get
in
teams.
With
the
same
that
one
that
we
have
in
this
in
this
group
and
then
we
are
just
getting
the
ID
display
name
under
different
under
different
types.
So
with
all
of
this,
we
are
rendering
the
different
values
of
dating
and
and
so
on,
so
I
think.
That's
everything
that
I
want
to
show
you
I'm
in
love.
There's
any
question
or
comment.
A
Another
great
demo,
Thank
You
Louise,
for
that
I-
think
there
might
be
a
couple
questions
there
in
the
window,
but
really
excited
to
see
that
I
just
reminder.
If
you
would
like
to
demo
some
of
your
work,
please
just
reach
out
we'd
love
to
have
you
demo
on
an
upcoming
call,
always
excited
to
see
what
folks
in
the
community
or
building
our
next
meeting
is
June
20th,
that
is
in
two
weeks,
that'll
be
our
last
meeting
before
the
July
breaks.
A
Our
next
general
sharepoint
development
specialist
group
will
be
next
Thursday
on
June
13th
I
want
to
say
thank
you
again.
It's
everybody
that
joined
the
call
today,
thank
you
again
to
our
presenters,
Hugo,
Bob
and
Lewis.
First,
those
really
great
demos.
Just
a
final
reminder.
We
will
be
off
on
July,
so
no
calls
no
recordings,
no
things
like
that
in
July
and
then,
as
always.
Thank
you
everybody
for
joining
the
call
and
we'll
look
forward
to
talking
to
you
all
soon
have
a
great
rest
of
your
week.
Buh-Bye.