►
From YouTube: How to connect Microsoft Dataverse to Microsoft Teams
Description
In this 14-minute citizen developer-focused demo, Norn Young shares one way to save time finding information in Teams. Use Power Automate to identify customer channels across 100s of Teams, link an account record to a specific Teams channel, and see a dynamic “Open Teams” button on the model-driven app command bar. Account and Channel information is stored in Dataverse. The Model-driven app allows users to connect an Account to a Teams channel. Enjoy the rapid, yet comprehensive explanation of flow logic. This PnP Community demo is taken from the Microsoft Power Platform community call – July 2022, recorded on July 20, 2022.
Demo Presenter
• Norm Young (Microsoft MVP) | @stormin_30
Supporting materials
• Blog – Norm Young | https://normyoung.ca/
Stay connected
• Twitter https://twitter.com/microsoft365dev
• Call attention to your great work by using #PowerAppsCC and #PnPWeekly on Twitter.
Learn more
• 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 Blog - https://aka.ms/m365pnp/blog
• Microsoft 365 Platform Community - https://aka.ms/m365/community
A
Well,
I
hope
everyone's
enjoying
their
summer.
I
know
I've
been
so
far
and
I've
been
doing
a
lot
of
camping
and
when
you're
camping,
it's
really
important
to
have
the
things
that
you
need
quickly
at
your
disposal
to
make
that
camping,
experience
more
convenient
and
not
that
this
is
a
a
demo
about
camping.
A
So,
let's
get
into
it,
and
so
the
the
scenario
is
is
that
we
have
tie
graph,
hundreds,
hundreds
of
customers
and
we
keep
them
in
dedicated
customer
channels.
Inside
of
microsoft
teams,
and
as
you
can
imagine
you
know,
finding
a
channel
inside
of
a
team
can
be
very
hard
to
do
at
scale
and
and
we
are
at
scale
and
of
course
you
some
might
think
that
maybe
we
should
just
simply
have
a
team
per
customer.
A
It's
very
inefficient
and
our
technical
problem
is
that
we're
using
a
dataverse
solution
and
there's
no
native
teams
integration
into
dataverse.
It
exists
in
dynamics
365,
but
it
doesn't
exist
in
dataverse
at
least
not
at
this
time,
and
so
our
solution
was
to
use
powerautomate
to
collect
or
harvest
all
of
those
customer
channels
across
those
different
teams
create
a
mechanism
where
we
could
link
the
account
record
to
that
teams
channel
and
then
have
a
open
teams
button
on
the
model
driven
command
bar.
That
would
be
dynamic
when
it
was
linked
and
populated.
A
So
the
first
thing
that
we
have
to
do
is
perform
that
initial
harvest
of
all
of
the
different
teams
that
exist
for
our
customers.
So
in
this
case
we
did.
This,
like
you
know,
like
a
backfill
operation,
execute
it
once
per
customer
customer
team.
Excuse
me
we'd
have
to
iterate
through
those
different
teams.
So
that's
why
we
had
that
var
team
grid
variable
that
would
get
the
the
team
info.
Then
we'd
run
again
and
get
the
channel
info.
A
A
If
you
replace
that
with
ms
teams
and
then
the
rest
of
the
url,
it
will
open
up
the
native
app
and
that's
the
experience
that
we
wanted
for
our
users.
So
we
do
a
little
replace
on
that
web
url
and
that
allowed
it
to
open
up
into
the
teams
client.
So
once
that
was
done,
harvest
across
all
those
different
teams,
and
we
have
the
baseline
of
that
information
and
that
is
added
to
our
custom
database
table,
then
we're
able
to
move
on
to
the
next
step.
A
The
next
step
is
now
that
daily
run
where
we're
going
to
run
multiple
times
a
day
and
check
against
the
current
customer
team.
We
have
a
debug
variable
that
we'll
use
to
get
like
debug
information.
We
create
an
object
for
all
of
the
different
parameters
that
we'll
need
inside
of
the
the
flow
we
use
scopes
to.
Try
and
you
know,
break
up
the
work,
handle
errors,
and
so
we'll
go
to
the
current
team
for
the
customers
and
we'll
use
that
to
that
var
team
grid.
A
We'll
do
the
same
thing
to
get
the
the
channels
you
need
to
have
both
team
and
the
channels
we'll
compose
this
information.
So
we
can
use
it
again
later
for
populating
that
team's
channel
table
open
that
up
and
here
what
we're
doing
is
we're
going
to
list
all
the
rows
in
that
channel
and
we're
only
taking
active,
most
recent
channel,
and
so
I'm
going
to
filter
the
results
of
that
list
channels
to
just
get
the
last
known
record.
A
So
I
can
only
show
the
the
last
record,
and
so
I'm
inserting
I'm
only
going
to
insert
the
new
rows
after
that
last
one
is
created,
and
this
is
where
you
see
I'm
doing
work
with
composing
and
and
manipulating
the
maximum
date,
and
then
I
take
that
date
and
I
use
it
to
filter
that
array
that
it
came
through.
Of
that
result.
A
We
don't
add
enough
customers
to
do
it
more
than
that,
so
that
works
out
well
and
again,
I'm
doing
this
replace
on
the
https
to
ms
teams,
because
that
will
click
the
button.
It
won't
open
the
browser,
it'll
open
up
the
teams,
client,
which
is
a
nice
experience
for
my
users.
I
do
a
catch
inside
of
this
workflow,
my
production
level
flows.
A
I
have
some
data-driven
components
where
I
will
get
the
admin
of
the
system,
their
information,
so
I
can
send
them
debug
if
there
is
a
an
issue
and
I'll
take
the
results
from
that.
First
scope
that
we
saw
in
the
flow
for
the
try
and
that
will
be
composed
and
formatted
in
a
way
that
I
can
send
it
to
the
admin.
Should
there
be
a
failure
in
inside
of
teams
as
an
adaptive
card,
and
it's
a
very
nice
experience
all
right?
So
let's
go
to
the
next
slide.
A
So
I
go
in
and
I
edit
the
command
bar
and
I'm
going
to
look
at
the
main
form
of
the
account
table.
So
we'll
edit.
That
and
here
we
can
see
the
button
that
I've
created
these
most
of
them,
except
for,
like
three
of
them,
are
the
ones
that
would
come
standard
with
the
account.
So
we
create
a
new
button
and
we
call
it
the
open
teams
channel,
that's
the
label
and
then
we'll
tell
it
to
use
an
icon
and
we'll
use
the
ms
teams
icon.
I
didn't
have
to
upload
this.
A
It
just
existed
there
already
and
on
the
action
we'll
run
a
formula,
so
the
formula
on
select
is
to
launch
that
channel
url.
That
has
been
linked
to
the
account
record.
So
the
first
part
of
the
demo.
We
were
harvesting
information,
there's
a
linkage
that
still
has
to
happen.
But
this
is
what
the
button
will
do
and
then
we
have
to
show
or
hide
the
button
depending
on
whether
it's
populated
or
not,
and
that's
what
this
check
is.
So
if
that
channel
url
value
in
the
account
table
is
not
populated,
don't
show
it
well.
A
Why'd
you
go
to
the
account
table
well
doing
a
launch
at
least
my
experience
doing
a
launch
from
the
related
table
and
not
the
account
table
didn't
work,
and
that's
why
I
had
to
do
that.
Okay,
next
one!
This
is
what
the
user
experience
looks
like
we're
in
our
model
driven
app
and
we're.
Looking
at
a
test
account
you'll
notice
that,
in
this
configuration
tab
we
have
a
customer
channel,
none
is
listed,
so
I'm
going
to
find
one
that
is
linked
to
my
test
account.
A
A
Finally,
we
use
notifications
to
send
a
a
confirmation
that
that
action
of
the
linkage
was
successful.
If
there
was
a
failure,
they
would
get
a
notification
there
as
well,
but
then
a
backend
notification
would
go
to
the
administrator
of
the
system
right.
So
what
does
that
link
to
teams?
Look
like
well,
it's
executed
on
demand.
We
we
have
the
debug
variable.
We
have
more
parameters
that
we're
using
to
make
the
flow
work.
A
lot
of
it
is
for
data
driven
elements
that
I've
defined.
A
I'm
checking
for
the
length
of
that
value
in
that
column,
and
if
it's
not
populated,
then
we
shouldn't
be
running
it.
But
in
this
case
it
is
so
I'm
going
to
go
now
over
to
my
team's
channel
table
inside
of
dataverse
and
I'm
going
to
get
the
value
make
sure
it
matches,
and
then
I'm
going
to
compose
that
url
and
then
I'm
going
to
set
it
in
my
parameters.
A
A
And
I
will
list
the
users
now
now.
Why
am
I
listing
the
users?
Well,
if
I
want
to
send
a
notification,
I'm
going
to
have
to
find
out
who
to
send
it
to,
and
that's
what
I'm
doing
here
so
I
list
the
users
I
get
that
information
parsed
out
and
I'm
able
to
get
their.
I
think
it's
their
azure
active
directory
id
or
something
like
that,
and
then
I
can
send
that
notification
to
them.
So
I've
got
the
owner
of
the
record.
A
Here
we
go
back
into
our
system,
users
and
boom
that
goes
out
and
they
get
that
message
right
now.
Excuse
me!
So
that's
like
the
business
side
of
it.
The
back
end
is
to
to
do
the
catch.
The
catch
is
to
catch
any
types
of
errors
that
may
have
happened,
so
the
admin
knows
to
to
go
in
there.
So
the
adaptive
card
again
takes
all
of
that.
Debug
information
that
I
can
trap
and
sends
it
to
the
admin
to
use,
so
that's
all
good
there
so
really
blasted
through
that.
A
The
user
experience
is
driven
out
of
that
model
driven
app,
so
they
have
their
own
hub
for
work
inside
of
the
business
and
it
allows
them
to
focus
on
that
higher
value,
business
of
work
and
these
margins
over
time.
You
know
they
they
add
up
to
something
significant.
So
I
really
blasted
through
that
and
again
I
really
wish
the
development
time
for
that
would
have
been
equally
but
it
it
was
not
so.
Thank
you
so
much
for
the
opportunity
to
come
here.
I'm
I'm
happy
to
keep
this
conversation
going.
B
Really
really
good
stuff
really
appreciate
it,
and
and
and
again
just
to
underscore
don't
discount
those
marginal
gains
right.
It's
the
straw
that
broke
the
camel's
back,
so
those
little
things
add
up
in
a
good
way
when
you're,
making
those
little
marginal
gains
in
every
little
minute
back
throughout
the
day
is
a
benefit
for
us,
so
really
fantastic
stuff.
Thank
you!
So
so
much.