►
From YouTube: Adaptive Cards community call-June 2020
Description
This month's call, hosted by Matt Hidinger, covered a Build 2020 recap and look at the roadmap. We then had MVP Hugo Bernier showcase an impressive and user-friendly SharePoint web part for hosting Adaptive Cards - with full templating support!
Resources:
About Adaptive Cards https://adaptivecards.io
Adaptive Card Host Web Part https://aka.ms/AA8qqhy
PnP https://aka.ms/m365pnp
Stay connected
Twitter https://twitter.com/microsoft365dev
YouTube https://aka.ms/M365DevYouTube
Blogs https://aka.ms/M365DevBlog
A
We'll
go
ahead
and
get
started
for
everyone
getting
the
recording.
If
your
calendar
series
expired,
go
to
that
link
that
you
found
it
from
AKMs,
slash
adaptive
cards,
community
call
and
we're
gonna
keep
going
so
we're
in
June,
we'll
see
in
July
and
as
long
as
you
keep
showing
up
I'll
keep
putting
these
together
and
data
will
continue,
making
sure
that
good
content
comes
through
and
blogs
follow
so
I'm
Matt
Heidegger.
A
A
Awesome,
thank
you
so
much
so
yeah.
So
that's
that's.
What
we're
gonna
talk
about
today,
a
build
2020
recap:
I,
do
have
an
update
on
the
ACMs
project
or
the
adaptive
card
management
service
project
that
you
may
have
seen
in
previous
months
and
then
hit
it
off
to
hugo
for
the
sharepoint
demo
and
integration
and
source
code
and
all
the
cool
things
for
those
of
you
who
are
integrating
into
sharepoint
okay.
So
with
that,
let's
kick
it
on
up
so
bill.
2020
went
on.
A
It
was
all
virtual
if
you
hadn't,
fought
along
there's
tons
of
great
content,
the
one
that
David,
Chloe
and
I
put
together
on
all
the
latest
adaptive
cards
can
be
found
at
this
short
link,
and
we
really
talked
about
these
sections.
So
we
talked
about
templating
adaptive
card
templating
and
some
some
pretty
great
designer
up
to
it's.
We
talked
about
adaptive
cards.
V2
is
the
first
time
we
ever
used
that
moniker
and
the
major
initiative
going
on
at
adapt
of
cards.
A
V2
is
this
concept
of
universal
actions
which
we'll
talk
about
and
we
concluded
with
a
road
map
that
landed
with
v2
and
v3
and
beyond.
The
only
thing
I'll
add
to
that
is
that
this,
the
card
management
service,
so
we'll
kind
of
go
through
that,
so
I
will
probably
go
quickly
through
this
and
hand
it
off
to
Hugo
and
we'll
obviously
have
time
for
Q&A,
especially
if
you've
seen
some
of
this
content
and
had
some
thoughts
on
it.
A
This
is
a
great
forum
again,
you
know,
even
if
you
have
clarifying
questions
along
the
way,
I'm
gonna
be
monitoring,
chat
and
so
will
Dana
and
there's
a
handful
of
people
from
the
adaptive
cards
team
on
here
as
well.
So
if
you
have
questions
along
the
way,
please
feel
free
to
add
them.
I
like
to
keep
these
things
casual,
I
hope
you
do
as
well.
So
with
that,
let's
jump
right
in
so
templating
and
designer
updates.
This
was
really
the
recap.
I'm
not
gonna
spend
any
time
actually
going
through
templating.
A
Strangely
one
thing
I
always
have
to
reiterate
to
folks
is
you
can
use
template
'day
if
you're
sending
cards
in
Outlook
actual
messages,
if
you're
sending
cards
into
teams,
if
you're
rendering
cards
templating
is
possible
today,
and
it
makes
it
easy
to
build
adaptive
card
payloads
with
dynamic
data,
you
create
an
adaptive
card,
all
the
way
back
to
say
1.0
and
your
back-end
or
your
server
or
whatever
power
automate,
whatever
you're
using
to
generate
cards,
and
then
you
can
send
them
to
teams.
So
it's
a
kind
of
common
misconception.
A
We
see,
like
you
know
when,
when
will
teams
have
templating,
which
is
a
fair
question
by
the
way,
and
we
get
into
like
our
our
v3
roadmap
templating
or
data
mining
will
be
actually
integrated
into
the
clients
like
teams
and
outlook,
but
until
then
you
can
absolutely
use
it
today.
If
you're
on
a
dotnet,
back-end
or
a
JavaScript
nodejs
back-end,
you
can
use
template
until
these
cards
up
and
send
things.
So
we
did
have
a
breaking
change
in
the
biting
syntax.
It
used
to
be
just
curly,
brace
now
it's
dollar
curly
brace.
A
We
did
that
to
a
line
with
other
common
binding
syntax.
It's
the
es6
language,
it's
it
just
seemed
a
little
more
common
and
it
was
a
little
easier
to
denote.
It
was
also
compatible
with
the
second
layer
that
we
introduced
called
adaptive
expression.
So
this
was
a
collaboration
between
our
the
adaptive
cards
team,
some
folks
on
my
group
and
then
the
bot
framework
team,
and
this
is
a
new
standard
for
writing.
Cross-Platform
AG
platform,
agnostic
expressions
that
can
be
evaluated
directly
on
multiple
platforms
and
there's
a
lot
of
potential
here.
A
So
Tim,
cotton,
Bach
I,
don't
know
if
he's
on
the
call.
There
was
a
thread
with
him
tomorrow
and
Lewis
on
Twitter
at
some
point
and
and
Tim's
been
promoting.
This
website
made
with
cards
IO,
where
he
has
done
some
neat
things
with
templating
and
expressions,
including
like
taking
an
array
of
data
and
like
filtering
it
and
sorting
it,
and
you
can
do
a
lot
at
the
expression
layer
that
is,
is
pretty
powerful
and
those
of
you
familiar
with
power.
Automate
you're
already
used
to
a
pretty
rich
expression
language
there.
A
It
should
be
fully
compatible
between
the
two
with
minor
changes.
I
think
power,
automate
uses
kind
of
an
@
symbol
to
break
out
into
the
expression
layer,
but
either
way
they
should
be
pretty
compatible,
and
you
can
do
some
pretty
expressive
stuff
building
a
template
which
really
becomes
powerful.
If
you
don't
have
the
opportunity
to
change
the
data
like
you
know,
if
you
get
data
in
the
form
of
a
current
like
a
decimal,
but
you
want
to
display
it
to
a
user
as
currency,
you
want
to
round
it
to
a
certain
amount
of
decimals.
A
You
maybe
want
to
do
some
basic
arithmetic,
arithmetic
to
it
or
like
math
functions
or
just
massage
the
data,
that's
where
the
template
can
get
pretty
powerful
and
really
massage
that
data
into
a
presentable
format.
With
that
the
adaptive
card
designer
got
a
bunch
of
updates
as
well
data
binding
improvements.
It's
really
easy
to
bind
to
your
sample
data.
There's
a
new
version,
selector
UI
in
in
the
designer
allowing
you
to
actually
here
I
can
quickly
pull
that.
A
A
That
could
be
a
wrong
assumption,
but
to
draw
awareness
is
something
that
has
existed
for
maybe
a
year
now
is
we
have
adaptive
cards
aya,
which
is
where
all
of
our
production
stuff
lives,
but
we
also
have
AV
next
dot
adaptive
cards
that
io,
which
just
lets
us
play
around
with
things
some
experimental
things,
and
one
thing
that's
really
neat
in
here.
If
you
switch
over
to
the
v-necks
designer
and
you
click
new
card,
it's
a
little
hard
to
discover
right
now.
A
You
actually
have
to
click
new
card
and
scroll
all
the
way
to
the
bottom
of
this
there's
this
create
from
image-
and
this
was
built
by
a
community
member
of
ours,
a
group
of
folks
from
Amazonia-
and
they
built
this
product
and
open
sourced
it.
So
it
is
in
our
github
repo
and
what
it
lets
you
do
is
upload
an
image,
a
bitmap
image
that
they
will
send
to
a
server
and
do
some
some
machine
learning
some
image
analysis,
some
OCR,
all
the
fancy
stuff.
A
You
learn
to
process
the
image
and
they
actually
create
an
adaptive
card
for
it
and
it's
pretty
cool.
So
these
are
a
set
of
sample
images.
You
can
upload
your
own
image,
but
these
samples
just
make
it
easy
to
demo
the
feature
and
then
I
click
convert
to
adaptive
card
and
what
that's
gonna
do
is
actually
analyze
this
image.
This
is
just
a
PNG
image
could
have
been
generated
from
anything
coming
from
the
internet.
Whatever,
and
what's
really
neat
about
this?
Is
it
pulled
out?
A
The
text
set
it
to
a
color
pulled
out
that
image
horizontally
aligned
it
to
the
center.
It
also
no
is
that
these
look
like
radio
buttons
those
circles,
so
it
analyzed
the
image
and
said
those
actually
look
like
radio
buttons.
So
it
turns
those
into
an
adaptive
card.
Choice
set
set
configured
to
basically
be
one
option.
Only
so
pretty
neat,
it
really
just
gets
you
started.
You
know
the
the
hope.
A
Maybe
you
don't
have
to
learn
everything
about
the
adaptive
card.
Designer
is
kind
of
the
hope
there.
So
I
thought.
That
was
a
really
cool
addition.
That's
currently
I'm
v-necks
cuz.
It's
not
quite
you
know,
production
ready,
but
you
can
play
with
that
there
and
one
nice
thing
added
to
the
designer
is
this
version
selector
drop-down,
when
this
loads
up?
A
So
if
you're
currently
targeting
say
outlook
desktop,
which
supports
1.0
of
the
schema
you'll
get
these
warnings
if
you
use
features
that
were
introduced
later
on
in
1.2,
for
example,
and
like
the
toolbar
element,
the
card
element
toolbar
filters
itself
to
only
show
things
that
were
available
in
1.0.
So
your
note
notice
media
is
missing.
Rich
text
block,
so
it
just
makes
it
so.
The
designer
helps
you
create
cards
that
are
actually
compatible
with
the
host
you'll
be
going
to
you
and,
as
you
changed
a
different
host,
we
will
set
this
drop
down
accordingly.
A
A
So
the
next
thing
was
a
tappa
cards
v2
and
again
because
templating
lives
outside
you
can
use.
Templating
today
works
with
adaptive
cards
today.
Adaptive
cards
v2
is
our
first
major
addition
to
the
platform
itself,
the
adaptive
card
platform,
if
you
will
the
introducing
a
concept
of
a
transport
protocol
and
in
a
standardized
action
model,
and
those
of
you
who
happen
to
write
cards
for
maybe
teams
and
outlook,
will
be
very
aware
of
this.
Current
I,
don't
want
to
say
limitation,
but
it's
it's
extra
work.
A
A
So
there
were
two
different
models
that
each
had
pros
and
cons,
and
the
major
benefit
that
we're
doing
in
v2
is
a
universal
standardized
action
model.
So
it'll
be
a
new
action
type
called
action,
dot
execute
it
will
handle
I
only
grabbed
some
of
the
slides.
So
if
any
of
this
is
interesting,
I
would
recommend
just
going
back
to
the
build
talk
where
you'll
get
more
deep
dive
on
all
this
I'm,
really
just
trying
to
summarize
a
lot
of
it
here.
A
But
the
nice
thing
is
now
you'll
have
a
standardized
way
of
communicating
back
to
a
back-end.
It
also
has
the
ability
to
refresh
the
card
on
arrival.
So
you
know
this
is
great.
If
you
want,
you
know
the
card
to
stay
up
to
date
at
a
certain
C
once
and
there's
a
whole
bunch
of
stuff
going
on
in
the
the
auto-refresh
world
that
we're
still
figuring
a
lot
of
this
out.
So
this
is
one
of
those
things
that
I
would
say
stay
tuned.
The
build
announcement
was
a
very
early
sneak
peek.
A
This
will
come
and
be
available,
potentially
at
a
preview
by
the
end
of
the
year,
but
released
as
early
as
we
can
into
into
next
year.
The
back
backend
of
this
is
going
to
be
a
bot.
The
easiest
way
to
write
a
bot
for
bot
framework
is
to
just
install
the
SDKs
if
you've
already
written
about
it'll
make
it
extremely
easy
for
you
to
now
handle
calls
from
Outlook
a
lot
of
additions
were
made
not
only
just
standardizing
on
the
communication
model
back,
but
also
responding,
as
in
you
know.
A
Typically,
if
I
click
on
a
button-
and
it
approves
something
you
know
the
card-
will
gray
out
and
show
the
cursor
it'll
communicate
with
your
server.
Your
server
will
get
all
the
authenticated
state
who's.
The
person
clicking
it
a
trusted
communication
to
your
back-end
and
you
can
respond
with
a
new
card.
So
what's
the
latest
state
of
the
card
and
refresh
it
in
a
nice
way,
so
a
lot
of
progress
towards
like
okay?
How
do
we
actually
communicate
this
front-end
with
a
with
a
back-end,
so
encourage
you
to
learn
more
about
that?
A
We'll
have
plenty
of
share
on
this.
As
the
year
goes
on,
and
the
last
topic
is
I've
been
calling
it
card
author
services
I'm,
not
sure
if
the
name
sticks
or
where,
where
we're
gonna,
officially
brand
it
I
guess:
I
have
Dana
and
I
see
Ben
on
the
call.
I
should
probably
reach
out
to
them
and
use
their
marketing
expertise
to
figure
out
what
the
heck's
we
name.
This
thing,
you
might
remember
it
as
the
adaptive
card
management
system,
so
we
had
a
set
of
interns
for
through
April,
March
and
February
fantastic
group
of
interns.
A
I
definitely
missed
them
dearly
and
they
worked
on
this
project
that
made
it
easy
for
organizations
and
people
to
just
collaborate
on
a
set
of
cards.
So
a
very
rich
front-end
that
let
you
login
config
your
authentication.
However
you
want.
This
is
a
service
that
you
would
host
yourself.
So
if
you're
a
business
somewhere-
and
you
know
you
would
basically
install
this
SDK-
deploy
it
to
a
sure
AWS
your
own
server
to
play
it.
A
However,
you
want
and
can
figure
out
that
occasion
and
then
people
can
log
in
and
create
cards
card
templates
for
any
types
of
things,
and
then
there
would
be
a
back-end
library
that
would
make
it
easy
to
fetch
the
cards
from
that.
So
rather
than
pasting,
you
know
if
you're
a
developer
using
cards
today,
you
might
go
to
our
designer
create
a
card.
A
You
know
looks
like
this
and
then
you've
got
all
this
JSON.
So
what
do
you
do?
Do
you
just
copy
it
put
it
in
a
variable
somewhere?
Do
you
store
somewhere,
like
we
kind
of
leave
it
up
to
each
developer,
to
figure
out?
What
do
you
do
with
this
JSON
with
the
CMS,
which
is
here
and
I?
Guess,
I'll
just
log
into
this
real
quick,
there's
a
very
nicely
integrated,
front-end
portal,
where
I
can
just
click
on
new
card.
The
designer
is
integrated.
A
I
always
like
to
take
this
opportunity
to
mention
to
people
that
the
designer
the
adaptive
card
designer
itself
is
a
component,
so
you
can
install
it.
You
can
embed
it
in
your
own
apps,
just
head
to
NPM
and
just
look
for
the
adaptive
cars
designer
and
you
can
install
this
package
and
that's
exactly
what
the
interns
did.
A
So
I've
got
a
card
here
and
I
can
click
Edit
in
designer
it
loads
up
the
designer
loads
up
the
card
I
can
make
changes
to
it
and
just
say
you
know,
hello,
community
call
hit,
save
and
then
either
publish
it
or
whatever,
and
if
I
publish
it
what's,
neat
and
I
can
share
it.
All
that
all
the
things
you
would
kind
of
expect
you
know
if
an
organization
is
collaborating
on
cards,
maybe
you
have
non
developers
working
on
these.
A
It's
we're
slowly
getting
to
the
point
where
it's
we
want
it
to
be
so
user
friendly
that
anyone
can
create
you
I,
create
actionable
UI
and
a
developer,
who
may
have
to
hook
it
up
to
logic
or
use
power
automate
to
do
something
with
it.
We
can
really
start
to
empower
all
folks
all
roles
throughout
an
enterprise
or
an
industry
to
really
start
democratizing.
A
lot
of
this
stuff,
like
just
I've,
got
this
card.
A
I
want
to
get
to
people,
and
so
that's
what
this
project
is
so
the
update
there
is
we've
got
some
people
working
again.
We
weren't
sure
how
we
were
gonna
continue
working
on
it
once
the
interns
left,
we
did
hire
a
couple
of
vendors
to
work
on
it,
not
for
long
really
just
a
short
amount
of
time
just
to
get
it
so
it's
works.
A
Anyone
can
install
it,
I've
done
demos
of
it,
but
if
any
of
you
have
gotten
excited
and
tried
to
install
it
yourselves,
you
no
doubt
hit
some
some
hurdles,
and
so
we're
really
just
polishing
that
up
and
that
that
effort
just
kicked
off.
So
that's
kind
of
hot
off
the
presses,
but
the
good
news
is:
we've
got
a
plan
now
where
we
can
not
quite
get
it
like
release,
quality,
full
compliance
and
all
the
things
that
has
to
happen
to
go
GA,
but
definitely
do
a
point
where
you
can.
You
can
use
it
reliably.
A
So
that's
a
that's
a
pretty
exciting
development
that
happened
since
build
and
then
it
really
closed
this
off
and
then
I'll
hand
it
over
to
Hugo.
This
is
what
our
road
map
looks
like
in
kind
of
these
block
diagrams,
or
it's
it's
a
somewhat.
It's
probably
a
lot
to
look.
I've
looked
at
this
so
many
times
I,
just
you
know,
I
can
see
the
matrix
I,
don't
know
how
confusing
this
looks
to
you
folks.
A
But
the
way
I
like
to
summarize
this
is
adaptive
cards
functions
on
really
five
verticals,
the
the
things
we
want
to
deliver.
So
we
help
with
rendering
right
it's
a
cross-platform
rendering
layer
and
in
that
world.
What
we're
doing
in
this
year
is
closing
accessibility,
we're
making
strides
on
really
making
cards
fully
accessible.
It's
an
important
thing
to
do
and
we're
all
learning
how
to
do
that
well
and
learn
efficiently
and
and
just
do
it
on
every
platform.
A
So
that's
a
major
initiative
if
you've
been
blocked
on
your
rollout
of
adaptive
cards
due
to
any
accessibility
stuff
know
that
we've
got
your
back
there
and
we're
working
to
close
that
throughout
the
year.
Input
validation
is
our
biggest
feature
coming
at
the
rendering
layer,
so
this
will
be
client-side
validation.
So
if
you
have
a
couple
inputs
on
your
card
and
they're
required,
you
will
be
just
able
to
say
they're
required
if
it's
a
text
input
you'll
be
able
to
provide
a
regular
expression
to
say
this:
is
the
format
I
want
it
in?
A
If
it's
you
know
a
choice
set
and
things,
and
so
there's
that's
a
great
improvement.
It's
by
far
our
highest
requested
feature
we're
making
progress.
You
could
actually
follow
along
the
pull
request
in
github
and
it
wants
a
link
to
that
if
people
are
curious,
we're
looking
to
get
a
preview
of
that
out
in
July.
So
pretty
soon-
and
that's
just
you
know
great
news
for
folks
that
have
been.
You
know
you
have
cards
that
are
collecting
data.
A
We
also
want
to
get
into
glyphs
I'm,
not
gonna,
say
much
here,
because
I
don't
have
a
high
confidence
that
we'll
be
able
to
figure
it
out.
It's
mainly
a
licensing
thing,
so
I'm
not
really
gonna
break
into
that
one
right
now
and
we've
also
got
a
handful
of
platforming
consistencies
that
were
just
addressing
just
making
sure
that
some
people
have
gotten
really
creative
with
their
cards
done
some
really
advanced
things,
particularly
since
1.2
and
there's
just
a
couple
platform
just
in
differences.
A
Some
API
extensibility
point
differences
that
we're
just
looking
at
kind
of
button
up
some
of
that
stuff.
So
that's
what's
happening
at
the
rendering
layer.
Then
we
have
the
action
layer.
So
what
happens
when
you
click
a
button,
and
for
that
we're
making
lead
way
through
2020,
like
I
said
you
can
expect
a
preview
of
the
universal
action
stuff
this
year
with
final
release
in
2021
and
that's
what
I
mentioned
is
our
2
dot
X?
A
So
what
you'll
start
to
see
over
time
is
that
these
independent
these
these
kind
of
horizontal
lines
they
start
to
converge.
As
we
start
to
see
well,
what
is
it
out
of
cards
to
dot?
Oh
look
like
what
is
2
dot,
X
look
like
and
in
2
dot,
X
we're
really
rendered
we're
combining
the
rendering
and
the
action
stack,
and
that
will
really
make
up
what
we
what
we
call
to
dotto
yeah
into
a
unified
SDK
on
all
platforms.
Universal
actions
will
just
work.
A
The
rendering
stuff
will
continue
to
work
and
you'll
start
to
see
that
into
auto
templating
will
still
exist
as
standalone
and
the
main
benefit
there
is.
You
can
use
it.
You
can
use
it
with
2.0.
You
can
use
it
with
one
auto.
You
can
use
it
with
0.5.
You
can
use
templating
today
a
separate
thing,
so
we've
released
the
release.
Candidates
of
dotnet
JavaScript
we'll
be
releasing
those
RTM
within
the
coming
weeks.
So,
if
you've
been.
B
A
For
templating
to
exit
preview,
that's
coming
very
soon.
If
you
haven't
gotten
started
with
the
release
candidate,
please
do
we're
getting
some
fantastic
results
from
some
early
adopters.
It's
ready
to
go.
We
just
want
to
make
sure
we're
not
missing
anything
obvious
and
the
release
candidate.
So
if
you've
been
using
the
preview,
please
do
let
us
know
so.
Like
I
said,
templating
SDK
is
available
for
data
and
JavaScript,
and
then
in
and
we're
just
now.
A
Gonna
start
working
soon
on
the
templating
SDKs
for
the
mobile
platforms
and
that'll
get
interesting
very
soon
and
I'll
explain
why
we've
also
got
the
card
designer
that
you've
seen
the
version.
Selector
templating
support
and
we
assume
there's
gonna,
be
some
stuff
moving
forward,
but
we're
pretty
happy
with
the
designer,
as
it
is
right
now
and
then
card
author
services,
we're
getting
it
to
a
stable
state
where
you
can
install
it
and
use
it
in
2020,
and
you
can
expect
that
to
release
in
2021
and
that's
again
that
that's
CMS
now
to
wrap
this
up.
A
I
did
want
to
give
you
a
look
at
what
we
consider
3.0
and
so
I
mentioned
in
to
dotto.
We're
gonna
combine
rendering
and
actions
in
3x.
What
you
can
expect
is
the
combination
of
rendering
Universal
actions
and
live
data
binding,
and
this
basically
takes
our
template
anguish,
which
currently
exists
as
a
standalone
feature
and
if
integrating
it
tightly
into
the
rendering
layer
so
that
data
binding
can
happen
directly
on
a
device
that
you're
on
directly
on
an
iPhone
directly
in
teens.
A
A
You
can
have
the
templates
separate.
We,
it's
really
I,
think
an
open,
a
lot
of
potential
for
innervation
innovation
from
from
folks
on
your
end,
okay,
30
minutes-
that
was
a
quick,
quick
ish
summary
I
will
go
through
some
questions
and
Hugo.
This
is
where
I'm
gonna
go
ahead
and
hand
it
off
to
you.
So
if
you
want
to
take
over
sharing.
B
Thank
you
so
much
hi
everyone.
My
name
is
hugo
Bernier.
My
company
is
tae
ho
ninjas,
and
this
is
a
picture
of
me
when
I
used
to
have
a
lot
of
hair.
I
can
be
reached
at
twitter
at
Bernier
at
bernie
age
and
my
blog
style
ninjas,
that
blog
I
am
a
Microsoft
MVP,
as
we
mentioned
before,
but
I'm
also
a
proud
member
of
the
patterns
and
practices,
a
virtual
team,
and
so,
if
you've,
if
you
haven't,
had
a
chance
to
visit
the
patterns
and
practices
site,
there's
all
sorts
of
resources
around.
B
You
know
tools
SDKs
and
things
like
that
that
you
can
use
in
your
own
solutions.
Around
Microsoft
365
development
I
put
the
QR
code
there
in
the
corner
in
case
you're
interested.
But
the
other
thing
that
I'm
part
of
is
something
called
D.
It
started
as
a
Toronto
citizen,
developer
user
group,
but
we've
just
renamed
it.
The
this
is
a
developer
user
group.
Our
focus
was
to
create
you
know
a
group
that
is
not
about
selling
products
to
people
and
it's
not
really
intended
for
the
for
the
geeks.
B
How
do
we
empower
PSA's
and
developers
and
organizations
without
creating
shadow
IDs,
so
we
meet
the
first
Wednesday
of
every
month
and
the
URL
is
at
the
bottom
here:
TC
Doug
comm
and
while
the
primary
focus
has
been
around
the
power
platform,
we
consider
and
I
hope
everyone
to
call
agrees
that
we
consider
adaptive
cards
absolutely
a
citizen
development
resource
and
that's
where
the
idea
for
this
web
part
came
came
about
so
the
web
part
that
you're
going
to
see
today
is
actually
a
sample.
That's
already
published
and
the
repository
put
the
QR
code
there.
B
The
URL
is
way
too
long
for
me
to
even
say
it.
If
you
are
looking
for
that-
and
you
can't
remember
the
URL
just
remember
to
go
to
aka.ms/offweb
parts
again.
The
QR
code
is
there,
and
so
this
is
actually
a
site
that
we
built
that
allows
you
to
find
also
two
samples
for
SharePoint
web
parts.
Using
the
SharePoint
framework
and
there's,
as
you
can
see,
there's
all
sorts
of
samples
angular
react
everything
and
the
the
web
part
that's
highlighted
in
green.
B
There
is
the
web
part
that
we're
talking
about
and,
as
you
can
see,
it
was
changed
very
recently
as
early
as
well
today
and
that's
what
I'll
be
showing
you
today
so
before
I
start
I
want
to
say,
I
want
to
thank
a
couple
people
that
the
sent
me
messages
as
or
open
issues
as
early
as
twenty
one
hours
ago,
to
tell
me
that
the
sample
web
part
that
I
had
created
and
polyphen
also
created
a
version
of
this
web
part.
They
were
broken
or
more
specifically,
the
adaptive
card.
B
Template
component
was
broken
because
of
the
May
20
2008,
so
I
I
fixed
it
at
the
last
minute
last
night,
I
must
admit
that
it's
a
total
hack,
my
fix
but
I
do
plan
on
updating
as
soon
as
there's
an
updated
NPM
package.
I
will
update
the
the
adaptive
card
templating
functionality,
but
you
can,
you
can
use
the
new
adaptive
card
templates.
It
mostly
works
right
now,
but
you
could
also
use
the
the
old
adaptive
card.
Template
schema
all
right.
Let's
show
you
the
web
part
to
get
started.
B
So
this
is
a
SharePoint
framework
web
part
and
it
was
totally
built
as
an
example
on
how
to
use
adaptive
cards
in
SharePoint.
This
is
not
really
intended
for
for
to
be
used
in
production,
although
if
you,
if
you
choose
to
do
that,
you're
more
than
welcome
to
do
so,
what
we
did
do,
though,
behind
the
scene
is
that
I
created
a
adaptive
card
component,
a
react
component
that
you'll
be
able
to
use
in
your
own
web
parts
and
the
component.
B
A
B
We
really
wanted
to
make
this
as
easy
as
possible
for
for
people
to
use.
So
let's
get
my
first
sample
I.
Believe
that's
the
red
one
and
we've
made
it
easy
here
for
you
to
edit
with
some
syntax
highlighting
and
if
I
paste
that
and
the
demo
gods
are
with
me.
This
should
be
working.
Yes,
it
does
work,
okay,
great
and
while
we're
there,
let's
just
show
you
how
we
can
actually
use
if
I
edit,
the
section
here
and
I
change
the
background.
B
Well,
it's
probably
not
a
very
exciting
demo
here,
but
the
background
is
designed
to
react
to
to
changing
themes.
You'll
notice,
there's
a
little
I
have
a
little
issue
here
with
the
highest
contrast.
The
strong
contrast
backgrounds
with
the
the
buttons
are
actually
the
same
color
as
the
background.
This
is
something
I'd
love
to
talk
to
someone
in
the
adaptive
card
game
to
to
align
the
themes
so
that
we
can
do
something.
That's
a
high
contrast
and
good
for
accessibility,
and
that
webpart
also
works.
B
Okay,
let's
continue
the
other
thing
that
I
can
do
again.
I've
got
some
other
samples
here,
so
let's
use
sample
with
data
because
we
do
support
adaptive
card
templating
and
what
we
do
here
is
we
detect
if
you're
using
adaptive
card
templating,
we
just
kind
of
tried
to
help
you.
So
if
you,
if
you're
using
this,
we
say,
turn
on
adaptive
card
templating
and
then
from
this,
what
we've
done
is
we've
actually,
given
you
the
option.
Pick
data
from
JSON
pick
data
from
a
list
on
your
SharePoint
site
or
pick
data
from
a
URL.
B
We
are
planning
on
adding
things
like
dynamic
data
sources.
You
know
so
that
we
can
have
dynamic
data
from
other
webparts,
but
let's
just
start
with
getting
some
data,
and
let
me
know
if
I'm
going
too
fast,
I
hope
that
everyone
can
see.
My
screen
I
do
like
my
resolution
to
be
really
high.
It's
like
four
thousand
by
three
thousand,
so
I
had
to
zoom
in
a
lot
to
prepare
for
this
to
home.
So
after
everything
goes
well-
and
you
know,
Matt
you're,
like
the
the
adaptive
card
equivalent
of
hello
world
right.
A
B
Right,
so,
if
I,
if
I
just
prove
that
I'm
not
lying
here,
I
just
changed
the
data
and
I
think
I
copied
it.
This
is
a
picture
of
Paul
I.
Think
Paul's
in
the
call
I
want
to
shout
out
to
Paul,
because
Paul
actually
took
this
simple
web
part
that
I've
created
and
he
really
quickly
created
a
react
hook,
version
of
the
exact
same
web
part,
and
so,
if
you're
interested
in
learning
about
react,
hooks
and
understanding.
What's
the
difference
between
a
react
and
react,
hooks
great
thing
to
do
is
just
go.
B
Alright,
let's
go
look
another
example
here.
So
if
I
changed
my
template
here,
ooh
something
really
boring
I
was
not
I.
Didn't
have
a
lot
of
inspiration
when
I
created
this
sample
template
here,
you
can
actually
go
pick
from
a
list
and
you
can
get
a
data
and
that's
kind
of
hard
to
show
here
at
this
resolution.
But
it's
actually
getting
me
a
list
of
all
that
I'm
gonna
zoom
a
little
bit
so
I
can
I
can
show
you
this.
B
B
You
know,
there's
in
SharePoint,
you
have
the
ability
to
use
list
formatting
and
view
formatting
to
do
pretty
much
the
exact
same
thing,
but
if
you
were
inspired
and
you
wanted
to
create
a
crazy
template,
you
know
that
at
some
point,
you'll
reach
the
limitations
of
what
list
and
view
formatting
is
capable
and
SharePoint,
but
you
can
absolutely
do
it
using
adaptive
card
templating.
So.
B
You
have
a
better
imagination
than
I
do
when
it
comes
to
to
creating
templates.
Alright,
anybody
want
to
see
some
code,
so
I
actually
took
screenshots
of
the
code,
because
demoing
code
and
Visual
Studio
code
is
always
painful.
I'm
gonna
try
to
go
as
quickly
as
possible.
Again,
if
you
have
any
questions
about
this
feel
free
to
reach
out
to
me.
But
let's
get
started.
First
thing
is
in
the
project
itself:
I've
created
the
web
part
called
adaptive
card
Post
web
part.
B
B
So
the
first
thing
that
we
do
in
this
web
part
is
we
actually
make
the
web
part
theme
aware
by
giving
it
a
theme
provider
and
by
getting
the
theme
variant
from
the
header,
and
then
we
subscribe
to
an
event
so
that
when
people
change
the
themes
or
the
change
of
background
colors,
the
web
part
is
automatically
notified
and
it
just
makes
the
web
part
redraw.
And
then
we
just
when
we
call
the
adaptive
card
host
component,
we
just
pass
it
the
theme
variant
and
the
component
will
take
care
of
of
applying
the
themes.
B
Another
thing
that
we
do
in
this
web
part
is
that
anything
that's
intensive
in
terms
of
resources
like,
for
example,
we
have
the
code,
editor
property
pane
that
shows
up.
You
probably
don't
want
to
load
that
every
single
time
someone
is
looking
at
a
web
part,
especially
if
they're
just
looking
at
it
in
View
mode,
not
edit
mode.
So
there's
this
feature
in
SharePoint
framework
that
allows
you
to
defer
loading
the
resources,
your
property
pain,
needs
to
only
when
you
need
to
display
the
property
pain,
it's
a
kind
of
crazy
idea,
but
it
works
perfectly.
B
So
that's
what
we
do
here
is
we
just
kind
of
do
import
the
code
editor
in
this
case,
and
we
only
do
that
when
you
display
the
web
part
and
then
we
just
set
that
in
the
property
pane
now,
the
component
itself
is
really
what's
responsible
for
rendering
the
body
of
the
web
part.
So
the
adaptive
card
host
at
PS
X,
is
where
the
logic
for
rendering
the
what
you
saw,
and
you
know
what
we
do
is
we
actually?
If
we
need
a
template,
we
use
the
the
PNP
reusable
control,
placeholder
component.
B
That
will
tell
you
hey.
You
need
to
give
us
a
template.
If
we
need
the
data,
we
do
the
same
thing
we
say:
hey,
you
selected.
You
want
to
use
adaptive
card
templating
with
you
didn't
give
us
data
yet
so
please
give
us
that
and
then
this
is
really
where
all
the
hard
work
gets
done.
This
is
the
component
that
that
we
built
that
is,
is
really
wrapper
around
the
adaptive
card
NPM
packages,
but
it's
it.
It
is
designed
to
work
with
in
SharePoint.
So
it
takes
the
template
JSON.
It
takes
the
data.
B
It
takes
a
flag
whether
we
use
templating
or
not,
and
it
takes
a
theme
variant,
but
the
other
thing
that
does
is
it
actually
will
bubble
up
any
action
element
in
the
adaptive
card.
So
if
someone
clicks
on
a
button
or
a
link
or
something
like
that,
your
the
web
part
that
is
calling
the
CUDA
component
will
actually
get
notified
and
you
can
do
whatever
you'd,
like
with
that.
B
So
in
the
adaptive
card,
control
and
misses
again
to
control
that
we've
designed
for
you
to
embed
it
it
in
your
own
web
parts.
If
you
want
to-
or
you
can
use
the
web
part
that
I'm
demoing,
we
do
a
few
things.
So
the
first
thing
is:
we
use
the
adaptive
card,
and
now
this
is
this
is
really
stressful,
because
I
get
Matt
on
the
call
and
he's
probably
looking
at
my
code
saying
what
were
you
thinking
so
we
create
the
adaptive
card.
B
You
say
these
are
the
colors
that
we
need,
and
so
there's
a
there's
a
few
sections
for
example,
as
you
can
see
here,
reg
here.
Well,
it's
not
letting
me
highlight
so
we'll
just
we'll.
Just
keep
that
for
now
this
part
here.
For
some
reason,
it
was
unable
to
grabbed
a
success
text
from
from
the
SharePoint
context,
but
you
know
in
general
the
theme
works
again.
B
We
do
some
have
some
issues
with
the
the
button
color
being
the
same
color
as
the
background
color
in
high
contrast,
environments
but
I'm
sure
it's,
it's
probably
a
matter
of
something
I
didn't
know
how
to
fix,
and
then
the
other
thing
that
we
had
in
this
in
this
component
is
we
had
done
a
property
field
view
picker
that
was
responsible
for
picking
the
view
from
your
list.
For
me,
a
document
library
we've
since
then
actually
taken
this
out
of
the
code
sample
and
we've
actually
moved
it
as
a
PNP,
reusable
control.
B
So
the
PNP
reusable
controls,
if
you
haven't
used
that
yet
you
can
go
to
this
long
URL
here
or
you
can
again
go
to
the
aka
that
ms
/m
365
PNP,
where
all
the
PNP
initiatives
are
listed.
But
this
is
a
library-
or
this
is
a
packaged
story
that
you
can
add
in
your
SharePoint
projects
to
use
all
sorts
of
controls,
and
you
know
but
wait
if
you
order
now,
you'll
also
get
in
the
in
the
future.
In
the
near
future.
B
I'm
planning
on
publishing
the
adaptive
card
control
for
SharePoint
that
you
just
saw
inside
a
web
part
I'm
planning
on
posting
it
as
a
PNP,
reusable
control.
So
for
you
to
to
use
adaptive
cards
in
your
SharePoint
projects,
you
want
to
have
to
copy
the
code.
You'll
just
use
the
PNP
library
using
the
package
command
here,
I'm
totally
planning
on
updating
this
webpart.
Well,
of
course,
as
soon
as
I
can
do
a
permanent
fix
for
adaptive
card
templating
I
will
do
that,
but
in
in
plans
are,
is
to
add
access
to
the
service.
B
Also,
our
intention
was
to
add
the
card
editor
right
into
the
web.
Part
and
I
totally
dig
the
creating
a
card
from
an
image,
so
I
might
have
to
borrow
that
and
put
that
in
the
web.
Part
I'm,
always
looking
for
ideas
and
inspirations.
The
the
goal
here
is
to
create
something
that
will
be
useful
for
the
community.
So
if
you
have
any
feedback,
please
don't
hesitate
to
reach
out
to
me.
That's
pretty
much
it
for
me.
Matt.
If
you
ask
questions.
A
That's
awesome,
yeah
I'm
glad
you
covered
the
end
about
just
yeah,
making
a
reusable
control.
I
think
that's
a
that's
cool
I,
particularly
loved
the
thorough
attention
to
detail
you
put
to
walk
people
through
it,
for
example,
detecting
when
it
looks
like
a
template.
The
configuration
options
were
great,
including
the
additions
Paul
made
to
load
from
URL
I
mean
that
was
a.
It
looks
like
a
pretty
solid,
thorough
user
experience.
Thank.
A
We'll
just
open
it
up
to
questions
I
want
to
draw
attention
to
this
made
with
cards
I.
Oh,
so
some
folks
asked
you
know
there
are
a
community
collection
where
people
can
put
some
cards,
how
they're
using
them
so
Tim
cotton
Bach,
who
has
been
a
longtime
supporter
and
innovator
I
guess
within
our
community,
made
this
website
made
with
cards
IO
and
that's
really
its
point.
You
can
submit
entries
here.
A
A
This
is
like
a
really
great
stab
at
a
Community.
Supported
and
community
run
things.
So
if
this
is
something
that
interests
you
I'd
say
get
in
touch
with.
Tim
he'll
probably
end
up
talking
about
this
next
month.
Once
he
gets
it,
a
little
more
polished
ready
to
go,
but
this
is
really
where
we're
hoping
to
kind
of
foster
a
grassroots
kind
of
community
thing
for
helping
other
card
people
or
card
users
be
successful.
So
with
that
said,
yeah
any
questions,
I'm
gonna
go
through
the
list.
A
A
B
A
A
B
C
I
support
the
the
question
on
trouble.
Messages
I
think
it
was
about
where
to
find
examples.
So
I
don't
have
the
URL
with
me,
but
we
have
a
set
of
labs
as
they're
called
that
are
available
on
the
document
that
are
available
on
github
and
also
very
thoroughly
documented.
So
I'm
gonna
try
to
pull
the
that
URL
and
just
paste
it
in
in
the
chat
right
here.
Okay,.
C
A
A
Folks
too,
get
that
there
they're
doing
some
evolving
I
guess
of
the
way
they
integrate
with
the
designer
and
I
think
I'm,
sorely
somewhat
speaking,
off-the-cuff
right
now,
but
I
think
the
hope
is
to
make
it
a
little
more
compatible
with
the
new
template
language
that
we've
we've
just
announced,
as
well
as
the
expression
layer,
so
I
think
we're
doing
some
tweaking
there
and
I
have
to
imagine.
The
hope
is
that
once
we
have
that
figured
out,
will
you
know
it
won't
be
team.
A
Specific,
certainly
long
term
will
make
it
very
easy
for
you
to
send
custom
adaptive
cards
to
Outlook
as
well,
but
I
don't
have
anything
confirmed
yet
so,
nor,
as
the
question
regarding
cards
and
team's
conditional
show
and
fill
for
the
text
area,
so
I
think
you're
asking
about
client-side
conditional
Show.
So
when
a
choice
set
is
like
other,
please
specify
I
think
you
want
a
text
box
just
show
up
and
unfortunately
that
doesn't
work
at
this
time.
A
The
templating
is
a
purely
kind
of
one-time,
server-side
Senate
thing,
but
that
is
something
that
will
absolutely
be
possible
once
we
add
the
real-time
data
binding,
more
client-side
stuff
there
so
definitely
stay
tuned.
That
is
a
very
key
scenario.
We
hope
to
add
support,
form
and
real,
quick,
while
I'm,
showing
that
I'll
I'll
have
these
resource
links
here.
I
think
they
were
all
in
the
chat.
Thank
you.
A
Everyone
for
sending
these
links
into
chat
there
are
other
community
calls
that
we
more
than
you
know
it
as
much
as
you
want
to
keep
joining
us,
we'll
we'll
keep
talking,
I,
think
and
keep
engaging
with
you
so
check
out.
These
other
calls
I.
Think
yeah.
You
can
find
these
calls.
You
know
at
the
m3
65
developer
YouTube
channel,
so
this
will
be
online
there.
The
next
call
will
be
at
January,
9th
at
9:00
a.m.
it's
always
the
second
Thursday
of
the
month.
So
please
do
come,
join
us
again
in
July
and
I'll
just
add.
A
I
know
we're
wrapping
up
and
people
are
head
now,
but
Hugo
thanks
a
ton
for
for
showing
that
I
know.
It's
been
highly
requested.
Anyone
else.
If
you
have
Hugo
just
emailed
me,
he
just
you
know
in
my
email-
is
I,
try
and
be
available
to
folks.
So
if
anyone
wants
to
show
things,
let
me
know
and
we'll
do
our
best
to
see
what
we
can
accommodate.
So
you
know
again
I
like
to
keep
these
things
casual
and
certainly
if
we
can
highlight
folks
some
work
that
you
folks
are
doing
we'd
love
to
do
that.
C
A
Yeah
that'd
be
great.
If
we
can
talk
I
know,
it's
come
up
in
high
contrast
and
things
so
yeah.
Please
do
reach
out
to
us
last
question
and
I.
Don't
know
if
we'll
be
able
to
get
to
all
these,
so
I
might
after
a
try
and
reach
out
to
folks
automated
testing.
We
don't
have
any
strong
guidance
on
automated
testing
at
this
point.
It
is
something
we're
starting
to
look
at
at
our
at
our
end.
A
B
A
So
you
might
be
awaiting
a
while
on
that
one
I
mean
we're
currently
calling
it
2021
plus
we're.
You
know,
I
write,
I
was
gonna,
say
you
know,
write
me
and
I
can
write
our
bosses
I
think
we
have
a
good
plan.
We
just
you
know
it's
it's
just
what
what
resource
and
what
can
we
do
with
with
the
devs
that
we
have?
Basically
so
I
would
say.
Hopefully,
we'll
have
plenty
to
share
as
we
get
executing
on
the
universal
actions
plan
and
that'll
be
our
next
major
initiative
Rea
after
that.
B
The
Refresh
option,
in
version
1.1
point
du
or
something
yeah,
yeah
version
version
2.0.
As
I
said,
we
were
really
planning
on
leveraging
all
the
capabilities
of
adaptive
cards,
because
it's
such
an
amazing
initiative
like
the
card
designer
and
the
services
and
all
that
stuff.
But
that
seems
like
something
that
we
could
do
pretty
quickly:
cool.
A
Awesome
I'm
gonna
try
and
get
the
wrong
question
so
as
adaptive
card-present
for
angular
8,
we
don't
have
any
native
angular
test,
decays
or
and
okay
David's
answering
that
yes,
so
the
JavaScript
runners
should
work.
How
close
that
gets
is
is
really
yeah.
If
you
have
any
issues
do
do.
Let
us
know
I
mean.
C
Yeah
we
we
do
not
have
a
story,
we
didn't,
we
do
not
have
a
renderer
for
each
and
every
you
know,
UI
framework
available
for
Java
Script
like
we
would
have
to
do.
Angular
react,
JSF,
UJS
and
and
whatnot.
What
we've
opted
to
do
is
a
generic
JavaScript
renderer
that
can
be
used
pretty
much
everywhere
and
I
can
tell
you
already.
That
teams
is
a
great
example
of
a
client
that
was
written
in
angular,
using
our
JavaScript,
renderer
and
now.
C
Teams
I
believe,
is
at
least
writing
some
parts
of
the
product
in
react,
Jas
and
they're.
Still
using
the
same
render
outlook
web
app
is
react,
is
application
and
uses
the
same
renderer.
So
it's
really
designed
to
be
usable
across
all
JavaScript
UI
frameworks,
and
you
can
even
make
it
so
that
your
specific
angular
controls
or
whatnot
are
used
in
the
context
of
what
the
renderer
does.
So,
let
us
know
if
there
is
any
problem,
but
it's
it's
been
done
before
is
what
I
wanted
to
emphasize
yeah.