►
Description
Viva Connections & SharePoint community call on March 10. Demos - My Emails Viva Connections Adaptive Card Extension, Getting started with Microsoft Graph Toolkit and SharePoint Framework, and Using Microsoft Graph APIs in Viva Connection ACEs. Project releases for SharePoint Framework, PnPjs, CLI for Microsoft 365 plus 2 ACE samples! Sharing is Caring events on March 15th - 1) Microsoft 365 platform community call – 8:00am PT, 2) AMA – PnPjs – 9:00am PT, and 3) PnP SPFx Samples – Solving SPFx version differences using Node Version Manager – 2:00pm PT. The host of this call is Patrick Rodgers (Microsoft) | @mediocrebowler. Q&A takes place as always in chat throughout the call.
Learn more:
• See the full blog post for this call at: https://aka.ms/m365pnp/community/blog
• Download invite for bi-weekly SharePoint Framework call at: https://aka.ms/spdev-spfx-call
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp-videos
A
Hello
and
welcome
to
the
viva
connections
sharepoint
framework
bi-weekly
sync,
it
is
march
10
2022,
I'm
your
host
for
this
call
patrick
rogers
and
we're
excited
for
the
call.
Today
we
want
to
go
ahead
into
our
agenda.
We'll
have
latest
updates
around
sharepoint
framework
patterns
and
practices
updates
across
the
program.
A
New
community
samples,
we'll
do
our
optional
picture
time
for
folks
that
are
interested
there
and
then
again,
three
great
demos
from
siddharth,
eaves
and
paolo,
bringing
us
my
emails,
viva
connections,
adaptive
card
extension,
getting
started
with
the
microsoft
graph,
toolkit
and
sharepoint
framework
and
then
using
microsoft
graph
apis
within
aviva
connections.
Ace
so
really
excited
to
see
all
three
of
those
demos,
but
first
some
quick
updates
across
the
program.
So
often
we
get
asked.
How
do
I
participate?
How
do
I
get
more
involved?
Please
I
want
to
do
a
demo.
A
We
would
love
to
have
you
do
a
demo,
please
reach
out
to
us
down
there
in
that
link
in
the
bottom
right
corner
request
a
spot
to
do
a
demo
I'll
just
tell
you
right
up
front
we're
booked
out
for
a
few
months
now,
but
we
will
find
you
a
slot
we'll
get
you
an
opportunity
to
do
a
demo
for
sure
it
just
might
not
be
right
away
and
those
demos
can
be
anything
spf
x,
anything
across
the
entire
pnp
suite
of
things
or
accommodations
thereof.
So
we
love
love,
love
the
demos.
A
It's
amazing
to
see
all
the
great
work
you
all
are
doing
out
there
for
your
customers
and
your
companies,
and
I
would
love
to
have
you
come
demo
it
on
the
call
as
well.
You
can
always
contribute
on
github
by
reporting
issues,
submitting
pull
requests
or
helping
others
with
their
issues
and
questions
time
permitting.
We
always
appreciate
that
and
then
finally
appreciate
always
your
feedback.
How
are
these
calls
how's?
Our
documentation?
A
Where
can
we
help
and
positive
feedback?
Is
okay
too,
if
we're
doing
something
you
like,
we
could
always
try
and
do
a
little
bit
more
of
it
here.
We
have
a
giant
slide
with,
has
a
lot
of
links
on
it.
The
only
link
you
really
need
to
worry
about
is
dot.
Ms
m365
pnp,
that's
going
to
take
you
to
our
patterns
and
practice
landing
page
and
from
there
you
can
find
links
out
to
all
of
these
community
calls,
as
well
as
links
to
our
developer
videos.
A
A
So
get
involved
in
as
many
of
those
as
you're
interested
you're
absolutely
welcome
in
all
those
places
and
then
finally,
a
bunch
of
different
sample
galleries
for
teams,
spfx,
spfx
aces,
the
power
platform,
spfx
extensions
and
list
formatting
tons
and
tons
and
tons
of
great
samples
to
help
you
get
started
on
your
projects
and
get
ideas
for
new
projects,
but
again
aka
dot.
Ms
slash
m365
pnp
is
the
one
link
that
will
get
you
all
of
those
things.
A
Next
tuesday,
this
is
15th
of
march.
This
is
our
reoccurring.
Microsoft,
365
platform
call
hosted
by
folks
from
microsoft,
presenting
latest
updates
across
the
m365
development
platform.
So
we'll
have
latest
news
from
the
from
the
engineering
teams.
Another
community
photo
op
and
then
we've
got
mark
cashman,
lincoln
damaris,
harini,
salati
and
micellar
barrett,
fit
and
format
microsoft
list
for
work
and
life,
and
then
sebastian
will
be
back
with
more
on
building
mgt
apps
with
sharepoint,
and
then
we
might
have
a
little
bit
of
time.
At
the
end.
A
B
B
For
example,
perhaps
you
want
to
present
on
a
call,
as
patrick
had
mentioned,
but
you're
a
little
nervous,
perhaps
you'd
like
to
submit
a
sample
for
the
very
first
time,
but
you're,
not
quite
sure
how
to
navigate
github
sharing
is
caring,
is
a
program
that
has
been
set
up
to
provide
you
hands-on
guidance.
These
are
safe.
B
Space
opportunities
live
where
you're
going
to
collaborate
with
members
of
the
patterns
and
practices,
team,
mvps,
microsoft,
employees
and
we're
going
to
guide
you
together
through
this
journey
and
empower
you
to
do
more
in
the
community
that
you
love,
we
invite
you
again,
they're
all
free
a.k.a.m.s
forward.
Slash
sharing
is
caring.
We
are
currently
working
on
some
upcoming
schedules.
Just
bear
with
us
there's
a
lot
of
upcoming
events
that
we're
trying
to
maneuver
around,
so
those
will
get
scheduled
out
in
the
next
few
days.
B
If
you
don't
see
new
schedules
for
them
immediately,
but
get
excited
because
next
week
we
are
going
to
have
an
ama
with
our
lovely
host,
patrick
and
julie
turner,
around
pnp
js.
It
has
just
released
3.0
not
too
long
ago.
So
we're
really
excited
about
that.
You
can
register
on
the
site
come.
We
will
record
it
if
you
can't
make
it
but
bring
those
questions
we're
going
to
collaborate.
It's
always
a
really
really
great
opportunity
to
collaborate
with
the
maintainers
of
these
programs.
B
Now,
once
you
do
contribute
in
a
variety
of
ways,
we
want
to
celebrate
all
the
amazing
work
that
you're
doing
in
a
formal
and
official
way
the
patterns
and
practices
recognition
program
has
been
created
to
do
just
that
we
partner
with
credly.
Yes,
that
is
the
same
credly
that
manages
all
of
the
badges
for
microsoft,
certifications,
and
so
it
will
be
associated
to
your
linkedin
profile.
You
can
put
on
your
website.
You'll
see
them
right
there.
Next
to
your
certification,
badges
and
you
can
tweet
them
out,
share
them
with
everyone.
B
It
is
a
great
way
to
be
recognized
for
the
work
you're
doing
and
it
is
100
free.
We
cover
all
the
costs.
We
see
some
of
the
newer
badges
here
on
the
screen
for
power
contributor
on
the
power
platform.
Samples
sharing
is
caring
and
debuting
in
just
the
next
few
days.
Is
our
community
content
author?
That's
the
community
docs
head
up
by
mark
anderson
and
emily
mancini.
So
again,
don't
hesitate.
We
do
need
you
to
opt
in,
though,
so
that
we
can
connect
your
github
account
to
your
email
account
within
credly.
B
A
Great
stuff,
david
and
julie-
and
I
are
very
much
looking
forward
to
that
ama.
I
hope
you
can
join
us
if
you
can't
join
us.
Please
do
send
us
some
questions
ahead
of
time
and
we'll
do
our
best
to
get
those
answered
during
the
ama
so
want
to
make
sure
folks
if
they
have
questions
and
can't
make
that
time.
For
whatever
reason
I
have
an
opportunity
to
get
them
answered
so
happy
to
field
those
as
well.
We'll
now
go
to
vaso
with
updates
cross
sharepoint
framework.
C
Cool,
so
for
those
who
didn't
notice,
just
to
recap,
we
do
have
a
first
version
of
sharepoint
framework
1.15
as
a
public
preview
available.
This
is
an
early
early
early
release
and
it
only
has
a
subset
of
features.
We're
going
to
go
through
that
list
in
a
second.
If
you
go
to
the
following
slide,
we
can
see
that
our
usage
is
just
skyrocketing.
Still
we
did
a
all-time
highest
daily
usage,
this
monday,
7th
of
march
2022,
with
a
quite
significant
leap.
C
Actually
from
the
previous
week
again,
it's
it's
super
cool
to
see
the
adaption
in
the
larger
customers
and
mid-sized
customers
and
and
so
more
and
more
usage
across
the
platform.
We
do
have
tens
of
millions
of
monthly
active
users
using
custom
components
built
with
spfx
in
microsoft,
teams
viva
and
in
sharepoint.
This
is
something
which
actually
showed
already
in
the
first
of
march.
C
The
weekly
developer
call
as
we
had
the
engineering
people
and
pms
joining
from
the
spfx
team,
not
only
just
me,
but
other
people,
the
new
version
of
1.15
beta
and
the
first
version
is
out
that
has
a
craft
sdk
v3
support.
There's
bug,
fixes
and
adjustments
on
the
based
on
github
issues
and
there's
a
new
action
times
for
the
media
and
geo
location
so
which
are
in
preview
as
part
of
the
1.15
release
journey.
Then
we'll
keep
on
introducing
additional
features
capabilities
until
it's
ready
to
get
shipped
eta
right
now
in
june
2022.
C
So
we'll
keep
you
up
to
date,
using
the
developer
block
and
then
social
media
as
there's
always
a
new
version
available,
something
which
is
also
coming
well.
Post
115,
which
is
actually
kind
of
a
cool
thing.
Is
that
we're
aligning
more
and
more
on
the
on
the
microsoft
365
and
teams
platform
as
well.
So
in
the
future,
you
are
able
to
also
be
and
building
acs,
which
are
lit
or
powered
by
microsoft,
bots,
which
is
kind
of
cool.
C
D
Julie,
take
it
away
sure,
so
we
are
going
to
be
doing
some
releases
tomorrow.
This
is
march
11th
tomorrow,
so
we're
going
to
do
a
2.13
release.
This
is
going
to
fix
the
copy
2
function
for
root
sight
collection
from
where
you
don't
have
root.
Site
collection
permissions
these
so
for
version
two
we're
not
going
to
have
any
long-term
support.
D
So
if
you
there
are
some
community
submitted
prs,
we
will
roll
out
a
version,
but
as
far
as
the
core
team
goes,
we
are
not
going
to
continue
to
improve
version
2,
but
we
will
do
releases
for
pr
submitted
to
the
version
2
branch
for
at
least
the
next
couple
months,
we'll
update
everyone.
When
that
guidance
changes,
we
will
be
doing
a
version
3.1
release,
also
on
march
11th,
and
so
that's
going
to
have
some
general
documentation
updates.
D
We
will
have
documentation
for
using
esm
modules
and
typescript
solutions,
and
we
will
have
some
fixes
for
profiles,
my
properties
and
fixes
for
the
get
edit
profile
link
and
get
is
my
people
list
public.
So
those
are
some
fixes,
there's
a
few
other
things
that
will
probably
be
released
as
well
check
out
our
change
log
for
all
the
details.
We
also
did
do
a
version
303
release
on
march
3rd
to
fix
a
search
issue
again
with
the
new
major
release.
We
obviously
will
see
some
issues
here
and
there.
D
So
please
direct
all
your
feedback
to
the
issues
list
and
we
will
try
to
get
to
your
issue
as
soon
as
possible
and,
as
always
follow
us
on
m365
pmpjs
on
twitter.
We
are
also
publishing
updates
to
the
microsoft
365
pmp
page
on
linkedin,
so
you
can
also
follow
us
there,
and
that
is
all
I
have
back
to
you.
A
Patrick
great
stuff,
thank
you,
julie
and,
thanks
to
everybody,
who's,
helping
us
out
reporting
stuff
with
the
new
version.
Three,
always
a
few
misses
for
big
major
version
releases.
I
appreciate
all
the
help
from
everyone.
There
updates
on
the
cli
for
microsoft,
365
new
preview
version
5.1
is
out
with
retrieving
planner
plans,
details
prompting
for
missing
required
values
in
commands,
as
well
as,
what's
coming
up
validating
your
sharepoint
framework
projects,
downloading
teams,
app
packages
and
more,
you
can
always
install
that
preview.
A
5.1
npm
install
dash
g
at
pnp,
cli
dash,
microsoft,
65
at
next
and
the
docker
container
command
is
there
so
that's
a
great
way
to
try
out
the
cli
within
a
docker
container,
that's
predefined
by
the
team
to
make
it
easy
to
ensure
you've
got
all
the
dependencies
in
runtime
correct
to
work
on
that
you
can
follow
up
on
the
release,
notes
there
in
the
link
and
definitely
encourage
you.
If
you
haven't
used
it,
try
out
the
cli
great
way
to
manage
your
projects.
A
Script
things,
keep
things
consistent
across
environments,
so
excited
to
see
that
next
up,
spfx,
reusable
components.
So
we've
got
a
set
of
react
controls.
These
are
controls
designed
to
be
used
in
the
body
of
your
web
parts
or
application
customizers,
and
this
360
is
out
so
a
new
adaptive
card
host
control
enhancements
for
multiple
controls,
updated
localization
for
swedish,
as
well
as
various
other
fixes.
A
You
can
check
out
the
release,
notes
at
the
link
there
and
the
property
control
designed
for
use
in
the
edit
pane
of
your
web
parts
are
at
350,
giving
us
support
for
aces,
multiple
enhancements
to
various
controls
and
other
fixes
encourage
you
to
check
out
the
release
notes
there.
This
is
another
great
way
to
get
your
project
jump
started
and
build
on
top
of
existing
controls
built
by
the
community
that
you
can
reuse
within
your
project.
A
Next
up
is
modern
search,
so
we've
got
ak
dot.
Ms
slash
pnp
search
for
all
the
details.
There
building
modern
search
experiences
with
flexible
web
parts
version
4.5.4
is
the
february
2022
release.
You
can
read
all
the
release,
notes
for
the
fixes
and
updates
there,
but
this
is
a
great
way
to
build
modern
search
experiences
within
your
company
or
customer
portals
built
again
on
community
resources
to
really
help
you
get
started
and
build
rich
experiences
without
having
to
do
all
that
coding.
A
B
Yep,
thank
you,
patrick
yep,
and
healthy
wishes
out
to
hugo
as
well.
We
know
it's
hard
to
put
him
down
and
make
him
rest.
So
hopefully
he
is.
We've
got
two
fantastic
new
aces
for
us
to
look
at
this
week,
zhao
one
of
our
amazing
contributors,
my
calendar
plan,
which
is
an
ace
that
allows
you
to
see
your
upcoming
calendar
and
interact
with
it,
and
then
we've
got
another
weather
ace
from
akash
that
we
can
take
a
look
at
so
both
of
these
are
available
and
go.
Try
them
out
again.
B
The
aces
is
a
growing
repository
and
is
absolutely
open
for
more
contributions,
and
we
could
we
know,
there's
a
lot
of
moving
parts,
so
we
are
just
putting
the
finishing
touches
on
the
getting
started
with
vp
connection
adaptive
card
extensions
sharing,
his
caring
session,
derek
cash
peterson,
luisa
freese,
hugo
and
myself
we're
meeting
multiple
times
this
week.
So
in
the
next
few
days,
we're
going
to
see
a
a
date
available
for
that
it's
going
to
be
a
multi-day
session,
so
we're
going
to
have
homework
and
it's
going
to
be
really
really
cool.
B
A
Hey
thanks
david
and
thanks
to
everybody,
who's
working
on
the
samples
really
an
amazing
resource
for
the
community,
so
certainly
encourage
you
to
check
out
those
samples
and
you've
got
a
new
project
and
now
we'll
go
over
to
visa
for
optional
picture
time.
If
you
are
interested,
you
may
turn
on
your
camera
and
join
into
the
group
photo.
C
C
C
That's
a
bit
strange!
Let
me
click
the
recording
button
and
let's
wait
few
more
seconds
until
we
fill
in
the
50
seats.
How
is
there
a
freeze
on
the
middle?
That's
crazy,
but
let's
do
some
hand
waving.
Everybody
said
thanks
everybody
for
joining
really
awesome
to
have
you
again
on
the
call.
Thank
you
thank
you
for
being
here.
It's
really
really
cool
to
see
also
that
we're
starting
to
be
have
those
in
person,
conferences
coming
up
and
thanks
everybody.
A
E
Thank
you,
patrick
hello,
and
welcome
everyone.
Today,
I'm
going
to
present
ace
component,
my
email
a
little
bit
about
myself.
I
am
siddharth
vagasa,
I
am
in
microsoft,
mvp.
I
am
an
active
pnp
contributor
and
these
are
some
of
the
social
handle
links
through
which
you
would
be
able
to
connect
with
me.
E
E
So
the
driving
factor
here
for
this
particular
sample
was
basically.
This
was
my
first
adaptive
card
extension,
which
we
can
say
a
dynamic
extension
which
was
getting
actually
data
from
somewhere.
So
the
idea
here
was
to
explore
the
adaptive
card
extension,
how
to
call
a
graph
api
from
the
elliptic
card,
extensions
understanding,
the
concepts
of
the
card
view
and
the
queue
being
an
spfx
developer
for
so
long.
E
This
concept
is
little
bit
different,
but
it
takes
for
to
understand
like
how
these
card
views
and
how
the
quickviews
are
interconnected
with
each
other,
it's
it
needs
and
practical.
So
what
for
same
purpose?
What
I
did
was,
you
know
basically
start
getting
working
on
this
sample
to
understand
how
this
card
use
and
wiki
would
work,
how
the
state
management
will
work
between
the
views
this
sample.
E
If
you
can
think
about
it,
it
will
gives
us
a
personalized
experience
in
the
viva
connection,
because
it
will
be
able
to
show
the
current
logged
in
user's
email
addresses
in
the
card
view,
and
then
it,
the
user,
would
be
able
to
navigate
between
different
emails
and
on
click
of
particular
view.
They
would
be
able
to
actually
view
the
detail,
email
and
there
is
a
button
also
in
the
quick
view,
which
will
take
the
user
to
that
particular
email
in
the
outlook
web.
E
So,
overall,
the
other
concepts
which
we
which
were
explored
here
is
how
to
make
the
action
buttons
dynamic,
which
will
basically
navigate
between
the
cartridge
which
we
will
show
in
the
demo,
so
yeah,
let's
quickly
jump
to
the
demo.
So
basically,
this
is
the
adaptive
card
extension.
If
I
go
to
preview
mode,
if
you
see
right
now,
it
is
basically
logging
and
getting
my
email
addresses
and
click
of
particular
email.
It
will
be
able
to
click
the
preview
of
that
particular
email.
E
And
then
on
click
of
particular
email,
we
will
be
able
to
go
to
the
particular
outlook,
emails
or
the
targeted
outlook
image.
So
this
is
a
simple
demo,
as
I
said,
but
the
idea
here
was
to
basically
explore
the
adaptive
card
extension
and
see
what
we
can
build
with
it.
This
is
what
we
have
so
going
through
the
code.
E
Let's
see
again,
we
would
create
this
using
yeoman
sharepoint
generator,
wherein
we
would
choose
an
s
component
as
our
component,
so
this
would
be
the
main
file,
which
is
basically
a
kind
of
an
extension
file
which
would
be
extended
from
the
better
base
adapter
card
extension.
Here
I
have
my
states
and
the
properties,
as
we
have
in
spfx
web
part.
Also,
the
states
basically
is
to
hold
the
emails
which
will
get
from
the
graph
api.
E
The
current
index,
the
current
active
index,
to
basically
render
the
quickview
and
the
current
email
object,
which
will
basically
dynamically
populate
that
quickview
then
in
the
initialization.
This
is
basically
the
state
initialization.
This
is
similar
to
what
we
do
with
the
spfx
or
with
the
class-based
state
components.
E
This
is
where
the
navigator
would
navigate
and
register
all
the
cardview.
So
this
is
important
to
understand
here
is
that,
whichever
car
we
wanted
to
be
part
of
our
solution,
we
would
have
to
make
sure
that
the
card
is
registered
with
a
particular
name
and
which
mapping
to
that
particular
component
of
that
card.
So
in
this
case
I
am
just
using
cardview
and
the
queue
which
comes
with
default
solution
generators.
So
it
would
be
just
two
quick
views,
but
we
can
have
as
many
quick
view
as
possible.
E
Then
this
is
the
method
which
basically
gets
the
get
outlook
data.
So
we
are
calling
the
graph
api
misleads
mail,
folders
inbox
messages,
which
will
give
me
a
list
of
messages
from
my
mailbox
for
getting
the
data
from
the
graph
api.
We
are
using
the
ms
graph
client
factory,
so
using
the
client
factory.
We
would
be
able
to
make
any
graph
api
call
from
the
message
in
this
case,
then
we
are
setting
the
state
here
to
set
the
state
we
are
setting
the
current
email
address,
which
would
be
the
zeroth
index
by
default.
E
Another
important
thing
to
note
here
is
this,
which
is
basically
the
render
card.
So
here
we
are
basically
passing
returning
the
constant
which
we
said.
You
know
the
unique
identifier
for
a
particular
card
view.
So
this
is
where
how
the
particular
card
view
is
getting
rendered
now.
So
when
we
say
this
particular
card,
we
would
be
rendered,
so
we
would
have
a
card
view
component,
which
would
be
getting
rendered
in
the
cardboard
component.
E
Again
cardboard
component
would
be
extended
from
basic
primary
text
card
view
in
this
case,
so
we
have
three
types
of
card
views
which
we
can
have,
one
which
would
be
a
basic
type.
One
would
be
a
basic
primary
text
and
one
would
be
kind
of
basic
primary
text,
but
it
also
has
an
image
component
associated
with
it.
So
this
one
is
primary
text
so
which
we
will
in
this
case
we
will
get
basically
two
things
to
show
on
the
card
view.
E
One
would
be
the
primary
text
and
one
would
be
the
description
and
then
the
buttons
which
would
be
displayed
on
the
component,
so
only
we
would
be
able
to
add
only
this
three
component
in
the
card
view
we
don't
depending
on
which
kind
of
card
view
which
we
are
using.
We
won't
get
anything
more.
So
if
it
is
an
image
card,
we
would
probably
get
an
image
card
also
which
image
placeholder
also,
which
we
can
use
so
considering,
first
see
how
we
are
getting
particular
data.
E
So
in
this
case
there
would
be
an
data
method
which
is
overridden
method
and
because
it
is
of
a
type
primary
text
text
card,
we
would
have
an
option
to
return
an
object
wherein
we
can
send
primary
text
and
description
which
would
be
rendered
in
the
component.
So
in
this
case,
what
I'm
doing
is
basically
as
soon
as
we
have
the
emails
which
are
loaded,
I'm
getting
reading
from
the
state
of
the
email
object,
the
subject
and
the
from
email
address.
E
Then
the
second
important
thing
here
is
to
understand
is
the
card
button
method.
This
is
basically
the
method
which
will
return
the
buttons.
So
in
my
case
the
buttons
would
be
the
previous
and
next
button,
but
I
need
to
make
that
buttons
dynamic,
depending
on
which
is
the
current
index
of
that
particular
email.
E
So
if
the
current
index
is
greater
than
0,
it
means
I
know
that
I
have
to
push
the
previous
button
so
that
user
can
navigate
to
previous
email
if
it
is
less
than
the
current
index
is
less
than
the
length
of
the
email
it
means.
I
know
this
is
a
large.
This
is
not
the
last
email.
That's
when
I
I
need
to
push
the
next
button,
so
this
is
how
we
are
able
to
show
and
hide
the
previous
next
buttons
maximum
for
a
card
cardview
component.
E
E
Then
there
is
an
action
method.
So,
basically,
here
what
we
are
doing
is
when
we
are
pushing
the
button.
We
are
saying
the
action
is
of
type
submit
and
I'm
passing
a
parameter
id
which
basically
identifies
that
particular
button,
whether
it
is
a
previous
button
or
whether
it
is
a
next
button,
and
here
if
the
type
is
submit
what
we
are
doing
is
and
if
the
id,
when
then
we
get
the
data
of
that
particular.
Whatever
parameters,
we
would
have
passed
in
the
action
in
the
action.data
method.
E
Here
we
are
comparing
it
with
the
choice
wherein,
if
it
is
a
previous,
I
am
decrementing
the
index
and
loading
the
current
email
by
decrementing
the
index.
If
it
is
next,
we
are
setting
incrementing
the
index
and
also
setting
the
current
email
object
to
particular
thing
right
now.
After
all
of
this,
what
the
next
thing
which
would
be
having
is,
we
will
do
when
a
particular
card
is
being
selected
right.
So
that's
where
we
want
to
basically
open
the
quick
view.
So
this
is
the
method
which
basically
can
have
either
two
types
of
return
object.
E
One
can
be
a
quick
view
card
action
or
it
can
be
an
external
link.
So
if
you
want
to
open
an
external
link,
the
type
can
be
an
external
link
in
the
parameter.
We
would
have
a
url
of
the
particular
external
link
where
we
want
user
to
redirect,
but
in
this
particular
case,
what
I
wanted
to
do
is
I
wanted
to
open
that
particular
quick
view.
So
I'm
just
this
would
be
a
default
method
which
would
be
coming
when
you
are
rendering
the
code.
But
if
you
want
to
customize
it,
you
can
always
customize
it.
E
So
here
I
am
saying
that
okay,
even
the
user
card
has
been
clicked.
We
need
to
basically
open
the
quick
view
registry
so
quickly
going
to
preview
component
card.
We
would
be
able
to
basically
place
that
in
this
particular
quickview
component,
it
would
be
extended
by
a
base
adaptive
card
view.
It
will
also
the
parameters
would
be
also
passed
where
in
the
properties
state
would
be.
E
E
So,
in
my
case,
what
I
did
is
I
created
basically,
a
ipvq
data
object
wherein
I'm
just
passing
a
single
email
message,
object
to
that
particular
adaptive
card
and
then
using
the
properties
of
that
particular
object.
We
are
making
the
adoptee
card
dynamic.
So
now,
let's
quickly
go
to
the
template.
The
adaptive
card
template
so
here
in
the
top
body
part.
What
we
are
seeing
is
the
email
subject.
So
if
you
look
at
any
email,
so
this
is
the
email
subject
which
we
are
getting,
then
I
have
a
column
set
wherein
I
need
two
columns.
E
That
is
because
one
I
need
to
show
the
image
and
also
the
from
email
address
and
the
created
date.
So
this
is
how
the
column
set
would
be.
In
the
first
column,
I
need
an
image
which
will
be
displayed
in
the
second
column.
I
need
the
from
email
addresses
and
the
date
which
is
getting
displayed.
All
of
these
are,
depending
on
the
adaptive
card
designers.
E
You
can
use
adaptive
card
designer
dot,
io
and
design
the
adapter
card,
which
we
want
use
that
template
and
just
paste
it
here
and
make
it
dynamic
the
way
we
want
it
to
dynamic,
make
it
dynamic.
Then
this
is
the
date.
Then
we
have
the
body
preview,
which
is
getting
displayed
once
the
on
the
below
part.
So
this
is
the
body
preview
and
also
there
is
a
button
which
says
view
button.
E
So
basically,
that
button
is
coming
because
we
have
an
action
attribute
here
when
I
am
saying
that
I
need
and
button
whiskers
view,
and
what
I
wanted
to
do
is
my
action
type
is
open
url,
so
it
will
redirect
user
to
that
particular
webmail,
and
I
am
using
babbling
property
of
the
message-
object
to
basically
send
the
user
to
that
particular
email
addresses.
So
this
is
how
we
would
be
able
to
use
and
make
the
adaptive
card
extension
getting
data
from
the
graph
api.
E
E
So
in
this
case
we
are
using
mail,
dot
rate
basic
and
mail.read
to
basically
get
the
current
logged
in
users,
email
addresses
and
then
the
graph
client
factory
would
be
able
to
use
the
token
for
the
current
logged
in
user,
because
this
would
be
rendered
in
the
sharepoint
itself
and
would
be
able
to
get
that
data.
So
that's
how,
as
I
said,
it
was
a
just
a
first
dynamic
s
company
which
I
was
exploring
and
when
I
created
it,
I
have
wrote
an
article
also
about
it.
E
A
Awesome
very
great
stuff,
very
cool
demo.
There
excited
to
see
more
use
of
these
aces
adaptive
card
extensions
out
there
in
the
community
encourage
folks
to
definitely
check
those
out.
If
you
haven't
it's
a
really
fun
way
to
extend
sharepoint
framework,
but
with
that
we're
gonna
go
over
to
eaves.
If
you
are
ready,
you
can
go
ahead
and
take
over
the
presentation.
A
F
Take
it
away
perfect,
welcome
everybody
so
today,
I'm
just
making
a
demo
on
getting
started
with
microsoft,
graph,
toolkit
and
sharpen
framework.
So
my
name
is
eva
barcat,
I'm
a
business
application
consultant
at
sword
group.
So
basically,
I'm
working
everything
related
to
microsoft,
365,
azure
dynamics,
365
and
poor
platform,
I'm
based
in
switzerland
in
lausanne,
I'm
also
a
microsoft
mvp
in
the
office
development
category,
I'm
the
only
one
in
switzerland
as
active
mvp
in
this
category.
So
this
is
great
stuff
and
I'm
also
a
microsoft
certified
trainer.
F
If
you
have
any
questions
so
feel
free
to
reach
me
out
on
my
social
networks
or
directly
on
my
on
my
blog
I'm
trying
to
answer
every
every
time.
I
have
some
question
or
technical
enquiries,
so
just
for
for
this
demo
just
a
quick
overview
of
the
configuration.
So
basically
I'm
using
windows
10,
I
will
use
node
version
1481.
F
I
will
use
sharpen
framework
1
14
and
I
will
use
mgt
spf
x
package,
the
last
the
latest
version-
and
I
will
start
with
a
web
part
solution
with
a
react
framework,
and
I
will
use
mgt
react
in
the
latest
version
2..
So
basically,
this
is
a
version
released
this
monday,
so
this
is
pretty
fresh,
so
just
to
start
the
first
step
to
configure
a
project,
you
need
to
manage
the
sharpen
framework
library
for
microsoft,
graph
toolkit.
F
F
Then
in
your
project,
you
need
to
install
the
mgt
spfix
npm
package
with
the
same
version
number
of
the
mjt
spfix
package
from
your
tenant,
app
catalog.
So
basically,
if
you
have
an
existing
project,
feel
free
to
upgrade
it
or
install
the
latest
version
in
the
tenant,
tab,
catalog
and
inside
your
project.
So
basically
you
need
to
use
npm
install
at
microsoft
or
mgtx
prefix
at
latest
for
upgrading
an
existing
project
if
you
want
to
deploy
the
latest
version.
F
The
third
step
is
to
instantiate
the
sharpen
provider.
So
basically
you
need
to
import
providers
and
sharpen
providers
from
the
mgts
prefix
package.
As
you
can
see
on
the
screen,
then
you
need
to
instantiate
the
sharepoint
provider
in
the
onnis
method
of
the
webpart
file.
So
basically,
as
you
can
see,
you
just
instantiate
the
sharpen
provider
and
you
pass
the
context
as
parameter.
F
The
fourth
step
is
to
use
simply
to
use
the
rear
components.
In
my
case,
it's
based
on
react.
So
first
you
need
to
import
the
required
components.
So,
for
example,
you
have
agenda,
you
have
person,
file,
list
task
and
so
on.
So
basically
you
have
to
import
this
before
using
it
and,
after
feel,
free
to
use
all
the
components
inside
your
web
part.
F
F
So
this
is
the
steps
and
now
that's
a
quick
demo,
so
I'm
switching
back
to
visual
studio
code.
So
basically
the
first
step
just
to
show
you
because
it's
really
important,
so
you
need
to
deploy
the
microsoft
graph
toolkit
library.
So
basically
you
go
through
this
link
and
you
deploy
this
package.
So
basically,
this
is
the
latest
one,
the
240.
F
you
deploy
this
inside
your
tenant,
app
catalog.
In
my
case,
I've
just
deployed
this
fresh
version,
so
this
is
the
latest
one
and
when
it's
done
it's
okay
and
you
can
directly
import
two
things.
The
first
thing
is
the
mgt
spfx
library,
so
you
need
to
use
npm
install
and
you
install
the
mjt
specifics
package.
Second,
you
install
the
mgt
react
in
the
same
version.
You
see.
F
The
version
is
the
same
and
after
that
you
are
ready
to
use
the
components
so
basically,
the
first
step
after
installing
those
two
packages
is
to
go
in
the
web
part
side
and,
for
example,
in
my
case,
I'm
just
importing
the
providers
and
sharpen
providers
from
the
mgt
spfx,
just
after
instantiate
the
sharpen
provider
inside
the
units
method.
So
basically
you
see
I'm
passing
the
context
of
the
webpart
directly
in
the
sharpen
provider
and
after
that,
I'm
ready
to
use
these
components
inside
my
components.
F
So
basically
I've
made
just
a
simple
web
part
project
to
show
you
a
little
more
things
about
this
toolkit.
So
basically
you
see
I'm
just
importing.
As
you
can
see.
Sorry,
it's
a
little
bit
young,
but
I'm
importing
a
lot
of
components
so,
for
example,
agenda
person,
sorry,
person
task
and
so
on
and
after
I
can
use
it
directly
inside
this
little
project.
So
I
made
just
a
quick,
a
quick
project.
I
will
just
show
you
the
render.
So
the
render
is
like
this.
It's
pretty
simple.
F
You
see,
you
have
a
lot
of
components,
so
basically
I've
made
some
files,
some
tasks
to
do,
and
I
have
also
two
two
sections:
where
I'm
using
the
get
components
and
one
of
my
favorite,
because
with
the
get
component,
you
can
query
any
endpoint
on
microsoft
graph
with
a
get
request.
So
basically
you
can
get
emails.
You
can
get
your
join
team,
for
example,
it's
pretty
simple,
but
it's
just
to
show
you
the
behavior,
but
in
my
case
I
can
request
all
the
teams
I
belong
to.
F
So
basically,
if
I
show
you
the
code,
it's
pretty
simple,
so
basically
you
use
as
a
other
web
development
project.
You
have
the
react
component
and,
for
example,
I
have
the
person
component.
I'm
getting
my
profile,
you
see
you
can
customize
the
data
type,
I'm
putting
my
photo.
You
have
the
card
interaction
in
my
case,
I'm
putting
a
hover
behavior
to
to
display
some
advanced
detail
of
my
my
profile
when
I
go
over
the
card.
F
Basically,
you
see
you
have
the
agenda,
it's
pretty
simple,
just
to
show
you
the
basic
stuff,
but
you
can
group
by
there.
You
can
show
a
max
number
of
items.
You
have
the
the
files
file
list,
so
basically
you
can
enable
the
upload
process,
and
so
on.
You
have
the
task
you
have
the
to
do
and
my
favorite,
because
in
my
recent
experience
I'm
using
a
lot
these
get
components.
F
So
basically,
in
my
case,
I'm
just
getting
my
messages,
you
see
you
provide
the
graph
get
query,
then
I'm
using
the
v1
and
you
have
the
scopes.
So
basically,
this
is
the
card
here.
So
basically,
meld.read
is
the
scope
to
use
to
get
the
email
and,
after
I'm
providing
just
a
property
match
pages
to
restrict
the
number
of
items
and
after
the
great
thing
with
the
get
you
can
create
a
template.
F
So
basically,
in
my
case,
I've
declared
a
mail
template
and
you
can
retrieve
all
the
data
context
and
the
data
context
contains
all
the
properties
from
microsoft
graph
and
I
can
use
all
these
properties
inside
my
template.
So
you
see
I
can
display
the
subject.
I
can
display
the
person
component
with
the
person
query.
As
you
see
the
address
the
email
address
of
the
of
the
sender.
F
So
you
see
you
can
create
your
own
template
with
all
the
property
you
want
and
you
render,
as
you
want
inside
your
report,
so
this
is
really
really
powerful
and
after
the
second
one
is
for
my
teams,
you
see
I'm
just
getting
the
themes.
I
belong
to
v12
to
get
the
the
scope
inside
this
template
is
teams.basic.org.
F
So
basically,
this
is
the
scope,
the
permission
to
retrieve
all
these
properties
and
information
from
microsoft,
graph
and
after
I'm
just
restricting
with
match
pages
onto
and
like
the
mail.
You
have,
for
example,
the
team
template,
and
in
my
case
you
see
the
team
template.
I
can
retrieve
the
data
context
and
with
the
data
context,
I'm
just
displaying
some
properties
like,
for
example,
in
my
case,
I'm
putting
just
a
teams
icon
and
I'm
putting
the
display
name
of
the
team
and
the
description,
and
in
this
case
the
renderer
is
like
this.
F
F
So
basically,
this
is
really
powerful
and
I
saw
that
sebastian
levert
will
will
make
a
presentation
based
on
maybe
advanced
concepts.
So
basically,
this
was
my.
This
was
my
demo
this
week.
This
demo
was
just
to
show
you
the
basic
stuff
on
how
to
get
started
with
a
microsoft
graph,
toolkit
and
chapel
framework
and
for
advanced
stuff.
Maybe
I
will
make
another
demo
with
a
more
advanced
concept,
but
the
goal
of
today
it
was
just
to
show
you
how
to
get
started,
the
exact
steps
and
maybe
some
some
cool
stuff
like
the
get
component.
A
Right
demo
great
work
on
that,
and
I
don't
know
it
looked
pretty
advanced
to
me
so
excellent
stuff.
There
excited
for
folks
to
check
that
out
in
the
sample
gallery
and
our
last
demo
today
comes
from
paulo
using
microsoft,
graph,
apis
and
viva
connection
aces
adaptive
card
extensions,
paolo,
go
ahead
and
you're
already
taking
over
the
screen,
such
a
pro
over
to
you,
paulo,
take
it
away.
G
Hello,
everyone
and
yes
now
we
are
going
to
talk
about
how
we
can
consume
micrograph
apis
within
microsoft,
viva
connections,
adaptive
card
extensions,
so
a
few
words
before
digging
into
the
demo,
and
I
simply
want
to
remind
you
that
whenever
we
create
an
adaptive
card
extension
with
sharepoint
framework
under
the
cover,
we
have
a
sharepoint
framework,
the
whole
sharpen
framework
infrastructure
so
as
like,
as
we
can
easily
consume
micrograph
in
any
kind
of
client,
sidewall
part
that
we
create
with
spfx.
So
we
can
do
the
same
in
an
adaptive
card
extension.
G
So
we
can
simply
rely
on
the
ms
graph
client
type.
We
need
to
define
in
the
package
solution
json
file
of
our
solution.
The
web
api
permission
request
that
we
want
to
have
satisfied
from
a
requirement
permission
requirement.
Point
of
view.
We
need
to
grant
those
permissions
to
the
solution
that
we
created
with
spf
exit
for
the
adaptive
card
extension
that
we
created
with
spfx
and
then
in
our
code
base.
G
We
can
just
rely
on
the
msgraph
client
object
in
order
to
make
queries
against
micrograph
to
retrieve
items
or
eventually
interact
with
the
the
microtestify
workloads
through
the
micrograph,
in
order
to
create
new
instances
of
events
in
a
calendar
or
sending
messages
or
stuff
like
that.
So
this
is
what
we
are
going
to
see
from
a
very
basic
point
of
view,
just
to
understand
how
we
can
do
that
in
an
adaptive
card
extension.
So
let
me
switch
to
the
demo
and
first
of
all,
this
is
the
very
first
one
I
will
show
you.
G
This
is
a
very
basic
sample
in
which
I
want
to
focus
on
how
we
can
consume
graph,
rather
than
how
we
can
create
a
really
cool
ui,
because
this
is
just
a
demo
focus
on
consuming
a
graph
in
ac.
So
this
is
a
sample
in
which
we
can
see
a
list
of
events
in
the
calendar
of
the
currently
connected
user.
How
can
we
do
that
using
adaptive
card
extensions?
So
here
we
have
a
solution
that
I
created
with
the
human
generator
for
sharepoint
framework
and
I
simply
scaffolded
an
adaptive
card
extension
object
or
component
here.
G
First
of
all,
in
the
on
init
method
of
my
component,
aside
from
registering
the
card,
the
card
and
quick
views
that
I
have
in
my
component.
In
my
ace,
I
just
create,
as
I
was
telling
you,
through
the
context
of
sharpening
framework,
a
new
instance
of
the
micrograph
client
using
the
ms
graph
client
factory
property
of
the
context
of
spfx
and
using
the
get
client
method.
G
If
the
event
is
an
online
meeting
or
not,
and
the
web
link
to
the
event,
so
whenever
I
want
to
use
this
calendar
service,
I
first
of
all
initialize
the
object
and,
as
you
can
see
here
in
the
calendar
service,
I
make
it
available
globally,
so
that
I
can
simply
rely
on
the
instance
that
I
have
and
using
the
set
timeout
method.
I
simply
load
the
top
calendar
items
in
a
dedicated
request,
rather
than
doing
the
actual
request
within
the
unit
method,
just
to
speed
up
the
load
of
the
adaptive
card
extension.
G
So
in
the
get
top
calendar
items
method,
I
get
back
my
array
of
events
and
I
can
simply
set
them
inside
this
state
of
my
component.
Now
the
get
top
calendar
items
simply
relies
on
the
graph
client
and
using
the
me
slash
events
and
point
of
microsoft,
graph
version,
1
retrieves,
the
properties
that
I'm
interested
in
making
a
get
request.
So
really
simple
from
a
code
based
point
of
view.
G
Once
I
have
defined
the
graph
client
code,
I
need
to
also
declare
in
my
solution
in
the
package
solution
json
file
that
I
need
the
permission
to
consume.
The
calendar
and
in
order
to
know
what
permission
I
need,
I
can
simply
rely
on
the
documentation
of
graph,
so
here,
for
example,
you
can
see
the
page
about
how
to
get
the
list
of
events
inside
the
docs
of
microsoft
graph,
and
here
we
can
clearly
see
that
with
a
delegated
approach,
so
with
the
identity
of
the
currently
connected
user.
G
In
order
to
get
access
to
the
list
of
events
in
her
or
his
calendar,
we
need
to
have
the
calendars
that
read
or
eventually
the
calendars,
don't
read
right,
but
clearly,
if
we
simply
want
to
read
the
events
we
we
will
just
need
the
calendars
to
read
the
permissions
and
that's
why,
in
the
package
solution.json
file,
I'm
declaring
that
from
a
web
api
permission
request
point
of
view.
I
need
for
the
resource.
G
Micrograph
the
calendars
dot
read
permission
so
that
when
I
will
be
ready
with
my
solution
fully
implemented,
I
will
be
able
to
deploy
my
solution
in
the
app
catalog
and
from
an
admin
point
of
view.
I
will
be
able
to
grant
this
permission
request
to
my
solution
and
being
able
to
consume
the
micrograph.
G
So
now
that
we
have
seen
how
we
can
retrieve
the
list
of
events
and
how
we
store
the
events
in
the
state
object
of
my
adaptive
current
extension,
we
can
see
that
well.
From
the
car
view
point
of
view.
The
computer
is
really
trivial
and
it
simply
relies
on
a
button
to
show
the
actual
quick
view
in
the
quick
view.
G
On
the
contrary,
in
the
data
method,
we
return
a
complex
type,
which
will
be
made
of
a
title
and
of
the
array
of
the
events
that
we
have
in
the
state
of
our
adaptive
card
extension
component
as
such
in
the
json
definition
of
our
ace.
We
can
declare
we
can
define
the
ui
of
the
quickview,
including
the
data
binding
on
the
events
that
I
have
in
my
events
array
and
that's.
Why?
G
Here,
aside
from
providing
a
title
in
a
text
block
inside
the
adaptive
card-
syntax,
we
also
have
the
header
so
the
start,
and
the
time
and
the
subject
of
every
single
event
in
my
calendar,
as
well
as
we
use
the
data
binding
functionalities
that,
for
the
sake
of
completeness,
we
covered
in
one
of
the
previous
sig
calls
a
few
weeks
ago.
But
here
we
say
that
the
data
binding
for
a
container
that
we
have
right
here
is
targeting
the
events
property
of
the
object
that
I'm
providing
right
here
in
the
data
method.
G
G
As
I
was
telling
you
before,
you
can
create
a
package,
so
an
sppkg
file
that
we
already
have
right
here
in
the
sharepoint
slash
solution,
folder
of
my
solution
and
then
you
can
upload
the
package
into
the
app
catalog
of
your
sharepoint
online
target
environment
target
tenant.
So
let
me
do
that
just
for
the
sake
of
completeness,
if
I
will
drag
and
drop
the
package
on
my
app
catalog,
as
you
can
see
here,
and
let
me
zoom
in
oops
oops.
G
The
can
infrastructure
of
sharpen
framework
is
telling
me
in
order
to
properly
use
this
component.
You
will
need
to
grant
the
calendars
the
treat
permission
for
microsoft
graph
to
this
component.
I
can
click
on
the
deploy
button
and
I
can
go
to
the
admin
ui
of
sharepoint
online
and
under
the
advanced
section
in
the
api
access
section
section,
we
can
see
that
we
will
have
in
the
list
of
pending
permission
requests
the
permission
request
for
calendars.treat.
G
Actually,
in
my
scenario,
I
already
granted
the
permission
previously,
so
I
can
simply
see
that
I
have
in
the
list
of
already
approved
requests
a
bunch
of
permissions
for
microsoft
graph,
including
the
calendars.read,
as
you
can
see
right
here,
but
in
case
I'm
targeting,
I
was
targeting
a
fresh
new
tenant.
Where
I
don't
have
the
permission
already
granted.
G
Now
so
far,
we've
seen
that
we
can
read,
we
can
consume
data
from
micrograph,
but
actually
we
can
do
more.
Clearly,
we
can
do
more.
We
can,
for
example,
also
create
new
content
through
the
micrograph
in
order
to
feed,
for
example,
or
to
create
new
items
in
the
calendar
of
the
currently
connected
user.
So,
just
to
show
you
what
I'm
talking
about,
let
me
switch
to
another
demo
that
I
have
right
here.
G
G
So
let
me
refresh
the
page
to
get
the
new
manifest,
and
here
we
are
create
calendar
event,
as
you
can
see
now,
I'm
also
behaving
like
a
real
designer,
I'm
just
kidding,
of
course,
but
here
you
can
create
a
new
event
in
the
calendar
of
the
currently
connected
user.
So
here
is
my
calendar,
which
is
clearly
empty
right
now,
but
I
can
come
here
and
I
can
say:
okay
create
a
new
event.
I
can
provide
the
subject
for
the
event,
which
can
be
sig
called
demo.
Why
not?
G
The
event
will
be
today
at
this
time,
so
I
like
it.
The
event
will
end
still
today
and
let's
say
it
will
last
one
hour
or
something
like
that,
and
then
I
can
create
my
event
in
the
currently
connected
user
calendar.
In
a
matter
of
few
seconds,
you
will
see
the
new
event
popping
up
in
my
calendar.
We
can
wait
a
few
more
seconds
or
we
can
refresh
the
page.
G
Let
me
speed
up
the
process.
Let
me
refresh
the
page
just
for
the
sake
of
simplicity,
and
here
we
are
here.
We
have
the
sql
demo,
which
is
an
online
event,
so
I
can
even
join
it
and
start
contributing
to
this
demo,
which
of
course
I
will
not
do
otherwise.
I
will
stop
the
current
presentation.
So
how
can
we
do
that
again
back
to
the
code
base,
and
here
we
have
again,
the
adaptive
card
extension
is
like
as
before
we
have.
G
We
still
have
the
calendar
service
as
like
as
before,
but
right
now,
in
the
calendar
service,
we
have
the
create
event
method
in
the
create
event
method.
We
accept
a
subject
and
start
date
and
end
date
and
we
will
return
back.
The
event
object
that
we
created
here.
We
simply
need
to
create
an
event
object
based
on
the
definition
of
the
event
type
that
we
have
in
microsoft
graph
so
as
like
as
before.
G
We
have
the
main
properties
of
our
event
and
then
we
simply
need
to
still
use
the
graph
client
object
to
make
an
api
request.
For
me
slash
events,
but
this
time
it
will
be
a
post
request,
providing
the
actual
json
definition
of
the
event
that
we
want
to
create
in
order
to
collect
the
input
fields.
So
this
object
and
the
start
and
then
the
date
and
time
of
the
event.
We
have
a
quick
view.
G
In
the
quick
view,
we
still
have
the
capability
to
provide
a
data
object
when
we
create
the
when
we
render
the
quick
view.
But
what
I'm
interested
in
now
is
to
collect
input
from
the
user
and
that's
why,
in
the
definition
of
my
adaptive
card,
rather
than
having
the
text
blocks,
which
will
simply
render
content,
I
will
use
the
input
dot.
Something
controls
to
get.
For
example,
a
text
input
for
the
subject,
a
date
for
the
start
date
and
the
time
for
the
start.
G
Okay,
if
I
get
an
actual
invocation
for
the
action
with
id
submit,
which
is
the
button
pressed
in
my
quick
view,
let's
get
from
the
action,
the
data
property,
so
the
one
we
had
here,
the
one
we
defined
here
and
read
the
subject:
property
the
start
date
and
start
time,
the
end
date
and
that
time
so
that
I
can
build
the
input
for
my
create
event,
method
of
my
calendar
service,
and
I
can
simply
create
my
new
calendar
item
in
the
currently
connected
user
calendar.
So
again,
I
think
this
is
really
simple
and
straightforward.
G
You
simply
need
to
build
your
ui
using
the
adapter
card
syntax.
In
the
quick
view
you
collect
input,
you
use
the
on
action
and
then
you
rely
on
your
backhand
service
to
do
the
actual
creation
of
the
event
in
this
scenario,
using
the
microsoft
graph
and
just
to
give
you
an
idea,
I
saw
previously
in
one
of
the
previous
demos
someone
asking
a
question
about
how
it
will
render
in
the
ui
of
a
mobile
device.
G
Well,
if
you
want
to
play
with
the
ui
device,
you
can
easily
go
to
the
video
connection
dashboard
in
your
tenant.
You
can
switch
to
the
mobile
preview
and
you
will
be
able
to
see
how
your
adaptive
cars
will
behave
and
how
they
will
render
in
the
mobile
ui
of
an
hypothetical
a
smartphone
where
you
can
play
with
all
of
the
cars.
So
just
for
the
sake
of
completeness.
A
Great
stuff,
paulo
there.
Thank
you
very
much
for
that
demo.
I
think
it
really
shows
the
power
you
can
bring
to
these
adaptive
card
extensions.
That
can
look
deceptively
simple,
but
really
you
can
build
a
lot
of
power
there.
We
saw
creating
an
event
right
on
folks
calendars
from
an
adaptive
card,
so
really
exciting.
A
Think
about
all
the
possibilities
you
can
build
in
these
adaptive
cards
in
this
new
kind
of
experience,
so
definitely
encourage
folks
to
check
out
those
adaptive
card
extensions
if
you
haven't
yet
want
to
thank
all
our
demos
today,
siddharth
eaves
and
paolo.
Thank
you,
everybody
for
joining
our
call
this
week,
always
great
to
have
everybody
here.
Recording
will
be
available
in
24
hours
on
the
microsoft
365
community
youtube
channel
ak
dot.
Ms
slash
m365
pmp,
slash
videos.
You
can
of
course
subscribe
there
to
the
youtube
channel
to
get
all
the
latest
updates.
A
Our
next
viva
connections
and
spf
x
call
will
be
in
two
weeks
march
24th
at
the
same
time,
and
our
next
general
dev
call
will
be
next
week
next
thursday
march
17th
at
the
same
time,
and
then
don't
forget.
We
as
well
have
the
call
on
tuesday
march
15th
for
the
the
microsoft
m365
platform
call
all
our
community
calls
can
be
found
at
the
aka
dot.
Ms
m365
pnp,
link
and
as
well
are
here
are
links
to
all
of
our
upcoming
developer.
Calls.