►
Description
Viva Connections & SharePoint community call on November 3. Two demos: Getting started with PnPjs in SPFx solutions, AND Building ISV offering for Microsoft Viva with SPFx ACEs and multi-tenant APIs hosted in Azure. Announced CLI for Microsoft 365 - 5th Birthday Party, November 17, 10:00 pm CET on discord. Project releases include: SharePoint Framework (SPFx) – v 1.16 (RC) and CLI for Microsoft 365 – v5.9.0 (GA). See or listen to the latest episodes of Microsoft 365 PnP Weekly. The host of this call is Derek Cash-Peterson (Sympraxis Consulting) - @spdcp. Q&A takes place as always in chat throughout the call.
Learn more
• See the full blog post for this call in the Microsoft 365 platform community blog - https://aka.ms/m365pnp/blog
• Download invite for bi-weekly SharePoint Framework call at: https://aka.ms/spdev-spfx-call
• Microsoft 365 Unified Sample gallery - https://aka.ms/m365/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Platform Community - http://aka.ms/m365/community
A
B
B
We
have
a
packed
agenda
so
we're
going
to
just
jump
right
into
it.
We're
going
to
get
the
latest
updates
on
the
SharePoint
framework,
we're
going
to
have
some
updates
on
some
various
activities
from
the
patterns
and
practices,
team,
pmp.js
CLI
for
M365
and
the
reusable
PNP
spfx
controls.
We
are
going
to
talk
about
some
updated
or
new
samples
that
we've
got
and
then,
as
always
picture
time
with
together
mode
and
really
why
most
folks
are
here
is
the
demos
from
Julie
and
Paolo
to
see
some
real
world
things
that
they've
been
working
on.
B
So
if
you
are
interested
in
getting
involved
in
the
community
here,
there's
lots
of
different
ways.
You
can
do
that.
You
can
do
that
by
sharing
a
demo
that
you've
done
on
one
of
these
calls.
It
could
be
something
you've
done
for
your
your
company
as
long
as
it's
redacted
and-
and
you
have
permission
it
could
be
something
you
worked
on
as
a
side
project
or
something
you
can
share
that
you
can
also
contribute
a
sample.
You
can
contribute
to
any
of
the
issues
lists
on
GitHub.
You
can
also
provide
feedback.
B
You
know
how
are
we
doing
on
these
calls?
We
love
to
hear
things
that
we
could
do
better.
We
also
want
to
hear
what
we're
doing
right.
Do
you
want
to
change
the
documentation?
Did
you
find
an
update
there?
You
can
do
all
of
that
and
if
you
are
interested
in
scheduling
a
demo
for
one
of
these
calls,
you
can
use
the
URL
at
the
bottom.
Aka
dot
Ms
slash,
M365
PNP.
A
All
right,
excellent!
Thank
you,
Derek!
Well,
friends,
as
you
saw,
there
is
a
ton,
a
ton
ton
ton
of
resources
available
to
you,
samples
projects
that
you
can
contribute
to
all
kinds
of
stuff,
and
so
we
want
you
to
feel
empowered
to
be
part
of
that
is
your
community
and
you
are
welcome
to
submit
samples
and
get
involved,
but
you
may
feel
like
I'm,
not
quite
sure
how
to
do
some
of
that.
Well,
sharing
is
caring.
Is
a
program
here,
that's
going
to
provide
you
Hands-On
guidance.
What
does
that
mean?
A
We
have
some
available
now
we're
adding
more
any
day
now
as
well.
So
check
them
out
at
AKA,
dot
Ms
forward,
slash
sharing
is
caring,
then,
once
you
do
contribute,
we
want
to
recognize
and
celebrate
all
the
amazing
things
that
you're
doing
in
the
community
and
we're
doing
that
with
our
recognition
program,
which
is
powered
by
credly.
Yes,
you
say
quietly
that
sounds
familiar
to
me
that
same
credly,
that
provides
you,
those
badges
that
you
get
when
you
are
certified.
These
are
exactly
the
same.
A
They
sit
it
right
alongside
those,
so
you
can
show
your
clients
and
your
managers
that
you're
effectively
making
an
official
difference
in
the
community
again
no
cost
at
all.
We
cover
that
we
do
need
you
to
opt
in
AK
dot,
Ms
forward,
slash,
m365pnp,
Dash
recognition
and
a
special
congratulations
to
all
those
that
participated
in
the
Oktoberfest.
Those
badges,
some
have
gone
out.
Some
are
still
being
compiled
through
all
of
the
submissions
and
contributions
so
be
on
the
lookout
for
your
email
in
the
next
few
days.
C
Excellent,
so
quick
updates-
and
here
first
of
all,
the
ship
on
framework
1.16
release
candidate
went
out
was
a
test
today,
I
guess
it
was
yesterday.
Yes,
it
was
yesterday
time
for
class
when
you're
having
fun.
So
we
release
the
release
candidate
yesterday
and
we
didn't
do
a
significant
update
on
the
post.
It's
basically
a
revamp
of
the
previous
announcement,
but
the
features
and
capabilities
are
the
Saints
which
we've
been
sharing
already
publicly.
C
The
main
focus
here
is
enabling
the
SharePoint
program
Solutions
to
be
available
in
SharePoint
teams,
which
is
fully
G8
and
then
in
Outlook
and
office.com,
which
is
now
days
called
Microsoft
365m.
Now,
on
the
outlook
on
officer
a
Microsoft
365
app
just
to
call
them
out
they.
Those
experiences
are
only
available
in
the
preview
tenants,
so
in
a
targeted
release
mode,
so
they're
not
considered
as
a
ga
yet,
but
that's
coming
first
half
of
next
calendar
year
whenever
those
applications
are
ready
to
host
Microsoft
teams
applications.
C
Now,
let's
go
to
the
following
slide:
quick
recap
on
the
timelines
and
versions
which
are
available
as
a
1.15.2
is
the
currently
still
the
latest
version
in
production.
1.16
GA
will
happen
in
mid-november,
so
we're
talking
about
days
rather
than
weeks
or
months
right
now.
So
that's
coming
up
relatively
soon
and
in
there,
as
said
the
key
point
being
the
spfx
solutions
with
the
teams,
JavaScript
SDK
V2
support
and
that
enables
then
those
solutions
to
be
across
multiple
other
applications
and
you
can
access,
for
example,
Outlook
apis
to
that
endpoint
and
the
typing.
C
Now
you
can
of
course
build
spfx
Solutions
in
teams,
SharePoint,
Viva
Aces,
and
all
of
that
is
available
in
a
ga
mode
across
the
stack
1.17
ETA
is
the
first
quarter
of
2023
and
spfx
V2
in
quotes,
and
let's
see
if
we
can
get
the
name
chains
finally
completed
at
that
time
will
happen
later
next
year.
So
there's
a
lot
of
a
lot
of
interesting
stuff
in
the
roadmap,
but
that's
it
for
spfx
site.
Let's
move
I
think
bmpj
is
excited
big.
D
Original
it
is
it
is,
it
is
so
we
have
a
new
version,
as
we
do
every
month
going
to
be
released,
November
11th.
This
has
always
has
our
general
documentation
updates.
We
have
a
bug,
fix
for
the
eye
folder
and
get
item
error
where
it
was
returning.
The
parent
folder,
not
the
list
item
so
that
bug
has
been
fixed.
We
have
a
bug
fix
for
paged
behavior
in
list
items.
There
was
a
fix
for
rendered
list
data,
as
stream
was
not
working
in
batches
that
has
been
fixed.
D
We
added
the
ability
to
get
the
content
from
the
versions
of
a
file.
So
if
you
go
and
retrieve
the
version
of
an
item,
then
you
can
get
the
content
for
that.
So
that's
helpful,
and-
and
that
means
that
we
also
improved
the
typings
for
I
version
info,
and
then
we
added
the
ability
to
invoke
the
search
and
suggest
endpoints
for
SharePoint
and
and
then
updated
the
corresponding
documentation.
There's
actually
been
a
couple.
Other
bug
fixes
since
then
so
check
out
all
the
issues
that
were
closed
and
the
pull
request.
D
If
you
want
to
see
what's
going
on
there
and
as
well,
you
can
test
out
any
of
these
above
fixes
with
our
nightly
build.
So
if
you
install
the
at
PNP,
slash
SP
at
V3
nightly
or
graph
at
V3
nightly
Etc,
you
can
test
out
any
of
the
fixes
that
have
been
merged
to
this
date
and,
as
always,
follow
us
on
M365
pmpjs
on
Twitter
to
see
all
of
our
updates
when
they
happen
back
to
you,
Derek.
B
E
E
We
have
had
over
30
PR's
submitted
and
we've
had
lots
of
new
contributors
which
I'm
delighted
to
say:
we've
hit
a
milestone.
We
now
have
a
hundred
contributors
on
the
repository,
which
has
just
been
fantastic
lots
of
new
people
getting
involved
as
well.
I
want
to
highlight
one
individual
Nico
declare
who
basically
has
got
involved
in
the
last
couple
of
weeks
and
submitted
nine
PRS,
which
is
amazing.
E
So
thank
you
very
much
for
for
the
contributions
and
just
across
the
you
know,
the
the
whole
Community
everyone
getting
involved
and
and
really
kind
of
pushing
all
the
updates
during
hacktoberfest.
So
we've
got
lots
of
new
commands,
so
we've
got
lots
of
Power
Platform
commands,
there's
still
more
issues
that
are
available.
So
if
you're
interested
in
you
know
continuing
contributing
past
hacktoberfest,
there's
still
tons
of
issues
that
you
can
pick
up,
but
we've
got
support
for
cards,
environments,
gateways
tables,
Solutions
and
tenant
settings.
E
We've
got
some
more
commands
for
SharePoint
online,
managing
event,
receivers,
lots
and
lots
of
commands
around
permissions
as
well
so
breaking
inheritance
role,
definitions,
role,
assignments
that
there's
a
great
coverage
in
there
now
and
we've
also
got
a
few
more
commands
for
to
do
that.
Doesn't
even
scratch
the
surface,
because
I
encourage
you
to
check
out
the
release,
notes
which
I've
just
put
a
load
of
links
in
the
chat
and
there's
a
whole
host
of
updates
and
enhancements
to
existing
commands
as
well.
E
So
I
really
highly
recommend
that
you
check
that
out
see
if
there's
any
commands
that
you're
using
at
the
moment
that
you've
got
new
capabilities
that
you
can
use
so
to
get
the
new
version
of
sale,
life
Microsoft
365.
You
can
get
that
from
npm
using
the
at
latest
tag
or
if
you
want
to
just
try
it
out
best
place
to
do
that
is
using
our
Docker
container
use
the
latest
tag
on
there
and
you'll
get
the
5.9
version.
E
We've
got
a
few
things
coming
up,
so
we
have
our
fifth
birthday
party,
that's
taking
place
in
a
couple
of
weeks
on
on
a
Thursday
morning
and
we'd
highly
encourage
you
to
to
join
and
we're
going
to
have
a
little
bit
of
a
conversation,
a
little
bit
of
a
presentation
from
baldec
we're
going
to
have
a
quiz
we're
going
to
potentially
have
some
prizes
as
well
that
you
can
that
you
can
win.
Please
take
a
look
at
the
the
link
in
the
chat.
E
I've
put
a
link
in
there
to
the
the
party
invite
please
register
interest
so
that
we
we
know
that
you're
gonna
come
along!
That
would
be
great
and
for
for
this
month
as
well,
we're
planning
to
release
version
six
as
well,
so
great
that
we've
done
five
years,
we're
already
on
to
version
six,
if
you're
not
already
following
us
for
the
latest
updates.
Please
check
out
the
Twitter
handle
at
CLI,
Microsoft
365.
E
B
F
Thank
you,
Derek
I
would
love
to
say
as
Julian
Gary
that
hey
it's
a
new
month
and
new
version,
but
no
we
are
still
on
311
and
310.
So
no
huge
updates
here
there
are
some
plans
to
review
PR's
fixing
backs
on
the
next
few
weeks.
So
hopefully
we
will
have
some
new
releases
in
a
couple
of
weeks.
So
that's
all
from
my
side.
B
Okay,
all
right
thanks,
Alex
and
modern
search.
The
4.8
beta
was
out
in
well.
It
should
have
been
the
September
22
release,
but
I
guess
we're
gonna,
make
it
through
November
release
and
a
special
thanks
to
a
bunch
of
folks
who
submitted
some
PRS
for
support
for
actionable
adaptive
cards
like
viva,
viva
Aces,
and
keep
track
of
all
the
release.
Notes
for
the
updates
that
came
through
and
with
that
I'm
going
to
hand
it
over
to
David
for
PNP
spfx
samples.
A
Awesome
again,
thank
you
Derek
still,
friends.
We
have
a
plethora
of
samples
within
svf
extensions,
webparts
and
Aces
we're
getting
all
those
PR's.
We
just
want
to
mention
that
we
know
that
we're
a
little
behind
on
that.
We
really
appreciate
all
of
your
patience
and
the
amazing
samples
that
you've
been
contributing,
we're
bringing
in
reinforcements
to
get
those
processed.
It's
been
a
busy
couple
of
months
for
us,
but
don't
don't
lose
sight
of
those
PR's
getting
accepted.
A
C
Absolutely
I
will
share
my
screen.
We'll
do
that
and
we'll
wait
few
more
seconds
for
people
to
join
so
we'll
get
the
full
room
we
do
have
again
180
or
so
live
attendees.
Let's
see
how
many
people
will
get
to
the
screen
as
well.
A
few
more
seconds
few
more
seconds,
Let's
Wait,
a
While.
We
still
have
rooms
room
in
the
room
in
the
room.
C
Does
that
make
sense,
it
makes
sense,
there's
room
in
the
room,
so
room
room,
I,
guess
that's
filling
in
the
50
I
will
put
the
recording
on.
Let's
do
some
hand,
faving
we'll
grab
a
gif
animation
out
of
that
and
share
that
in
LinkedIn
and
in
Twitter
and
in
social
media.
Thank
you,
everybody
once
again
joining
on
the
community
call.
Hopefully
you
can
make
the
Las
Vegas
or
Copenhagen
later
this
year,
so
we
can
meet
in
person
as
well,
but
we'll
be
in
this
community
course
as
well.
C
D
All
right,
so
what
we
have
today
is
a
pmp.js
version,
3
sample
solution,
and
so
what
I
decided
to
do?
We
do
have
a
Patrick
and
I
did
do
videos
on
this
sample
and
the
sample
is
available
in
the
dev
spfx
sample
repo.
So
you
can
go
and
check
it
out.
I
did
update
it
a
tiny
bit
for
today's
call
to
just
do
highlight
some
other
things,
and
so
so
this
is
a
demo
you
can
in
general,
see
but
we'll
we'll
go
through
it
a
little
bit
a
little
bit
more
detail.
D
Okay,
so
this
is
the
sample
that
I'm
going
to
show
you
the
code
for
essentially
what
it
does
is.
It
looks
into
the
document
library
and
it
gets
all
the
documents
in
the
document,
library
and
Returns
the
size
and
the
name
and
the
title
of
the
document,
and
then
I
have
a
button
here.
That
updates
the
titles
and
what
it
essentially
does
is
just
append
the
word
Dash
updated
to
each
name,
which
is
super
like
super
use,
useful
right.
We
all
want
to
be
able
to
do
that.
D
So
if
we
click
update,
item
titles,
it'll
go
out
and
do
that
update
and
then
update
the
UI
so
that
it
shows
that
the
name
of
the
file
was
updated.
If
we
go
in
the
document,
Library
it'll
show
that
the
other
thing
that
you
see
here
is
this
little.
This
extra
new
thing
that
says
my
name
is
Julie
Turner
and
we're
going
to
talk
about
where
that
came
from
and
why
in
just
a
second?
D
So
that's
what
we're
gonna
look
at
code
for
so,
let's
start
and
switch
over
to
the
code,
and
so
here's
our
solution
and
I'm,
starting
by
looking
at
the
package.json.
So
when
you
want
to
use
pmp.js,
you
need
to
install
those
dependencies
and
if
you
go
to
our
documentation
and
look
at
the
getting
started,
documentation
it'll
show
you
how
to
do
that
specifically.
But
I
want
to
just
point
out
that
for
this
project,
I've
included
the
SP
package,
which
is
all
the
SP
SharePoint
rest
endpoint
support
and
then
I
also
included
the
graph
one.
D
And
this
is
our
support
for
graph
calls,
and
this
is
not
in
the
sample
that
you'll
find
on
the
repository.
That's
why
that's
sort
of
new
for
today-
and
we
also
added
the
logging
package
in
V2.
The
logging
package
was
embedded
in
the
SharePoint
package
in
the
graph
package,
but
we've
separated
it
out
for
V3.
So
that's
a
separate,
install
now.
Okay,
so
we
have
our
packages
installed
and
it's
all
running.
So
we
know
everything
is
good
to
go.
So
now
we're
going
to
talk
about
this
config
file.
D
So
one
of
there's
essentially
two
ways
to
that.
We
recommend
that
you
bring
use
PNP
JS
in
your
Solution
by
one
either
creating
a
sort
of
a
config
file
or
a
container
for
all
of
your
pnp.js
calls,
or
that
you
create
a
service
I'm
not
going
to
demo
a
service.
Today,
I
will
say
that
a
service
is
how
I
do
all
of
my
coding,
but
that
doesn't
necessarily
work
for
everything
so
and
for
everybody
in
their
in
their
patterns
of
development.
D
Is
it
a
way
for
us
to
consolidate
all
our
Imports
that
we're
going
to
use
in
one
place,
and
so
what
that
means
is
that
for
each
of
our
libraries,
our
SP
library
and
our
graph
Library,
we
have
packages
of
functionality
and
we
blocked
them
into
different
Imports
so
that
you
could
just
import
the
bits
of
functionality
that
you
need
for
your
project,
thereby
keeping
the
amount
of
code
that
you're
bundling
in
as
small
as
possible.
So
I've
included
all
the
stuff
that
I
need
for
the
SharePoint
rest
calls
that
solution
did
so.
D
We
need
these
Baseline
SharePoint
ones.
We
are
going
to
use
logging,
so
our
logging
package
is
imported
and
then
we
imported
webs
lists
items
and
batching,
because
I'm
going
to
show
you
batching
and
then
in
addition
to
that,
as
I
said,
we
I
included
graph.
So
one
of
the
things
I
want
to
point
out
right
now
is
that
if
we
were
just
using
SharePoint
and
not
using
the
graph,
then
this
import
right
here
where
it
says
spfx
could
just
be
that
we
wouldn't
need
this
additional
part
here.
D
This
additional
part
where
it
says
as
SP
spfx
is
sort
of
a
renaming.
So
in
the
PNP
SP
package
there
is
a
method
for
spfx.
That
ins
creates
the
behaviors
that
we
need
we're
going
to
give
it
a
different
label,
because
there
is
an
identically
named
one
in
our
graph
package
for
instantiating
graph
context
and
so
I'm
going
to
rename
that
one
to
graph
spfx,
because
I'm
going
to
use
both
libraries
so
now
I'm,
creating
globals
for
our
SharePoint
Factory
interface
in
our
graph
Factory
interface
and
then
I'm.
D
Creating
two
methods
here
that
I'm
going
to
export
so
I'm
exporting
a
constant
that
is
get
SP.
It
needs
the
context.
That's
the
web
part
context
passed
into
it
and
then,
assuming
that
the
context
isn't
null
it's
just
going
to
create
the
the
SharePoint
Factory
interface
that
we
need.
So
we
could
then
call
spfi.
D
We
say
we're
going
to
use
the
behavior,
the
SharePoint
spfx
Behavior,
which
establishes
our
context.
So
we
pass
the
context
to
it
and
just
to
illustrate
how
you
can
add
a
chain
additional
behaviors,
we're
going
to
add
dot
using
and
then
we're
going
to
pass
in
PMP
logging,
because
we
imported
that
and
set
our
level
our
level
for
when
we
want
logging
to
occur.
D
So
this
is
how
you
chain
behaviors
together,
and
if
you
look
at
our
documentation,
you
can
see
a
bunch
of
different
behaviors
that
we
provide
and,
of
course
you
could
build
your
own.
So
that
then
sets
up
this
SP
object,
which
is
a
global.
So
then
we
have
an
identical
method
for
getting
the
graph
context
and
again
it's
the
factory
interface
we're
using
our
graph
spfx
to
create
the
context
for
graph
and
I'm
using
logging
on
that
one
too.
It's
the
exact
same
thing:
okay,
so
let's
just
ignore
that
for
a
second
and
move
over.
D
Okay,
that's
the
big
change
from
version
2
to
version
three
is
that
those
objects
are
not
Global
anymore,
so
we
need
to
sort
of
create
our
own
Global
versions
of
them.
Okay,
now
that
that's
done,
we
can
just
jump
right
into
our
root
component.
So
this
is
our
root
component
that
we,
that
does
all
the
work.
This
is
maybe
not
how
I
would
do
it
in
production
and
I
want
to
kind
of
make
that
point
that
this
example
is
purely
met
as
an
example.
D
D
D
So
what
we
do
to
do
that
is.
We
have
this
SP
Factory
method
and
if
we
pass
an
existing
Factory
interface
into
it,
what
that
will
do
is
copy
all
the
behaviors
that
are
already
exist
on
the
SP
Factory
and
the
this
dot
underscore
SP
Factory
interface
to
the
new
one,
we're
creating,
which
will
include
our
context,
which
means
that
we
have
all
authentication
stuff
that
we
need
to
use
it
as
well
as
the
logging
that
we
had
added
in
that
original
one.
D
D
That
is
a
little
bit
more
clean
where,
if
there's
no
title
I'm
going
to
say
it's
unknown,
if
the
file
length
doesn't
exist,
I'm
going
to
set
it
to
zero,
just
some
cleanup
on
those
items,
and
then
this
is
the
added
thing
here:
I
added
a
new
method.
Here
again,
this
is
not
how
you
would
do
this
in
production,
I
added
a
new
method
here,
where
I'm
going
to
load
a
user,
and
this
is
where
I
wanted
to
just
demo
quickly.
That
I
can
make
graph
calls
here
as
well.
D
The
other
thing
that
I
want
to
show.
Let's
minimize
this
up,
is
go
back
up
to
our
render
method
and
just
show
that
here's,
where
I'm
rendering
that
display
name,
but
it
could
be.
You
know
any
of
the
other
properties
about
me,
including
about
me,
and
we
could
render
whatever
that
is
in
there,
and
this
is
where
I'm
rendering.
Then
the
items
now
I
have
that
button.
If
you
recall
where
I
was
going
to
update
the
titles,
so
let
me
come
down
here
and
just
look
at
what
update
titles
does
so
in
update
titles.
D
If
you
think
about
it,
we
have
a
whole
bunch
of
elements,
items
that
we
retrieved
from
the
document
library
and
it's
not
really
efficient
for
us
to
just
call
one
after
another.
Make
multiple
rest
calls
one
after
another
to
update
each
of
those
items,
so
in
this
case
we're
going
to
create
a
batched
instance.
So
now
I'm
going
to
take
the
SP
object
again
the
behavior
on
this
right
now.
The
behaviors
that
exist
on
this
object
are
the
context
for
security
and
logging.
D
So
now
I'm
going
to
say:
okay,
this
dot,
SP
and
then
one
of
our
root
methods
on
that
is
batched.
And
what
that
returns
is
what's
called
a
tuple
and
a
tuple
is
an
array
here
with
two
properties
in
it,
one
of
which
the
batched
SP
is
a
an
instance
of
the
the
SharePoint
factoring
interface,
but
which,
with
all
the
extra
needed
Plumbing
to
do
batch
requests.
And
then
a
second
thing
is
a
method
called
execute.
D
So
now
what
we're
going
to
do
is
I'm
going
to
just
go
clone
our
state
variable
with
items
in
it,
because
we
never
work
on
the
state
variable
directly
when
we're
we're
doing
work
like
this.
So
I'm
I'm,
using
a
little
shortcut
here
to
clone
that
and
then
I'm
going
to
Loop
through
each
one
of
the
items
and
make
a
a
call
but
I'm
going
to
use
the
batched
SP
as
the
call.
So
we'll
do.
D
So
this
is
an
array
of
the
updated
item,
results
and
I'm
going
to
push
each
of
the
results
onto
that,
so
that
they're
available
after
and
then
I'm
going
to
await
the
execute
method,
and
so,
when
I
await
the
execute
method
that
launches
all
that
batch
request,
that
I
created,
which
will
do
all
of
these
updates.
All
in
one
grouped
update
after
that,
I
then
remember
that
I
added
the
the
results
to
this
item
update,
result
array.
So
that
means
this
result
has
each
of
the
list
items
in
it.
D
So
if
I
then
Loop
through
the
results
and
do
the
result
dot
item,
this
gives
me
a
queryable
instance
of
the
item,
and
so
the
reason
we're
doing.
That
is
remember
that
when
I
got
the
items
from
the
the
list,
originally
I
used.
Caching,
and
so,
if
I
made
that
call
again
because
it's
the
same
endpoint,
it
wouldn't
know
that
it,
it
wouldn't
go,
get
a
new
version,
because
it's
cash,
so
we'd
have
to
clear
the
cache
Etc
et
cetera.
D
So
what
I'm
just
showing
you
here
is
that
we
can
use
this
item
result
since
the
batched
entry
didn't
have
the
caching
on
it.
Then
this
item
isn't
it.
It
is
not
batched,
but
it
can
be
used
to
go
and
fetch
the
item
and
ID
and
title
from
the
item
so
that
I
can
update
our
items
with
the
new
title
and
then
I
can
set
State
setting
the
new,
updated
items
because
I
cloned
them
so
I'm
going
to
set
them
back
to
State,
and
then
that
will
update
my
user
interface.
D
C
C
So
this
is
great
for
pmpjs
Snippets,
but
going
on
what
you
said,
are
there
samples
available
where
people
can
see
the
production
code
to
make
sure
that
we're
structured
stuff
correctly?
So
you
called
out
something
in
here
which
was
about
the
craft
or
something
which
is
not
about
the
production,
but.
D
D
So
when
I
say
don't
use
this
as
like
production
code,
what
I
more
mean
around
that
is
this.
The
the
structure
of
the
code,
like
I,
just
wouldn't
put
a
lot
of
this
logic
about
reading
files
and
loading,
the
user
and
updating
the
titles
in
the
same
component
file
where
I'm,
rendering
the
UI.
That
was
more.
What
I
meant
by
that
and
then
the
other
part
about
the
loading
user
I,
probably
would
do
that
I
did
it
in
line
with
reading
the
file
sizes.
D
I'd
probably
do
both
calls
at
the
same
time
and
load
them
into
separate
variables.
So
I
wouldn't
be.
You
know,
I
I'm,
essentially
forcing
a
Serial
path
through
this.
That's
why
I
was
sort
of
saying
I
wouldn't
do
this
in
production.
I
wouldn't
call
do
a
bunch
of
asynchronous
calls
and
then
do
the
asynchronous
call
to
the
loading,
the
user,
because
they
don't
depend
on
each
other.
So
there's
no
sense
in
waiting
for
one
to
finish
to
do
the
other,
especially
when
you're
writing
asynchronous
code.
That
doesn't
make
a
lot
of
sense.
D
C
C
G
Yes,
thank
you
Derek
and
thank
you
Julie
great
demo.
Now
we
are
going
to
talk
about
how
we
should
create
with
the
SharePoint
framework
in
Ace
solution
or
speaking
in
a
sharp
and
framework
solution
for
isv.
We
link
to
offer
that
solution
as
a
kind
of
a
software
as
a
service
offering
hosting
their
backend
code
on
Azure
and
having
the
proper
settings
in
place
to
make
it
happen
for
a
multi-tenant
solution.
So,
first
of
all
let
me
try
to
set
the
context.
G
So
let's
say,
let's
assume,
that
you
are
in
isv
and
you
want
to
build
a
solution
and
you
want
to
build
a
solution
which
might
be
an
extension
of
Viva
connection,
so
an
Adaptive
card
extensions
built
with
sharpen
framework.
But
what
I'm
going
to
talk
about
applies
completely
also
to
a
SharePoint
framework.
G
What
part
so
just
to
be
clear
and
let's
say
that
you
want
to
sell
or
provide
Your
solution
as
a
software
as
a
service
model
you
should
be,
or
you
should
keep
into
account
that
you
will
have
to
do
some
activities
to
register
an
application
measure
directory.
You
will
need
to
do
proper,
hosting
on
Azure
and
stuff,
like
that.
So
practically
speaking,
there
are
some
architectural
challenges
that
you
need
to
face
when
you
want
to
do
that.
G
First
of
all,
you
need,
or
you
should
at
least
create
a
multi-tenant
application
and
register
and
multi-tenant
application
measure
directory
I
say
you
should,
because
the
other
options
would
be
to
register
manually
register
and
create
an
application
on
every
single
tenant
of
every
customer,
which
means
you
are
not
offering
a
software
as
a
service
solution,
because
you
would
have
to
do
setup
stuff
on
every
single
customer
tenant,
which
is
indeed
not
doable.
So
you
will
have
to
create
a
multi-tenant
solution
and
you
will
have
to
make
your
multi-tenant
solution
available
on
all
of
your
customers.
G
Tenants
and
your
backend
services
will
need
to
be
multi-tenant
aware
in
order
to
being
able
to
do
that,
plus.
The
fact
that
your
application,
most
likely
will
need
to
do
something
with
the
target
tenants
of
your
customers
like
accessing
data
in
SharePoint
online
or
using
Microsoft
graph
and
other
stuff
like
that,
and
as
such,
your
customers
will
need
to
Grant
permissions
to
your
applications.
G
To
do
stuff
on
their
own
tenant,
so
there
are
some
requirements
from
a
deployment
point
of
view
which
need
to
be
satisfied
and
that's
why
we
are
covering
this
topic
in
this
demo.
Just
to
give
you
an
idea,
let's
imagine
that
you
are
in
isv
again
and
you
have
your
own
tenant.
You
registered
your
application
in
your
own
tenant
as
a
multi-tenant
application,
and
then
we
will
see
practically
speaking
how
and
where
you
can
do
that
and
that
you
also
configure
your
application
in
order
to
have
a
proper
permissions
to
access
Microsoft
graph.
G
Then
you
want
to
host,
for
example,
on
Azure
and
in
Azure
function,
app
your
backend
infrastructure,
so
that
your
SharePoint
framework
solution
will
rely
on
this
back-end
infrastructure
or
posted
on
a
function
app
and
you
configured.
Your
application
is
ready
with
the
client
secret
and
a
client
ID
in
order
to
being
able
to
get
a
token
to
consume
Target
resources
in
the
Target
tenant.
But
now
the
point
is
that
the
target
tenant
is
not
just
one
tenant.
The
target
tenant
will
be
any
tenant
of
any
of
your
customers.
G
Who
will
get
your
solution,
meaning
that
there
will
be
the
need
to
register
your
multi-tenant
application
in
the
Target
tenants?
The
customer
will
have
to
Grant
the
permissions
to
those
application
and
when
it's
done
any
of
the
customer
who
will
have
the
application
registered
and
the
permission
granted
will
be
able
in
your
custom
code,
which
will
be
running
in
SharePoint
or
in
Viva
connections
or
wherever
else
you
like.
G
As
long
as
you
can
run
sharpened
framework
code,
we'll
be
able
to
make
a
request
to
your
backend
infrastructure,
providing
an
access
token,
which
will
be
issued
by
the
Azure
active
directory
of
your
specific
customer
attenant
and
on
your
backend
infrastructure.
You
will
have
to
validate
the
token
and
you
will
be
able
to
get
access
to
the
back-end
infrastructure
of
the
customer
so
of
their
share
point
of
their
Microsoft
65
workloads.
Generally
speaking,
thanks
to
the
grant
of
the
permissions
that
they
admin
in
the
customer
side
did
for
your
application.
G
All
of
these
activities
require
quite
some
work
potentially
and
that's
why
and
thanks
God
that
SharePoint
framework
start
information
1.15
point
something
helps
you
a
lot
in
doing
that.
In
fact,
starting
from
this
version
of
SharePoint
framework,
there
are
some
useful
attributes
that
you
can
configure
in
the
package
solution.json
file
which
allow
us
to
have
an
easy
deployment
of
this
kind
of
solutions.
So
let
me
switch
to
the
demon.
Let
me
show
you
how
it
works
in
action,
so,
first
of
all,
I
want
to
show
you
the
actual
result.
G
This
is
a
demo
that
we
have
already
seen
something
like
one
year
ago
and
which
I
recently
updated
in
order
to
have
support
for
these
new
functionalities.
That
I'm
talking
about
this
is
an
electrical
extension.
Actually,
there
are
two
Aces
which
allow
to
manage
a
fake
list
of
orders
that
you
can
show
and
you
can
insert
additional
orders
using
this
Ace
into
into
this
list
of
orders.
This
is
an
example
that
you
can
find
also
under
the
sample
solution.
G
Gallery
right
here
and
I-
think
I
posted
on
the
chat,
the
link
and,
if
not
I,
will
do
it
right
after
this
demo.
But
here
you
can
find
a
an
easy
access
to
the
source
code.
You
can
either
download
it
or
view
it,
and
you
can
see
how
the
solution
is
built.
Now,
let
me
switch
to
the
actual
code
base
and,
first
of
all,
we
have
in
the
back
end
of
this
adaptive
card
extension
Azure
function
where
we
manage
the
list
of
orders.
This
is
a
really
regular
orders
function.
G
So
an
initial
function
running
on
Azure,
where
we
have
actions
like
get
orders
to
get
the
whole
list
of
orders,
we
can
get
a
single
order.
We
can
add
a
new
order
and
stuff
like
that.
Nothing
really
special
and
under
the
cover
we
work
with
any
memory
structure
for
orders,
just
for
the
sake
of
having
a
simple
deployment
without
the
need
to
deploy
databases
and
other
stuff
and
to
let
you
experiment
with
this
sample
without
the
need
to
deploy
a
complex
scenario.
G
This
is
your
function
is
backed
by
an
application
which
I
registered
in
Azure
directory,
and
let's
assume
that
I
am
the
isv
selling.
The
solution
here
is
in
my
tenant
in
my
isv10,
and
let
me
go
here:
the
application
registered
in
Azure
active
directory.
This
is
an
application
that
I
registered
simply
going
to
Azure
active
directory
and
going
to
app
registrations
and
creating
a
new
app
registration.
So
let
me
search
for
it
again
and
let
me
show
you
how
it
is
configured
I
have
a
client.
G
So
this
is
the
definition
in
my
isv
tenant
again,
assuming
that
I
am
the
isv
right
now
in
my
SB
tenant
of
my
multi-tenant
application
in
Azure,
active
Direction,
now
I'm
willing
to
use
this
application
as
the
entry
point
for
the
consumer
app,
which
will
be
the
SharePoint
framework
adaptive
card
extensions,
but
before
moving
there.
Let
me
switch
back
a
little
bit
more
on
the
Azure
function.
Just
to
highlight
that,
as
you
can
see
here,
for
example,
in
order
to
add
a
new
order,
I
have
an
attribute
which
is
called
the
function
authorize.
G
This
is
a
custom
attribute
and
you
can
find
the
implementation
in
the
sample
on
GitHub,
which
will
simply
declare
that,
in
order
to
be
able
to
call
this
add
order,
endpoint
of
my
function,
I
will
need
to
have
the
order.fullcontrol
permission
in
the
access
token
that
I
will
get
meaning
I'm
doing
authorization
control.
So
it's
like
as
I
need
the
orders
full
control
to
add
a
new
order.
I
simply
need
the
orders.read
or
eventually
still
find
to
have
the
orders
for
control
to
get
in
order,
so
to
read.
G
I
simply
need
the
basic
permission
to
write.
I
need
an
additional
or
Advanced
permission,
and
this
kind
of
authorization
check
can
be
done
and
should
be
done
on
the
Azure
function
side
at
the
same
time,
in
the
Azure
function,
because
we
have
configured
the
application,
Azure
ID
to
support
multiple
tenants.
We
need
to
be
aware
of
the
tenants
that
we
want
to
support.
G
So
if
we
are
offering
or
selling
our
solution
as
a
software
as
a
service
solution,
we
should
in
the
token
validation
parameters
of
our
function,
we
should
validate
the
Val,
the
issuer
of
the
token
meaning
the
Azure
active
directory
tenant,
which
will
issue
the
access
token
that
will
be
used
to
consume
our
function,
our
backend.
Why?
Because,
as
I
showed
you
in
the
previous
diagram,
we
can
have
multiple
tenants
and
each
and
every
tenant
will
have
its
own
interactive
directory,
which
will
be
the
issue
of
the
tokens.
G
So
in
our
business
logic
we
need
to
validate
if
the
issuer
is
a
tenant
of
a
customer
that
is
basically
paying
for
the
service
or
not,
and
if
not,
we
will
simply
say
sorry,
you
will
not
get
access
to
my
environment.
This
is
a
table.
One,
so
I
will
simply
accept
any
one,
but
in
your
real
life
you
should
do
proper
validation
and
store,
eventually
a
list
of
allowed
or
registered
or
paying
customer
tenants
in
a
SQL
database
or
in
a
cosmos,
DB
or
wherever
you
like.
So
this
is
the
Azure
function.
G
Now
we
want
to
consume
this
Azure
function
from
SPF
XM
from
our
adaptive
card
extensions.
Let
me
switch
to
the
spfx
solution.
This
is
the
Adaptive
card
extension
that
we
were
having
a
look
before
this
is
the
manage
borders.
I
will
not
dig
into
the
implementation
details
of
the
aces
by
themselves,
because
this
is
not
a
session
about
how
to
implement
cases.
This
is
a
session
about
how
to
manage
the
multi-tenant
deployment,
but
just
for
the
sake
of
clarity
here
in
my
adaptive
card
extension
I
have
in
the
on
init
method.
G
Once
again,
the
creation
of
the
aad
client
instance
through
the
ad
client
Factory
and,
as
you
can
see
here,
I'm
getting
a
client
for
this
specific
URI,
which
is
precisely
the
one
we
used
to
uniquely
identify
our
API
in
the
back
end.
So
through
this
methodical,
we
get
back
in
AED,
HTTP
client
object,
which
will
be
simply
provided
to
a
function,
to
a
service
that
we
have
in
our
solution,
which
will
be
the
order
service
where
we
will
rely
on
it
to
make
the
actual
requests
to
get
read,
update
and
so
on
so
forth.
G
G
This
is
what
we
have
been
doing
for
a
while
now
with
SharePoint
framework,
and
by
doing
that
we
can
build
a
package
and
we
can
deploy
the
package
in
a
Target
payment,
and
let
me
show
you
how
it
works
when
we
do
such
a
thing.
So
let
me
switch
to
a
demo
tenant
that
I
have
and
in
this
tenant
I'm
going
to
add
to
the
app
catalog
the
new
one,
the
sppkg
file
for
my
solution.
As
long
as
I
will
be
able
to
find
the
finder.
G
Okay,
here
it
is
so
this
is
my
sppkg
for
my
solution
and
if
I
will
upload
this
package
into
my
target
tenant,
you
will
see
that
okay,
now
we
have
the
SP
PKG
and
SharePoint
framework
is
smart
enough
to
say.
Okay,
you
need
to
enable
this
application.
If
you
want
on
all
of
the
sites,
because
it's
it
is
a
tenant-wide
solution.
Yes,
please
do
that
and
then
it
will
also
say:
okay
keep
into
account
that
for
this
solution
to
work
properly,
we
also
need
to
Grant
some
permissions,
which
are
the
permissions
for
my
application.
G
Let
me
go
to
the
API
access
page.
If
I
will
do
that
right
now,
I
will
be
able
to
see
that
there
is
a
solution.
My
Contours
orders,
one
which
is
pending
approval
for
the
orders.fullcontrol
permission
for
the
PMP
contoso
orders
application.
However,
if
I
will
click
on
approve
and
I'm
going
to
do
that,
it
will
fail.
Let
me
show
you,
you
see,
I,
have
this
error.
Why?
G
Because,
actually,
the
application
that
I
as
the
isv
registered
in
my
own
isv
tenant
is
not
yet
available
in
the
customer
tenant
and
as
such,
it
will
not
be
possible
to
Grant
the
permission
to
an
application
which
does
not
exist
in
my
tenant.
Okay,
so
what
I
should
do
would
be
to
open,
for
example,
a
tab
and
using
a
the
admin
constant
URL
that
Azure
active
directory
provide
us
I
will
be
able
to
register
my
application
onto
my
tenant
and
Grant
the
permissions
to
my
application.
G
This
admin,
constant
URL,
will
accept
the
ID,
the
unique
ID
of
my
application,
as
well
as
a
redirect
URI,
which
is
one
of
those
configured
in
the
authentication
section
of
my
Azure
ready
application.
Let's
do
that
by
doing
that,
okay
I
will
have
to
authenticate
as
a
tenant
admin
and
once
I
will
do
that,
I
will
be
able
to
register
and
Grant
the
permission
on
my
tenant
for
that
specific
application.
By
doing
that,
I
will
be
able
now
to
register
my
application
and
Grant
the
permissions.
G
If
I
will
go
back
to
the
admin,
Center
and
I
will
refresh
this
page
every
now
and
then
it
takes
a
while.
So
there
is
no
guarantee
that
it
will
already
work
right
now,
but
even
if
it
will
not
work
exactly
right
now,
in
a
matter
of
few
seconds
or
minutes
from
now,
it
will
be
possible
to
Grant
the
permissions
and
to
approve
the
permissions
for
this
application,
so
that
I
will
be
able.
Actually,
it
is
already
working.
Wonderful,
so
I
will
be
able
to
use
my
solution
now.
G
As
you
can
see,
this
process
is
quite
complex
from
an
end
user
point
of
view
and
that's
why
Microsoft
updated
the
behavior
of
SharePoint
framework
and
made
it
possible
to
do
something
like
that.
You
can
add
in
the
the
package
solution.json
file
of
your
solution,
the
app
ID
and
the
reply
URL
of
your
solution,
so
that
all
of
the
process
of
doing
the
registration
and
the
content
of
the
application
will
be
taken
into
account
by
the
SharePoint
framework
infrastructure
rather
than
by
your
customer,
which
is
really
good
in
my
opinion.
G
G
G
So
I
upload
the
packages
like
this
before
as
like
before
I
will
have
to
make
it
tenant
wide
available.
If
I
want
to
do
that,
enable
the
app
I
will
still
see
the
message
that
we
need
to
Grant
some
permissions
to
my
application,
but
when
I
will
click
to
the
go
to
API
access
page
now
in
this
tenant,
which
is
a
fresh
and
clean
new
one,
you
can
notice
it
by
the
different
color
in
the
top
just
kidding
but
yeah.
It
is
a
new
one,
A
different
one.
G
G
We
see
the
wonderful
page
of
M365
PMP
community,
and
by
going
back
right
here,
we
will
soon
see
that
the
application
is
now
registered
and
available
with
the
proper
permissions
configured.
So
it
will
refresh
soon
and
let's
see-
and
we
are
okay
perfect.
So
if
I
will
go,
for
example,
to
the
workbench
of
my
tenant
in
any
site
collection
of
my
choice,
I
can
now
add
the
orders
is
to
manage
order
phase,
and
you
will
see
that
I
will
be
able
to
use
my
orders.
G
Ace
I
will
have
a
bunch
of
orders
available
and
I
can
play
with
it
in
my
new
Target
tenant
oops.
Let
me
click
on
this
one,
so
it
is
really
really
useful
and
Powerful
to
being
able
to
configure
those
two
settings
inside
the
package
solution.json
file,
rather
than
having
to
provide
additional
documentation
and
guidance
to
the
customer
in
order
to
deploy
the
solution.
G
The
the
request
will
come
from
tenant.sharepoint.com
of
every
different
customer
that
you
have,
so
you
can
either
configure
one
by
one
all
of
the
tenants
of
your
customers
in
the
list
of
course
enabled
in
this
setting
or
eventually
you
can
configure
an
asterisk
to
make
it
possible
to
use
any
consumer
for
your
API
up
to
you.
This
is
really
important
fundamental.
Otherwise
your
API
will
not
work
in
the
beginning
of
a
SharePoint
framework.
B
All
right,
thank
you
very
much,
Paulo
all
right.
So,
thank
you.
Everybody!
Thank
you.
Julie!
Thank
you,
Paolo
and
thank
you
for
being
here
today.
The
recording
will
be
available
within
24
hours
on
the
Microsoft
365
Community
YouTube
channel.
You
can
also
get
to
that
from
AKA
dot,
Ms,
slash,
M365
videos,
don't
forget,
follow
us
on
Twitter
Microsoft,
365
Dev
and
at
M365
PNP,
and
the
next
Viva
Connections
in
spfx
call
will
be
on
November
17th
at
7
00
a.m.