►
Description
Microsoft 365 platform community call delivered on January 10th.
Demos in this call: Introduction Microsoft Graph PowerShell v2 preview release, Test how your SPFx solutions respond to throttling with Graph Developer Proxy, and Introduction to Microsoft Viva ACE development learn module - Getting started.
Activities: 3 articles, 1 FAQ and 2 conversations released in the last 7 days. Registration is open for 3 Sharing Is Caring sessions in January including First Time Contributor training on Thursday, January 12th.
See the blog post for this call for project updates, news and events details. The host of this call was Vesa Juvonen (Microsoft) | @vesajuvonen. Q&A takes place in chat throughout the call.
Agenda
• 08:44 – Latest updates and news on the Microsoft 365 platform – Vesa Juvonen (Microsoft) | @vesajuvonen
• 09:55 – Microsoft Teams Platform updates – Surbhi Gupta (Microsoft)
• 10:48 – Together mode picture
• 11:58 – Demo Introduction Microsoft Graph PowerShell v2 preview release – Maisa Rissi (Microsoft) | @maisarissi_msft and Peter Ombwa (Microsoft)
• 26:16 – Demo Test how your SPFx solutions respond to throttling with Graph Developer Proxy – Waldek Mastykarz (Microsoft) | @waldekm
• 36:40 – Demo Introduction to Microsoft Viva ACE development learn module - Getting started – Vesa Juvonen (Microsoft) | @vesajuvonen & Andrew Connell (Voitanos) | @andrewconnell
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 this weekly Microsoft 365 Platform community call: https://aka.ms/m365-dev-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 - https://aka.ms/m365/community
A
B
And
we
are
back
in
a
normal
schedule,
meaning
we
do
have
three
demos
scheduled
for
this
week
and
for
upcoming
weeks,
we'll
have
at
least
two
demos
from
the
original
Tuesday
call
coming
from
Microsoft
typical
Microsoft
presenters
from
engineering,
Cloud,
Advocates
and
so
on.
So
we
did
have
a
pretty
relaxed
three
weeks
during
holiday
season
and,
as
we
didn't
want
to
do
actual
demos,
we
did
quite
a
lot
of
ad
hoc
q,
a
which
actually
cut
a
lot
of
a
lot
of
feedback
as
well.
B
So
we
might
actually
do
one
of
those
that
hook
Q
A's,
once
a
quarter,
maybe
to
have
a
a
nice
kind
of
a
discussion
style
set
up
on
Tuesday
call
as
well,
but
we're
trying
to
get
more
back
on
this
normal
in
quotes
normal
Tuesday
called
mode
today,
we'll
we'll
have
three
different
demos.
So,
first
of
all,
we'll
go
through
the
general
updates.
What
has
happened?
What
are
the
getting
started
assets?
B
There
are
some
updates
over
there
we'll
talk
about
that,
one
as
we
go
through
and
then
there's
later
just
needs
to
come
around
the
Microsoft
blocks.
What's
in
the
Microsoft
teams,
platform
will
take
the
2kml
picture
with
all
of
the
attendees
who
are
willing
to
enable
the
video
and
then
we'll
have
the
actual
stars
of
today,
we'll
start
with
maisa
and
Peter.
B
Around
introduction,
Microsoft
Powershell,
V2
preview
release
which
came
out
I,
think
in
the
middle
of
the
holiday
season,
so
to
say,
or
just
a
few
days
before,
the
the
main
holiday
season
starting
and
then
waldek
is
going
to
talk
about
how
to
test
your
spfx
solution
respond
to
trottling
with
craft
developer
proxy.
So
we
did
have
a
Sebastian
lever
to
talk
about
the
craft
developer
proxy.
B
Is
development
module
we're
going
to
talk
about
that
module
where
it
is
and
what
does
it
contain
as
part
of
that
intro
as
well?
For
the
upcoming
three
weeks,
we
will
cover
actually
those
three
exercises
and
together
with
AC
within
the
call,
because
it's
really
cool
to
have
a
nice
Ace
dedicated
module
available
as
well.
B
Now,
let's
first
get
started
with
a
typical
set
of
slides.
First
of
all,
you
might
have
seen
this
slide
in
the
past.
We
used
to
have
two
different
YouTube
channels.
Now
we
are
consolidating
to
a
single
YouTube
channel,
where
we
have
all
of
the
latest
creators
and
latest
videos
related
on
Microsoft
365
available,
and
that
is
akms
M365
videos.
B
We
might
actually
change
some
of
those
again
etcies
at
some
point,
but
again
all
of
the
old
addresses
will
work
as
well,
so
it
doesn't
really
matter
which
address
you
use
to
or
get
our
us
to
call
Old
akms
addresses
will
be
redirected
properly
to
the
right
channel
as
well.
There
might
be
some
changes
of
the
name
at
some
point
as
well,
but
it
is
a
one,
centralized
location
for
all
of
the
Microsoft
365
platform
and
development
topic.
B
Well,
not
only
on
developer
topics
as
well,
because
there's
Microsoft
lists
and
there's
a
lot
of
other
stuff
in
that
channel
as
well.
We
do
have
a
lot
of
Open
Source
assets
available
for
you
to
take
advantage
in
multiple
GitHub
organizations,
but
as
it
might
be
a
bit
difficult
to
find
the
relevant
sample
for
you,
because
there
are
hundreds
and
thousands
of
samples
within
a
ketone.
We,
we
luckily
have
a
set
of
sample
galleries
for
you
and
the
primary
sample.
B
Gallery
is
the
akms
M365
samples
where
we
have
all
of
the
awesome
samples
available
from
the
different
GitHub
organizations
from
Microsoft
and
also
from
the
community,
so
we're
really
trying
to
surface
and
make
it
a
one,
centralized
location
to
find.
What
relevance
for
you
and
if
you're
wondering
that,
there's
too
many
URLs
to
remember.
B
Luckily,
there's
only
one
which
say
game
as
entry
65
community
and
that's
going
to
be
the
landing
page
for
Microsoft
365
and
Power
Platform
community
and
from
there
you'll
have
access
on
all
of
the
different
additional
locations
where
we
have
other
things
available.
Now
we
do
have
also
a
lot
of
quite
a
lot
of
different
developer.
Community
calls-
and
this
is
the
Tuesday
one,
which
is
happening
every
single
week.
B
The
Thursday
series
is
more
for
Community
demos,
and
that
is
a
key
point
for
all
of
the
people
in
this
call
as
well,
because
we
do
welcome
Community
demos.
So
we
would
love
to
get
you
volunteered
to
show
what
you
have
built.
So
if
you
have
built
a
cool
sample,
it
doesn't
have
to
be
open
sourced,
but
it
shouldn't
be
a
product
either.
So
something
what
you
have
built
something
hard
to
have
learned.
B
We
would
really
love
to
have
you
sign
up
for
doing
a
live
demo
within
this
community
course
and
depending
on
what
the
demo
or
the
solution
contains.
We'll
then
associate
that
demo
to
the
right
Community
call.
So
we
do
have
quite
a
few
of
those
goals
where
we
actually
take
Community
contributions
and
Community
demos
which
are
available.
B
So
please
sign
up
using
that
form
which
you
can
see
there
and
then,
as
part
of
that
form,
we're
asking
what
is
the
demo
all
about
and
we'll
ask
all
of
the
details,
and
then
that
basically
gives
us
the
insights
on
where
we're
going
to
schedule
that
in
our
pipeline
now
other
than
that,
you
can
contribute
in
GitHub
or
you
can
provide
feedback
with
a
super
important,
providing
feedback.
We
have
multiple
different
channels,
so
we
have
the
feedback
portals
we
have
the
Q
a
we
have.
B
B
Now
we
do
have
these
assets
available
for
you
to
get
started
on
on
the
micro
traces
for
development.
So,
first
of
all
sign
up
for
the
developer
program.
You
create
a
free,
E5,
developer
tenant
which
will
renew
automatically
in
every
single
90
days.
If
I
remember
correctly
the
timeline,
and
then
we
do
have
a
lot
of
lot
of
awesome
training
material
available
for
you
to
follow
up
on
learning.
How
do
you
extend
the
Microsoft
365
across
the
whole
stack
so
take
advantage
of
these
free
assets
within
your
work.
B
We
also
have
two
different
podcasts
available,
so
we
do
have
the
Microsoft
releases
for
developer
podcast
available
and
today
and
there
was
a
create
partner,
showcase
episode
released,
which
is
integrating
yes
soon
with
Microsoft
365
with
WPS,
and
that
was
with
chairman,
fake
and
ikobash,
where
they
talked
about
the
learnings
of
that
partner
in
the
creation
on
the
PMP
weekly,
which
is
happening.
Surprise.
B
Surprise
every
single
week,
unless
there's
a
holiday
break,
we
had
a
Albertina
Scott
from
Bliss
ticket
digital
and
we
talked
about
the
low
code
and
no
code,
and
what
does
the
fusion
development
actually
means
nowadays?
So
what
is
the
future?
And
is
there
a
partner
opportunities
with
that
as
well?
So
it's
a
really
nice
discussion
with
happy
on
that.
B
Now
on
the
sample
calories,
we
kind
of
mentioned
that
a
number
of
them
already.
We
also
always
want
to
promote
our
primary
Microsoft
365
unified
sample
Gallery.
We
do
have
now
1450
samples
from
that
gallery
from
Microsoft
and
from
community,
and
we
are
all
the
time
adding
new
new
content
available.
So
you
can
easily
follow
up
on
the
latest
and
greatest
samples,
and
there
are
really
great
ways
of
finding,
for
example,
samples
which
one
person
has
contributed.
So
there's
a
lot
of
a
lot
of
cool
stuff
available
there
as
a
then
find
a
sample.
B
A
Absolutely
thank
you
vessel.
Well,
friends.
If
you
are
amazed
by
those
samples,
you
may
be
thinking
where'd,
they
come
from
well
amazing
contributors
like
yourself
now
you
may
think.
I
do
have
amazing
samples.
I
want
to
share
I.
Just
don't
know
how
these
programs
sharing
is
caring,
provides
you
Hands-On
guidance
in
a
safe
space
opportunity.
That
means
that
you
can
join
members
of
the
community,
MVPs
Microsoft
employees
and
we're
going
to
work
together
to
accomplish
just
that.
So
you'll
join
a
session,
for
example,
and
we'll
do
a
pull
request
together.
A
So
you
walk
through
answer
any
and
all
questions
ask
any
and
all
questions
help
each
other.
These
sessions
are
not
recorded
as
they
are
safe
space
and
they
cover
a
plethora
of
topics.
We
have
our
Power
Platform
samples
contributor.
In
fact,
coming
up
today
we
have
our
general
first
time
contributor.
Coming
up
later
this
week
we
have
more
coming
up
next
week
in
January
and
we're
getting
more
scheduled
out
in
February,
so
there
is
no
cost
to
join.
It
is
absolutely
free,
safe
space,
great
time
to
collaborate,
opportunities
as
we're
getting
into
the
new
year.
A
B
To
you
excellent,
thank
you
David
on
that
one.
Now,
on
the
new
side,
it's
still
pretty
quiet,
so
we
haven't
actually
seen
that
many
rooms
within
this
week
or
the
previous
week.
But
last
week
we
announced
the
new
Microsoft
craft
developer
proxy
preview
version,
3
0.3,
with
a
support
for
all
apis,
and
this
is
really
cool,
so
it
you
don't
actually
have
to
just
mimic
or
use
the
craft
proxy
for
Microsoft
graph
apis.
B
You
can
actually
use
it,
for
example,
if
you're
hitting
a
SharePoint
apis
and
SharePoint
rest
apis
and
see
some
apis,
which
quite
often,
unfortunately
still
is
required
for
some
of
the
elements,
for
example
in
SharePoint
related
on
that.
However,
today
we
announced
a
public
preview
on
SharePoint
data
is
Microsoft
graph
API,
so
that
is
now
available
for
you
to
take
advantage.
That
was
just
announced
one
and
a
half
hours
ago,
you'll
find
it
from
the
Twitter
as
well,
and
this
is
from
akmsm365
Dev
blocks
and
that's
where
those
are
available.
On
the
Viva
block.
B
There
was
a
note
related
on
new
year,
new
rituals,
with
Microsoft
Viva
insights,
which
is
actually
Gathering.
Some
of
the
old
news
and
old
announcements
from
the
previous
months
related
on
2023
goals
for
individuals
other
than
that
we
did
not
have
new
news
in
the
in
the
blocks,
but
I'm
pretty
sure
that
next
time
there's
a
lot
new
to
cover.
Now,
let's
do
a
quick
feedback
recap
also
on
what's
the
team's
platform
updates
from
a
documentation,
perspective
and
sure
p
is
kind
of
covered
that
today.
C
Thank
you
for
yourself.
First,
we
wish
you
all
a
very
happy
new
year.
We
have
a
quick
update
today
with
published.con
frequently
asked
questions
in
collaboration
with
the
ecosystem.
Pms
to
address
top
partner
asks
and
help
improve
a
platform
adoption.
If
you
have
queries
that
you
seem
fit
to
be
covered
in
this
document,
please
do
let
us
know
through
the
feedback
feature,
so
this
is
what
we
had
for
today.
If
you
have
any
feedback
or
suggestion,
please,
post
on
EK
dot,
Ms
teams,
platform
feedback,
the
link
is
available
in
the
footer.
C
B
Excellent,
thank
you,
sir,
here
on
that
one
and
then
we'll
do
the
remote
picture.
So,
if
you're
willing,
if
you're
open
for
it,
you
can
enable
the
video
we'll
grab
a
gif
animation
out
of
this
and
share
it
in
social
media.
We're
not
going
to
take
too
much
time
in
here
again
we're
trying
to
get
the
50.
There
are
50
states
in
the
room,
let's
say
who's
the
fast
fastest
under
house
I'm,
not
gonna,
actually
enable
even
my
my
camera.
B
B
Let
me
put
the
recording
on
and
let's
do
some
hand
waving
everybody
to
welcome
2023
and
the
community
back
on
business
on
this
weekly
Community
course
awesome
to
have
you
hear
a
lot
of
familiar
faces
on
the
call,
excellent,
brilliant
and
taught
I
can
see
great
dancing
on
the
background.
Awesome
excellent,
we'll
craft
a
gif
animation
out
of
that
and
share
it
in
the
social
media.
Thank
you
for
that.
But
then
we'll
move
to
the
actual
stars
of
today
and
we're
pretty
much
on
the
schedule.
This
is
really
really
good.
B
D
D
What
that
means,
I
will
show
you
in
the
next
slide,
but
pretty
much.
We
have
two
different
modules
now
one
microsoft.graph
that
is
targeting
view,
one
endpoint
and
now
microsoft.graph
dot
beta
module,
that's
targeting
beta
endpoint.
This
is
something
that
we
thought
as
a
really
good
Improvement,
because
today,
like
it's
pretty
much
easy
to.
D
So
we
decided
to
split
the
SDK
into
two
so
to
be
less
error
prone
and
less
ambiguous
scripts,
because
now
we
have
the
beta
prefix
in
all
beta
commandlets.
The
other
change
is
that
we
are
supporting
more
of
scenarios,
so
we
are
now
putting
manage
identity,
client,
Secrets
credentials
and
environment
variables,
so
managing
identity
is
some
of
you
may
know
like
it's
a
common
challenge
when
writing
and
automating
the
things
you
need.
It's
a
common
challenge
to
manage
the
secrets,
credentials
and
all
of
that
and
like
have
everything
you
need
secure.
D
So
now
we
are
eliminating
the
need
to
manage
your
credentials
by
yourself
by
using
the
manage
identity,
because
now
Azure
resources,
we
can
get
access
tokens
from
Azure
resources
that
are
protected
by
Azure
active
directory,
so
more
secure
out
thin
areas
same
for
clients,
secret
credentials
because,
like
if
you
need
interactions
in
the
background,
you
don't
have
an
user
to
sign
in.
You
can
use
dial
client
secret
credentials
and
for
those
who
may
need
to
use
environment
variables
or
unique,
or
you
want
to.
D
You
can
now
set
your
variables,
pointing
the
client,
ID,
the
tenant
ID
and
ask
Powershell
SDK
to
use
these
environment
variables
to
authenticate
against
graph.
Another
Improvement
about
Alf
is
for
the
certificates
because
we
do
now
support
certificate
authentication,
but
before
V2,
so
in
V1
we
only
were
looking
at
the
machine
certificate
store.
But
now
we
included
the
current
user
certificate
store,
so
both
are
being
looked
by
the
V2
version,
and
if
we
have
like
the
same
certificating,
both
current
user
and
the
local
machine,
we
are
going
to
use
the
current
user.
D
One
and
the
other
chains
are
HTTP
2
support
when
the
API
supports
http
2.,
and
we
added
also
the
success
range
code,
support
So.
Now
everything
that
it's
200,
something
we
are
going
to
be
able
to
get
this,
even
though
the
API
is
saying,
for
example,
the
response
will
be
a
202,
but
actually
they
are
also
respond.
They
are
also
responding
with
like
201
200.
That's
not
a
niche
anymore,
because,
like
now,
we
supported
the
success
range
code.
D
So
just
you
simplify
what
I
told
you
about
different
modules,
so
in
V1
for
you
to
use
V1
and
beta
in
the
same
commandlet,
you
would
need
to
change
your
profile,
so
the
selected
profile
to
V1
to
use
what
was,
if
you
want
and
for
beta
for
the
things
that
are
in
beta
and
now
in
V2.
We
have
the
beta
prefix.
So,
as
you
can
see
in
the
V2
code
snippet
here
we
have
the
get
mg
Beta
Drive
activity,
so
this
beta
word
was
included
as
part
of
the
beta
module.
D
So
for
those
who
are
using
only
if
you
want
endpoints
nothing
had
changed
it.
Your
script
should
be
working
just
fine.
You
probably
don't
need
to
change
anything
for
those
who
are
rely
on
beta
either,
because
the
functionality
you
need
is
not
exposed
in
view
one
or
you
need
or
you're
trying
something
new
some
preview
apis.
You
just
need
to
go
and
just
add
this
little
word
beta
after
MD
and
you
should
be
fine.
D
The
new
all
scenarios
here
are
the
Snippets
just
for
you
to
have
a
quick
review
so
manage
identity.
We
have
now
a
dash
identity
parameter
here
for
environment
variables.
As
you
can
see
here
we
are
using
environment
variables
to
say
the
client
ID,
the
tenant,
ID,
the
client
secret
and
the
third
one
is
the
client
secret
one.
As
you
can
see,
Dash
client
Secrets,
the
initials
parameter
are
now
one
of
the
ways
you
can
authenticate
against
graph.
E
E
So
the
first
thing:
when
using
manage
identity,
we
support
essentially
two
kinds
of
identities
we
have
a
system
assigned
and
user
sign,
so
system
assigned
will
automatically
use
the
manage
identity
of
that
service
instance
that
you're
running
on
in
Azure,
so
like
in
this
case
I'm
using
Cloud
shell
Cloud,
shell
ships
with
its
own
identity.
So
in
V2,
all
you
need
to
do
is
in
your
Cloud,
shell
environment
just
run,
install
module,
Microsoft
graph,
allow
pre-release,
so
it'll
be
something
like
this,
and
this
will
install
the
preview
version
of
V1.
E
If
you
wanted
to
install
beta,
you
could
also
just
do
here,
dot
beta
and
that
should
install
it.
The
cool
thing
with
our
Azure
Cloud
shell
is
that
everything
is
persistent.
So,
even
if
you,
you
know
close
your
browser
and
open
it
again,
the
module
will
be
installed
so
to
use
the
system
assigned
identity,
I'll
just
call
connectmgraph.identity,
and
that
will
pick
the
access
token
from
that
environment
and
just
like
that,
I've
logged
in
and
in
this
case,
I'm
using
app
only
permissions.
E
So
there
are
some
default
permissions
like
the
identity
has
so
the
next
thing
is
you
know:
I
can
just
use
the
module
as
usual,
so
like
in
my
next
sample.
I'll,
essentially
just
you
know:
filter
users
in
my
tenant
with
our
city
specified
as
wrap
on
it.
So
in
this
case,
I'll
get
like
a
collection
back
of
Redmond
best
users
who
have
their
City
specified
as
red
one.
E
E
There
we
go
so
in
this
case
I'll
just
Loop
through
the
users
called
the
new
mg
group
member,
specify
the
group
ID
as
that
group
that
I
just
created
up
there
and
then
the
directory
object.
Id
is
the
ID
of
those
users
who
I
want
to
add
now
why
it's
a
directory
object
here.
It's
because
a
member
of
a
user
is
any
type
of
that
derives
from
an
errors
or
your
object.
So
you
know
that
can
be
a
user,
a
group
and
other
different
types,
so
I'll
just
Loop
through
and
just
like
that.
E
We've
added
user
store
groups,
so
I
can
confirm
this
by
calling
the
get
MGA
group
member
by
specifying
the
group
ideas
that
Redmond
group
that
I
just
created
and
just
like
that
I
can
see
that
all
the
IDS
that
I
added
available
as
members
of
this
group,
so
once
I'm
done
with
my
group
and
I,
can
add
other.
You
know
settings
for
this
group
Etc
and
you
can
even
convert
the
group
to
a
team
and
do
a
lot
more
sophisticated
work
from
using
the
module.
E
But
in
this
case
you
just
want
to
keep
it
simple.
So
I'm
done
with
my
group:
what
I'll
do
next
is
just
go
and
delete
it
and
one
cool
thing.
You
can
also
call
the
module
with
the
dash
debug
to
see
what's
happening
and
just
like
that,
we
can
see
that
we
sent
a
request
to
that
URL
and
those
were
the
headers,
and
that
was
the
response
that
we
got
back
and
the
group
has
been
deleted
yeah.
E
Together
with
this
there's
a
whole
lot
more
improvements
that
we've
made
you
can
find
those
in
our
migration
guide
here.
So
we
talk
about
like
you
know.
What
are
the
new
features
and
improvements
that
we've
added,
how
you
can
use
them
when
providing
Snippets
as
to
how
they
can
be
used?
Etc,
so
I'd
urge
you
to
just
go
to
this
upgrade
guide
and
see,
what's
new
play
with
them
and
give
us
feedback.
D
And
and
just
to
add,
on
top
of
what
Peter
was
saying,
we
are
looking
for
feedback,
so
please
feel
free
to
raise
issues
or
to
go
to
the
discussion
topic.
We
have
in
the
Powershell
GitHub
repo
that
we
are
discussing
pretty
much,
why
we
separate
the
SDK
and
why
we
opt
per
per
different
command
left
names.
So
please
go
put
your
input
there.
We
want
to
hear
from
you.
D
What
do
you
think
and
we
pretty
much
want
to
also
tell
you
and
let
you
know
that
we
are
working
in
a
migration
too,
to
help
you
migrate,
your
scripts
from
V1
to
V2,
so
this
will
be
available
with
the
ga
version.
So
it's
a
streaming
progress,
but
this
is
also
something
that
we
are
working
on
and
also
want
support.
B
F
F
Window
with
the
SharePoint
workbench
and
vs
code
in
the
background-
yes,
yep
actually
see
them
all
right
can
I
have
a
quick
raise
of
hands.
Who
has
never
had
a
single
API
error
when
calling
graph,
SharePoint
API
anything
counts,
throttling
500
errors,
Fabian
had
no
errors,
AC,
no
errors,
I
believe
you
guys
have
never
been
building
anything.
F
I
see
you
there
excellent
cool,
so
basically,
when
you
build
apps
right
that
connect
to
Microsoft
graph
or
other
other
apis
once
in
a
while,
you
will
run
into
errors
like
rattling
500
errors,
and
these
things
are
really
hard
to
deal
with.
Why?
Because
there
are,
they
are
ephemeral
like
they
appear
and
then
they're
gone
and
it's
impossible
for
you
to
reprogram
right.
At
least
it
wasn't
possible
until
now
right,
because
now
we
have
the
Microsoft
graph
developer
proxy.
F
That
allows
you
to
simulate
these
errors,
both
on
Microsoft
graph,
but
also
on
any
other
API
that
you
might
use,
and
in
this
example,
I'm
gonna
actually
show
you
both
right.
So
right
now,
I'm
going
to
walk
you
through
a
simple
app.
What
I
write
really
a
weapon
that
you
can
see
now
on
a
screen
that
shows
the
title
of
the
current
site
using
purple
and
rest
API
and
then
uses
graph
me
endpoint
to
show
info
about
the
user.
F
That
is
currently
authenticated
right
and
how
would
that
work
and
how
would
the
web
part
behave
like
if
it
ran
into
throttling
or
other
errors?
Okay,
so
on
the
screen
you
see
the
web.
That
shows
two
things:
the
title
of
the
site
and
info
about
me.
The
way
it's
built
is
really
simple:
it
doesn't
get
any
easier
than
that
right.
So
in
SharePoint
framework,
161
I
can
use
the
Microsoft
graph,
JavaScript
SDK
V3
and
basically
from
there
I
get
a
client
I.
Don't
need
to
do
any
off.
F
I
get
all
of
that
already
for
free
from
spfx
and
I.
Do
a
simple
call
to
endpoint
me
to
get
info
about
me
and
I
showed
that
on
a
page.
So
this
is
this
block
which
you
see
here,
then
on
top
I
show
the
title
of
the
site
and
I
do
that
by
calling
the
SharePoint
rest
endpoint
in
here,
I
call
web
and
from
that
I
get
a
title
and
I
show
this
on
a
page
like
it
all
works.
F
It
doesn't
get
any
easier
than
that
right,
so
it
works
right,
like
you
can
shoot
that
that
production
right,
what
would
be?
How
would
the
web
part
work
like
if
it
would
run
into
roughly?
So
that's
that's
that.
Let
me
start
the
the
Microsoft
graph
developer,
Roxy
and
I
want
to
only
test
the
four
two
nines
too
many
errors.
F
Let
me
start
it
and
then
it's
available
now
and
then
let
me
start
new
window
of
chrome
to
which
I
can
attach
a
proxy
right,
because
if
I
were
to
do
that
with
Edge,
I
would
need
to
enable
it
on
my
OS,
which
would
mean
you,
wouldn't
be
able
to
see
anything
because
teams
also
needs
graph
right,
so
they
wouldn't
make
a
great
demo.
Let
me
see,
let
me
see,
let
me
see
where
is
my
window?
Here's
my
window.
Let
me
grab
the
URL.
Let
me
paste
it
in
Chrome
three,
two
one.
F
We
should
be
seeing
workbench.
We
actually
see
anything
and
we
won't
see
anything.
Why?
Because
we
are
already
intercepting
all
all
requests
and
if
I
refresh
that,
maybe
you
will
see
it
again-
maybe
not.
Let
me
see
that
right,
so
here
are
already
errors
that
we
intercept
and
we
simulate
four
to
nine,
so
the
workbench
couldn't
load
well.
That
doesn't
really
help
us
right.
F
So
let
me
adjust
the
proxy
a
little
so
that
it
will
only
stimulate
the
error
on
the
API
that
that
we
want
to
use
and
we'll
we
will
get
back
to
how
we
want
to
like
what
ideas
do
we
have
to
make
it
more
or
easier
for
you
to
use?
So
let
me
stop
it
here.
Let
me
get
back
to
the
config
and
in
here
we
have
the
list
of
URLs
that
we
Monitor-
and
here
you
can
see,
we
monitor
all
SharePoint
calls
well,
some
of
them
are
needed
for
the
workbench
to
work.
F
So
in
this
case,
let
me
just
trim
that
down
to
web
select
right
so
that
that
would
be.
That
is
basically
the
call
that
we
do
in
our
code
right
and
with
that,
let
me
restart
the
epoxy.
I
mean
I
run
a
version
on
which
I
Dev,
which
is
why
the
config
does
not
reload,
but
if
you
grab
the
version
that
we
already
shipped,
you
will
have
a
hot
reload.
So
if
you
change
anything
about
it,
you
will
need
to
restart
or
stop
and
restart.
Okay,
all
right.
So
we're
back.
F
Let
me
reload
the
workbench.
The
get
client
components
comes
through.
That's
perfectly
fine.
We
have
another
four
to
nine,
but
that
is
irrelevant
for
now
and
now,
let's
add
the
web
part
to
our
page
okay.
So
this
is
the
web
part
that
we
have
three
two
one.
Are
we
getting
four
two
nines
perfect,
so
we're
getting
a
four
to
nine
on
me
and
perfectly
fine
right.
So
this
came
through
eventually-
and
here
we
can
see
in
the
Microsoft
graph
developer
proxy-
that
there
was
a
request
right.
F
We
failed
it
with
a
429,
but
the
Microsoft
graph,
JavaScript
SDK
handles
four
two
nines
for
you,
so
in
other
words,
in
our
code,
if
we
get
back
to
here,
this
is
the
only
thing
like
we
need
to
do
anything
more.
This
just
works
because
that
SDK
handles
four
to
Nines
for
us,
so
we
need
to
do
anything
else.
What
about
disco
right?
So
what
about
the
SP
HTTP
client
that
we
use
to
get
the
title
of
the
site
from
the
rest,
API
right
that
came
through
and
I
really
want
to
see
this
fell.
F
So
let
me
reload
again,
and
we
will
stay
here
until
it
will
fall
there.
We
go
it
failed.
It
failed.
We
can
see
here
so
we've
got
our
429
on
retrieving
the
title
of
the
site,
undefined
the
code
fail
and
we
will
not
recover.
Why?
Because
SP
HTTP
I
end
doesn't
handle
49s
on
or
any
other
errors
right.
It
wraps
Fetch
with
auth,
so
that
you
don't
need
to
authenticate
but
other
than
that
you're
on
your
own.
F
F
Support
for
four
four
two
nines
to
this:
well,
your
fetch
code
would
need
to
become
something
like
this
right
or
where
you
add
a
sleep
so
that
you
can
back
off
for
the
period
of
time
communicated
by
the
retry
after
a
header,
and
then
you
need
to
like
try
again
until
the
call
will
come
through
right.
So
suddenly,
your
call
now
becomes
a
bigger
call
and
you
need
to
kind
of
centralize
it
think
around
it
and
so
forth,
and
so
on,
right
or
there's
another
way.
F
You
can
also
use
PNP
JS,
which
is
an
SDK
that
calls
an
API
and
it
can
call
graph
it
can
call
Spurs
system
and
so
forth
and
so
on,
and
it
handles
four
two
nines
for
you.
So
you
don't
need
to
do
anything.
So
let
me
quickly
uncomment
what
I
need
and
comment
what
I
don't
need.
I've
got
this
call
using
PNP
jstd,
exactly
the
same
call
right.
So
here
is
web
Select
Title.
So
let
me
do
that.
Let
me
save
it
three
two
one
three
two
one
is
going
to
rebuild
recompile
Reserve.
F
F
Will
the
request
come
through?
Well,
it
does
come
through,
but
there's
one
thing
that
is
odd
right.
So
here
we've
got
not
a
dollar
sign,
but
a
dollar
is
Escape
right.
So
it's
a
percent,
24
meaning
proxy
were
always
pass
it
through
right
because
we've
adjusted
that.
So
let
me
quickly
get
back,
adjust
proxies
config
and
also
make
it
okay.
I
want
to
do
two
things.
I
want
to
do
this
and
I
want
to
do
percent
24
save
it.
Let
me
quickly
stop
restart
three
two
one
we
are
in
back
in
Chrome.
F
Let
me
see,
and
now
we
want
to
see
the
call
to
the
title
of
the
site
fail.
Okay,
so
it
failed
here
there
there
you
go,
it
failed,
but
there
you
go.
So
we
have
it
initially
because
again,
as
I
said,
PNP
JS
handles
four
two
nines
for
you,
so
that
and
you
don't
need
to
do
anything
with
that
right.
So
in
your
code,
all
you
do.
Is
you
get
a
title
of
a
site
and
there
is
no
handling
errors
like,
like?
F
All
of
that
is
already
available
to
you
for
free
right,
and
here
you
can
see
the
first
call
failed
right.
We
get
a
four
to
nine
and
that's
coming
from
a
proxy
right
like
we
modeled
this
error,
but
then
there's
an
article
and
that
comes
through
and,
as
you
can
see
here,
we
get
the
title
of
the
site.
So
the
cool
thing
is
right
with
that.
You
have
now
the
ability
to
test
all
of
that,
something
that
you
couldn't
do
in
the
past.
F
Unless,
like
you,
would
spin
up
your
own
mock
service
with
your
own
dummy
data
and
all
of
that
change
your
code
to
call
one
endpoint
versus
the
other.
Now
you
don't
need
to
change
anything
about
your
code.
You
can
keep
your
code
as
is
and
simulate
how
it
will
work
in
production
when
it's
under
heavy
load.
When
it's
used
by
thousands
of
folks
in
production,
you
can.
You
can
check
that
already
on
your
tenant
of
one,
that
everything
will
be
fine
when
you
ship
your
code
production.
B
B
Exactly
now
we're
going
to
talk
about
a
bit
about
the
new
introduction
of
Viva
connection,
Ace
module.
So
let's
start
with
that
announcement
so
stunning,
each
day
and
we'll
have
a
plug
post
coming
up.
Actually,
tomorrow
we
have
a
new
Microsoft
level,
learning
path
or
learning
module,
which
is
focusing
on
the
ace
development
and
this
basically
a
building.
B
A
SharePoint
framework
powered
adaptive
card,
extensions
for
Microsoft,
Viva,
home
and
Viva
connection
and
I'll
talk
about
a
bit
about
what
is
Microsoft,
Survivor
home
and
viewer
Connection
in
a
second,
because
Weaver
home
is
going
to
be
starting
to
roll
out
quite
soon
worldwide.
So
that
is
a
great
opportunity
of
building
extensibility
for
Microsoft
365
and
then
then
from
those
Aces
you're
actually
redirected,
for
example,
the
Minecraft
themes,
applications
or
any
other
sources.
But
in
this
particular
case
the
learn.
Module
really
focuses
on
Ace
development.
So
how
do
we
build
those
ACS?
B
What
are
the
different
options
on
this
adapter
card
extensions?
What
is
the
relationship
between
a
SharePoint
framework
component
and
SharePoint
framework
code
and
adaptive
card
technology?
Sharepoint
framework
is
the
basically
the
orchestrator
behind
of
the
scenes
for
Asus
and
and
hitting
the
API
and
then
feeding
the
API
information
for
adaptive
cards,
which
are
then
rendering
the
uxl
as
part
of
this
module.
There
is
thank
you
AC
for
correcting.
B
In
this
event,
module
is
part
of
this
module
and
there's
three
distinct
exercises
from
getting
started
to
more
complex
scenarios,
and
also
this
includes
the
usage
of
media
selection,
location
capabilities
in
AC.
So
we
kind
of
cover
the
latest
and
greatest
on
the
as
development
as
well.
It's
both
available
in
both
written
and
in
video
format.
So
it's
up
to
how
do
you
actually
follow
up
on
the
guidance
so
and
we'll
release?
B
So
again,
it's
the
best,
akm
AK,
Ms
forward,
slash
Vivo
forward,
slash
Ace
forward,
slash
learn
is
the
location
how
to
get
there
now.
This
is
all
based
on
SharePoint
framework
development.
Sharepoint
framework
was
originally
released
already
in
2017,
and
it's
not
just
about
SharePoint.
You
can
actually
build
for
Microsoft
teams,
Microsoft
Viva
and
nowadays
also
for
Outlook
on
Microsoft
365
apps,
so
the
same
piece
of
code
actually
can
be
running
across
all
of
the
base.
B
So
there's
a
bit
of
a
difference
on
the
Viva
home
and
Viva
connection,
there's
going
to
be
more
information
on
the
Viva
Home
rollout
and
capabilities
and
and
options
in
the
future,
but,
as
you
can
see
in
the
Viva
Home
on
the
left
side
or
in
the
mobile
views,
they
are
ace
cards.
They
are
Ace
components,
their
adaptive
card
components
which
are
being
rendered
in
that
kind
of
a
card
format,
and
this
learning
path
really
focuses
on
okay.
How?
What
are
these
cards?
How
can
I
modify
find
them
how
they
are
being
exposed?
B
What
are
the
different
options
and
how
would
I
use
them,
for
example,
location,
information
and
media
upload
information
in
a
mobile
device
view,
because
these
are
really
designed
for
mobile
first
experience.
They
of
course,
work
really
well
in
a
desktop,
but
the
main
target
here
is
the
the
mobile
first
I'm,
for
example,
personally
using
Viva
home
and
Viva
cards
on
a
daily
basis
within
my
mobile.
B
It
stays
this
way
to
access
information
and
some
of
the
services,
but
to
be
able
to
understand
how
do
we
get
started
on
building
this
Asus
I
will
actually
turn
the
the
audience
and
turn
the
microphone
to
enter
kernels
who's
going
to
do
the
first
exercise
on
this
learning
module
and
we're
going
to
continue
this
exercise
in
upcoming
weeks
as
well
and
AC.
We
can
see
the
screen.
Thank
you.
Awesome.
G
Thanks
vessel
yeah,
so
I
want
to
just
run
through
the
first
demo
for
this,
but
that
we
have
in
this
or
the
first
lab
exercise,
slash
demo
that
we
have
in
this
module
before
I
go
in
there,
though
I
just
want
to
talk
a
little
bit
about
the
module
itself,
just
to
add
on
a
little
bit
about
what
vesa
just
talked
about.
This
is
a
new
Microsoft
learning
module,
which
consists
of
like
lectures
and
Hands-On
lab
exercises.
G
G
That's
exactly
why
I
don't
do
design
and
stick
with
the
development
stuff,
so
I'm
a
Microsoft
MVP,
specifically
around
office
Development
I've
been
doing
SharePoint
for
actually
this
year,
it's
20
years,
so
I
don't
recommend
that,
but
doing
anything
for
20
some
years
is
a
long
time
anyway.
So
let's
go
into
the
module.
G
So
what
this
is?
This
module
is
called
creating
adaptive
card
extensions
with
the
SharePoint
framework,
got
all
my
keywords
in
there
there's
a
link
to
where
you
can
find
it
as
well.
The
link
the
vest
I
just
showed
a
second
ago
is
also
there.
That
is
also
on
the
slides.
That's
also
been
shared
one
thing
too
just
to
highlight
here.
G
If
you
want
to
see
the
the
videos
for
this,
if
you
want
to
see
like
the
download
for
the
code
and
samples
for
this,
all
this
stuff
is
available
right
now
you
can
get
to
it.
The
videos
haven't
been
like
made
public
or
publicized
or
anything
like
that,
but
they're
all
still
there
they
are
they're
all
still
there
they're
all
publicly
available,
they're,
just
not
like
index.
So,
if
you
know
YouTube
it's
basically
all
the
videos
are
there,
but
they're,
just
all
listed
as
unlisted
right
now,
until
they're
kind
of
released
out.
G
If
you
go
to
the
intro
section
of
this
module
that
I'm
linked
to
right
here,
you'll
be
able
to
see
a
link
at
the
bottom
of
the
intro
module.
One
points
to
a
GitHub
repo
that
contains
the
slides
that
go
along
with
the
module
I'm
not
going
through
those,
and
then
it
also
contains
I'm
not
going
through
those
in
this
in
this
demo
today,
and
it
also
has
a
link
to
the
screencast.
That's
on
YouTube,
that
consists
of
all
of
the
parts
of
this
module.
G
If
you
want
to
do
that
stuff,
all
right,
I'm
going
to
get
out
of
PowerPoint,
because
we're
going
to
do
some
real
work
here.
Let
me
kind
of
first
show
you
what
this
thing
does
and
it's
very
simple
example
keep
in
mind.
This
is
a
demo
it's
made
for
people
trying
to
learn
how
this
stuff
works.
So
let
me
go
ahead
and
run
this
thing.
First,
all
this
is
is
a
adaptive
card
extension
that
demonstrates
how
to
read
and
write
to
a
SharePoint
list
ignore
all
the
yellow
stuff.
Those
are
just
warnings.
G
G
G
So
let
me
go
back
over
to
my
list
I'm
going
to
go
to
my
Ace
data
list,
which
is
going
to
contain
just
like
everybody
else:
I
store
all
the
movies
that
I
watch
in
a
SharePoint
list.
No,
not
really
that's
pretty
lame,
but
it's
mismix
for
a
more
interesting
demo.
So
you
can
see
what
our
family
Christmas
movies
are
that
we've
been
watching
over
the
the
break
recently.
G
So
I
will
paste
that
in
and
save
my
changes
and
then
I'll
come
over
here
and
I
will
flip
this
from
my
edit
mode
over
to
the
display
mode.
So
I
can
actually
see
the
content.
I
will
click
on
the
the
card
itself
and
it'll
show
me
a
list
of
the
movies
that
we've
been
watching
as
a
family,
so
Inception
Interstellar,
Dead,
Poet,
Society,
Die,
Hard,
good
Christmas
movie
and
last
night
we
watched
the
Batman
from
last
year
so
anyway.
G
So
let's
go
back
the
movie
that's
on
our
list
tonight.
Is
that
we'll
add
in
just
a
minute?
Actually
we're
going
to
add
it
right
now
so
I
want
to
add
an
item.
I
can
go
ahead
and
I
can
click
on
add
an
item.
So
I
can
go
add
an
item.
So
let
me
go
grab
the
movie,
that's
on
deck.
For
tonight
you
just
copy
and
paste
because,
let's
just
do
we'll
type
this
in
and
we
are
watching
Fight
Club,
because
my
daughter
is
on
a
school
trip
out
of
town.
G
So
she
doesn't
so
we
don't
have
to
subject
her
to
this
or
expose
her
I
guess
to
it
and
there
we
go
a
couple:
more
movies,
Sixth,
Sense,
National,
vacation
and
Fight
Club
got
added
I
come
over
to
my
list
and
I.
Look
at
the
ace
data
and
I
can
see
the
item
that
we
just
added
here
for
Fight
Club,
so
cool.
G
How
does
all
this
stuff
work
all
right
so
now
I'm
going
to
come
back
over
here
to
let's
go
ahead
and
close
this
out,
and
let's
take
a
look
at
the
code
for
this
now
that
you've
seen
how
this
works
so
again,
if
you're
not
familiar
with
Aces.
Just
really
briefly,
when
you
click,
this
is
the
card
view
that
you
get
initially
and
then
all
these
things
that
pop
up
are
called
quick
views.
G
If
you
click
on
the
card
view,
you
have
the
option
here
to
display
to
do
something
and
in
my
case
here
I'm
displaying
a
quick
view,
which
is
this
kind
of
a
display
view
that
I'm
just
created
a
carousel
to
cycle
through
the
items.
I
got
back
from
my
SharePoint
list
and
then
the
button
add
item
was
going
to
go
through
and
open
up
a
different,
quick
view
that
I
want
to
use.
So
if
I
come
over
here
and
look
at
the
code,
let's
see
how
this
is
all
set
up
here.
G
Where's
my
code
right
here.
So
everything
kind
of
centers
around
in
an
Adaptive
card
extension
or
an
ace
everything
centers
around
like
like
a
center
of
gravity
right
and
that
center
of
gravity
is
the
adaptivecard
extension.ts
file.
That's
going
to
be
in
your
project
now.
This
file
here
contains
a
couple
things
that
are
that
are
interesting,
that
you
should
pay
attention
to.
So
the
only
things
that
I
think
are
really
like
that
that
are
really
important
to
pay
attention
to
is
that
you've
got
a
you've,
got
an
interface
for
properties.
G
G
This
is
basically
the
same
thing
as
the
state
and
what
the
state
is
is.
This
is
going
to
be
a
way
for
you
to
store
name
value
pairs
for
your
component
that
are
accessible
everywhere
throughout
the
component.
That
includes
in
the
card
views
and
in
the
quick
view,
and
whenever
you
change
something
in
the
state,
it's
going
to
tell
the
rendering
engine
to
re-render
the
card
all
client
side.
Now
the
next
section
is
kind
of
important
here
is
a
list
of
the
different
IDs.
G
I
can
put
whatever
I
want
in
here
to
make
this
work
like
I
mean
I
could
even
just
make
this
literally
just
make
it
whatever
I
want
without
any
proper
spelling
doesn't
matter,
but
we're
not
going
to
test
it.
So
just
trust
me
on
that
one
then.
The
next
thing
I
have
to
do
is
inside
of
the
on
a
knit.
I
need
to
use
these
things.
These
things
called
Navigators.
These
view
Navigators.
Essentially,
these
are
just
like
arrays
and
I
have
to
go
through
and
tell
the
Adaptive
card
extension
rendering
engine
hey.
G
These
are
things
that
you
can
use
that
we
can
refer
to
and
we
refer
to
them
based
on
an
ID,
and
then
we
give
it
an
object.
That's
going
to
get
instantiated
when
the
view
is
activated,
and
then
the
last
thing
I'm
doing
in
my
in
my
initialization
is
I'm
going
to
go
load
all
of
my
data
and
this
code
is
not
how
I
would
write
stuff
in
a
production
thing.
So
don't
judge
me
on
my
code.
G
This
is
for
educational
purposes,
so
I
I
would
only
call
set
State
once
and
set
the
properties
on
both
I'm.
Just
trying
to
be
explicit
on
what
we're
changing
here
in
this
case,
I'm
grabbing
the
title
of
the
list,
that's
selected
and
the
items
from
the
list
provided
I
have
a
list
ID,
that's
defined
and
I'm
setting
those
values.
That's
how
I'm
going
to
be
initializing,
my
my
component
on
the
page.
Finally,
the
last
thing-
that's
interesting
here
is
my
render
card.
The
other
thing,
that's
interesting.
G
What
that's
going
to
do
is
simply
tell
the
ace
engine
to
which
card
I
wanted
to
display
for
my
adaptive
card
extension
or
for
my
my
Ace
and
that's
where
I'm
passing
in
the
ID.
Finally,
the
last
thing
I'm
doing
here
is
in
this
in
this
class.
This
is
from
the
property,
pane
or
I'm
using
this
in
the
poverty
pane,
I'm,
saying
hey
whatever
a
specific
field
called
our
property
called
list,
ID
changes
and
provided
it
it
has
changed
with
my
new
value.
G
All
value
check,
then
I
want
to
do
the
same
thing.
I
do
in
the
initialization.
That's
why
I
want
to
go.
Get
some
data,
so
I'm
just
telling
you
to
go
back
and
do
that
otherwise
cleared
out.
There's
nothing
to
see
here
all
right
so
now
the
next
piece
that's
going
to
get
rendered,
then,
is
that
when
this
thing
gets
added
to
the
page
is
my
card
view.
G
So,
if
I
go
look
at
my
card
view,
it's
defined
in
my
car
view.ts
file,
this
is
going
to
get
instantiated
because
I
had
a
view
navigator
that
was
set
my
card
view,
Navigator
had
an
ID
and
something
added
to
it
by
its
ID
and
I
passed
in
this
an
instance
of
this
class.
So
when
my
my
center
of
gravity
class
returned
back
in
the
render
method,
the
card
view
ID
that's
how
this
one's
getting
registered.
This
guy's
only
got
three
things
that
are
interesting.
G
He's
got
what
happens
when
I
click
the
card
itself,
not
a
button
on
the
card,
but
the
card
itself
well,
I
want
to
show
a
quick
view
which
one
this
one
right,
the
one
that
we
exported
a
little
bit
earlier.
Okay!
Well,
do
you
want?
What
do
you
want
to
put
on
the
car?
What
buttons
do
you
want
to
put
on
it?
G
Well,
in
this
case,
here,
I
can
pass
back
a
button,
two
buttons
or
no
buttons,
and
in
this
case
here,
I'm
saying
well,
if
there's
no
list
ID
to
find
well
I
I
can't
I
can't
do
anything
because
I'm
not
working
with
the
list,
so
I,
don't
post
that
I
post
back,
nothing.
Otherwise,
I'm
going
to
add
my
add
item
button
that
when
I
click
on
it,
it's
going
to
launch
a
quick
view
which
one
this
one
and
then
finally,
my
data
method.
G
What
is
that
guy
going
to
do
my
data
method
is
going
to
display
the
is
simply
going
to
return
back
an
object
that
is
going
to
get
meshed
with
the
card
View,
and
these
are
some
well-known
properties
on
the
card
view
that
I
can
that
I
can
get
rendered
out
now.
The
interesting
thing,
though,
with
this
comes
in
my
last
few
minutes
I
have
here,
is
to
look
at
my
my
quick
view.
G
So
the
first
quick
view
is
when
I
clicked
on
the
card
and
I
had
that
thing
pop
up
off
to
the
right.
That
was
going
to
show
me
a
list
of
all
of
my
my
Carousel
list
of
all
of
my
items.
So
how
does
that
work?
Well,
if
I
come
over
here
and
look
at
my
quick
view,
what
I'm
doing
here
is
I'm
returning.
My
data
I
have
the
same
kind
of
setup
again
so
I
have
my
data.
G
I
have
my
template,
which
is
going
to
Define
what
is
where's
the
the
Adaptive
card,
where's,
the
Json
that
defines
the
Adaptive
card
and
I'm
saying
it's
right
there.
So
you
can
see
that
in
the
project,
we're
not
going
to
go.
Look
at
Json
right
now,
but
that
car
that
Json
is
defining
the
structure
for
my
card
and
it
has
little
callouts
or
placeholders
for
where
I
want
to
inject
data
elements
to
it.
What
data
elements?
Well
the
ones
I'm
returning
back
in
my
data
method
here,
so
my
data
method
or
my
data
accessor
method.
G
What
I'm
doing
here
is
I'm
passing
back
all
of
the
items
that
I
get
back
from
the
SharePoint
list.
Item
and
I'm
also
passing
back
two
properties
here.
One
called
previous
enabled
one
called
Next
enabled
because
those
are
my
two
little
toggles
I
have
on
either
side
of
the
item
and,
if
I'm
at
the
beginning
of
the
array,
I
don't
want
to
have
a
previous.
If
I'm
at
the
end
of
the
array,
I
don't
want
to
have
it
next
and
I
know.
G
I
could
put
some
like
kind
of
loop
around
kind
of
a
thing
but
I'm
trying
to
keep
it
simple,
and
it's
a
demo
so
that
here
I'm
just
checking
to
see
am
I
on.
The
current
item
is
the
very
first
item
in
the
list.
Is
that
the
one
that
I'm
on
or
am
I
on
the
very
last
item
of
the
list?
And
that's
just
going
to
be
setting
those
two
properties
and
and
my
Json
for
the
Adaptive
card?
That's
got
a
visibility
property
sent
to
true
or
false.
G
It's
going
to
Define
if
something's
going
to
show
up
or
not
the
next
thing
that
I'm
going
to
do
here.
So
when
I
go
and
then
the
other
thing
that's
interesting
about
this
I
will
show
you
one
piece
to
this
I'm
going
to
lie
a
little
bit
here.
Is
that
my
buttons
that
I'm
using
to
display
stuff
so
my
previous
button
that
has
this
you
know
the
Chevrons,
pointing
to
the
left
side
versus
the
chevron's
point
to
the
right
side?
G
I've
got
a
selected
action
here
that
says
that
my
type
is
a
submit
and
my
ID
is
going
to
be
an
integer.
So
in
this
case
here
in
previous
I
want
to
go
back
one
so
negative
one,
whereas
I'm
going
to
use
on
the
Plus
on
the
when
I
go
next,
I
want
to
go
or
next
I
want
to
go
plus
one.
So
what
I'm
doing
is
inside
when
someone
clicks
one
of
those
buttons
that's
going
to
trigger
my
on
action,
I'm
going
to
check
and
see.
G
Is
it
a
submit
and
if
it
isn't
then
get
out
of
here,
otherwise
go
get
the
current
index
that
we're
on
and
then
just
take
that
index
and
increment
it
by
whatever
the
value
of
the
ID
is
and
I
might
be,
incrementing
it
by
negative
one
to
go
back
in
the
index
to
show
me
which
one's
there.
So
what
does
that?
Do
that's
going
to
go
back
and
grab
change
the
index?
That's
going
to
cause
a
re-rendering,
that's
going
to
change
the
item.
G
That's
going
to
be
displayed
inside
of
my
quick
view,
but
then,
last
but
not
least,
what
happens
when
I
click?
The
add
item
button?
Well,
that's
going
to
launch
the
quick
view
called
new
item,
quick
view
and
what
this
guy
does
he's
got
his
Json
set
up
where
I've
just
got
title
and
description
set
up
and
then
the
whole
submit
Button
as
well
set
up
if
I
look
at
the
new
item,
quick
view
for
this
one,
this
guy
works
basically
the
same
way,
but
what's
interesting
about
him,
is
in
his
on
action.
G
He's
checking
to
do
if
the
action
is
a
submit
action
and
if
it
is,
then
I
want
to
go.
Save
the
item
so
the
way
I'm
going
to
save
the
item
is:
there's
an
asynchronous
method
and
because
the
on
action
is
not
sync,
it's
not
asynchronous.
It's
returning
a
void.
So
you
can't
just
do
a
special
async
on
here
and
nobody
wants
to
play
with
promises.
So
what
I
ended
up
doing
was
I
just
wrapped.
G
It
up
in
an
iffy
and
so
I
made
that
iffy
asynchronous,
and
so
that's
how
I'm
doing
an
asynchronous
thing
inside
of
asynchronous
statement
as
synchronous
as
JavaScript
can
really
be,
and
so
here
I'm
saying
go,
add
an
item
which
is
coming
from
some
service
that
I
created
here.
This
is
not
a
demo
on
working
with
the
SharePoint
rest
API.
So
that's
all
that
that
service
contains
all
that
code
on
reading
and
writing
to
the
list.
G
So
here
I'm
going
to
pass
back
things
like
the
contacts,
the
list
ID
and
then
the
properties
for
the
item
I'm
going
to
save
and
then
once
I've
saved
the
item.
Well,
then,
let's
go
back
and
let's
go
get
all
those
items
and
refresh
our
array
so
that
now
I
want
to
go
back
and
click
on
the
card
view.
Again,
it's
going
to
show
me
those
items
being
displayed
and
then
finally
I
want
to
remove
it
from
the
quick
view.
In
this
case.
G
This
is
a
cool
thing
about
these
Navigators
is
we
have
a
way
to
like
push
and
pop
stuff
off
the
stack
in
this
case
I'm
popping
it
off
the
stack.
Well,
there
was,
and
since
there
was
nothing
else
on
The
View
stack
for
my
quick
view,
popping
that's
going
to
basically
close
the
quick
view,
but
I
could
have
just
as
easily
said
close
right
here,
and
this
would
have
closed
the
quick
view
as
well
and
had
the
same
effect
in
this
case.
However,
you're
going
to
see
in
the
next
two
weeks.
G
One
of
the
NASA
open
apis
to
show
images
from
a
Mars
Rover
and
then
the
last
demo
is
much
more
involved
on
working
with
the
Viva
connections,
actions
for
showing
and
getting
locations
using
the
Bing
Maps
control,
that's
available
to
us.
So
if
you're
interested
seeing
those
join
me
again
same
time
same
place
next
week
or
same
time
same
place
in
two
weeks.
So
that's
it!
That's.
B
All
I
guess
yep.
Thank
you.
I
say
there's
nothing
unfortunate
for
you
to
actually
do
the
Demos
in
this
call
in
upcoming
weeks.
Just
to
correct
on
that
now.
Thank
you,
Melissa.
Thank
you,
Peter.
Thank
you.
Walek.
Thank
you,
AC
for
the
demos
today,
a
bit
busy
call
we're
just
about
to
Running
Out
of
Time.
The
recording
will
be
available
in
24
hours
at
the
Microsoft
365
Community
YouTube
channel.
Take
Ms
M365
Community
videos
subscribe
today,
so
you
will
know
whenever
the
videos
there's
new
are
released.
B
We
do
release
new
video
at
least
one
new
video
every
single
business
day.
Typically
there's
multiple
ones
in
every
single
day,
which
is
pretty
cool
new
content
on
the
Microsoft
365
coming
up
all
the
time.
The
next
Community
called
platform
Community
call
happens
on
January
17th
at
8am,
Pacific
time
so
again,
Tuesday
next
week,
all
of
the
community
calls
at
akms
and
community
and
calls.
But
thank
you
for
this
one
thanks
everybody
for
joining.
Thank
you
for
the
presenters.