►
Description
Power Platform Integrations / Connectors LABs Call delivered on March 8.
Hosted by Jocelyn Panchal (Microsoft) - @JocelynP_PM, linkedin.com/in/jocepan00/
Agenda:
0:00 - Intro and Updates
4:06 - Yelp Connector Creation and Application Demo
12:20 - OpenAI Independent Publisher Application Demo
24:33 - Overview and Applications of the Dataverse Connector - Matt Townsend (Microsoft) | linkedin.com/in/matt-townsend-0033017a/
Learn more about Power Platform Connectors
https://github.com/microsoft/PowerPlatformConnectors
https://learn.microsoft.com/en-us/connectors/
Want to join the next LABs Call? Fill out this form: forms.office.com/r/VN6uEuYKnK
A
Good
morning,
good
afternoon,
good
evening
from
whenever
you
guys
are
tuning
in
from
I,
see
that
we
have
a
really
large
International
Community
I
am
Jocelyn
your
Power
Platform,
connectors
products
manager
and
today
is
March
8th.
Welcome
back
to
the
labs
call.
Oh
awesome
I
see
that
people
have
joined
from
the
boot
camp.
A
Thank
you
so
much
for
coming
today
we
have
an
awesome
agenda
set
up
for
you,
I'm
going
to
be
talking
to
you
guys
about
how
to
make
a
custom,
connector
and
demoing
a
really
awesome
connector
that,
if
you
guys
are
from
the
boot
camp,
you
may
have
seen
this
demo
already.
I
also
will
be
giving
you
guys
updates
on
connector
count,
and
our
featured
guest
for
today
is
product
manager,
Matt
Townsend
from
the
power
automate
cloudflows
team.
Who
is
here
to
teach
you
guys
about
the
dataverse
connector,
let's
get
into
it.
A
Just
a
quick
intro
of
myself
I'm
originally
from
the
East
Coast
born
in
Brooklyn
and
raised
in
New
Jersey
I
am
a
University
of
Washington,
Seattle,
alumnus
and
I
used
to
work
on
the
cloudflows
team.
As
part
of
the
major
experience
closer
to
Matt
Justice
set
the
stage
for
what
we
are
talking
about
today,
I
think
it's
important
for
us
to
just
have
an
overview
and
understanding
of
the
Power
Platform
connector
ecosystem
as
a
whole.
A
Predominantly
our
connectors
represent
power,
apps
power,
automate
and
Azure
logic,
apps,
all
connectors,
initially
start
off
as
custom
connectors,
which
you
can
create
yourself
and
deploy
within
an
environment
for
your
own
personal
use
and
for
your
Enterprise
use
and
from
there
you
have
the
option
to
certify
your
connectors,
which
means
making
them
part
of
the
large
quantity
of
shared
connectors
that
are
immediately
usable
for
all
users
of
the
Power
Platform.
As
part
of
our
out
of
the
box
Solutions,
there
are
three
main
types
of
certified
connectors.
A
The
first
are
first
party
connectors
which
are
Microsoft
owned
and
created
predominantly
they
are
Microsoft
owned
apis
like
SharePoint
Office,
Outlook
Excel.
There
are
also
some
first
party
connectors
that
Microsoft
made
originally
in
the
creation
of
our
ecosystem,
including
external
apis,
like
LinkedIn
and
Twitter,
and
Google
Drive.
Other
Rich
use
case
scenarios
that
we
just
picked
up
on
our
own.
The
second
are
third-party
verified
Publishers,
so
these
are
external
API
owners,
predominantly
Enterprises,
that
are
leveraging
the
apis
that
they
own
themselves.
In
order
to
create
these
connectors.
A
Some
of
our
big
examples
include
DocuSign
Adobe,
Autodesk
SurveyMonkey,
and
these
are
not
necessarily
going
to
just
be
made
by
community
members
which
it
brings
us
to
our
last
type.
Independent
publisher,
connectors,
independent
publisher,
connectors,
are
created
by
community
members,
individuals,
Consultants
community
of
Citizen
devs.
Anyone
who
is
leveraging
open
source
apis.
So
that
means
it's
not
necessarily
the
owner
of
the
API
themselves,
and
there
are
a
lot
of
fantastic
use
cases
created
from
independent,
publisher
connectors.
Some
of
them
include
snowflakes
Yelp.
A
We
have,
of
course,
openai
which
I'm
sure
you
guys
have
heard
of
by
now,
as
well
as
a
bunch
more
Discord,
Spotify
HubSpot.
These
are
all
some
great
examples
of
how
open
source
code
has
been
leveraged
by
the
community
in
order
to
create
these
connectors
just
an
update
on
where
we
are
from
a
month
ago.
I
know
it's
been
a
short
month,
but
a
lot
of
changes
have
already
happened.
We
are
now
at
969,
total
certified
connectors
across
the
ecosystem,
which
is
29
more
than
the
last
time
we
spoke.
So
that's.
A
It
was
only
a
28
day
month,
so
that's
actually
one
additional
one
per
day,
which
is
really
awesome,
and
that
includes
plus
15,
more
independent
publisher
months,
so
15
more
that
were
made
from
the
community
I.
With
regards
to
the
total
breakdown,
we
are
actually
now
at
more
connectors,
created
by
independent
Publishers
than
we
were
at
first
party,
so
more
Community
made
connectors
than
the
ones
that
Microsoft
has
made
itself.
A
A
This
series
is
indeed
recorded
and
posted
on
YouTube
I
am
a
little
bit
behind
in
my
postings
I'm
sorry,
but
a
few
months
back,
we
actually
had
a
talk
with
our
certification,
PM
I'm
Jed,
who
went
through
the
process
of
how
you
can
take
your
custom,
connector
from
just
being
deployed
within
its
own
environment,
to
certify
it.
So
it's
available
for
all
users,
but
I
realized.
A
We
never
actually
had
a
formal
conversation
about
how
to
initially
start
off,
creating
that
connector
and
in
the
survey
that
you
guys
fill
out
in
order
to
get
an
invite
to
this
meeting.
I
ask
you
guys
how
many
of
you
guys
have
created
a
custom
connector
within
your
own
environment
or
made
a
connector
that
you're
using
for
personal
use,
and
that
is
actually
I'm
pretty
sure.
Like
the
majority
of
you,
guys
said
that
you
have
not
used
or
made
one
yet
so
I
figured.
This.
Would
be
a
good
lesson
for
us
to
cover.
A
I
can
also
then
go
and
share
again
the
link
to
the
recording
from
amjad
talking
about
how
the
certification
process
happens.
So
we
can
have
a
complete
story.
First,
how
do
I
make
a
connector
and
then
how
do
I
certify
it?
So,
let's
jump
in
the
first
thing
that
we're
going
to
talk
about
is
how
to
make
a
Yelp
custom
connector.
This
demo
was
actually
originally
called
from
something
to
wow
in
five
minutes.
So
basically
we're
just
gonna
say
that
it
only
takes
five
minutes
to
create
something.
Super
duper
impressive
in
the
custom
connector
space.
A
After
that.
It's
pretty
simple.
We
can
just
name
it.
We
can
then
go
ahead
and
call
this
Yelp
bootcamp
demo
for
my
person
that
came
from
The
Bootcamp
you'll
recognize
these
recordings.
We're
able
to
give
it
a
quick
description.
I
can
just
go
ahead
and
say
that
this
is
going
to
be
the
Yelp
demo
for
these
purposes
and
I'll
go
ahead
and
paste
that
link
to
that
original
API
as
the
host.
A
After
that,
I'm
able
to
move
forward
now
indicating
what
authentication
type
we
are
going
to
be
using
we're
going
to
be
using
the
API
key
and
we're
able
to
label
that
parameter
as
the
Yelp
API
as
the
authorization
type
that
we
need
and
from
here
we
can
move
on
to
actually
deciding
what
actions
we're
going
to
be
using
so
defining
the
purposes
of
this
connector.
So
we're
going
to
go
ahead
and
click
on
a
new
action.
A
Predominantly
I
want
this
API
to
be
able
to
search
for
businesses,
so
we're
going
to
name
it
business
search
and
from
here.
This
is
very
important.
The
verb
that
we're
looking
for
is
to
is
these
are
recordings
for
demo
purposes,
but
thank
you
for
noticing
that
we're
going
to
be
getting
this
imported
from
sample
by
again
calling
that
API
from
the
dev
portal
website
we're
going
to
ensure
that
our
definitions
are
required.
So
you
actually
do
have
to
fill
in
these
terms.
A
To
make
sure
that
you
know
we
actually
have
a
term
that
we're
looking
for
the
term
might
be
restaurant
and
we
also
want
to
require
a
location.
So
we're
not
going
to
search
for
restaurants
or
search
for
businesses
throughout
the
entire
world,
we're
going
to
then
go
and
make
sure
we
call
a
default
response
again.
A
This
is
pretty
simple,
because
our
Dev
tools
are
able
to
give
us
a
default
response
for
what's
going
to
be
called
when
we
leverage
this
connector
immediately,
you
don't
need
to
be
some
kind
of
Dev
wizard
expert
mode
level
in
order
to
create
a
custom
connector
again.
Most
of
this
is
provided
by
the
dev
tools
itself
and
from
here
we
have
just
about
we're
almost
done,
creating
it
already.
A
Something
important
to
note
is
that
for
this
API
authentication
type,
the
word
Bearer
first,
because
this
is
the
specific
type
and
then
insert
our
API
key
we're
going
to
test
it,
and
it
might
take
a
second
to
refresh
that
our
connection
is
valid,
we'll
click
the
little
refresh
token
and
there
we
have
it.
There
is
our
connection
and
has
been
established,
and
now
we
can
go
and
test
it
in
a
flow
before
we
get
anything
super
fancy
or
try
to
create
an
app.
A
So
I
looked
for
restaurants
in
Manhattan
and
I
tested
the
operation
to
see
that
we
did
actually
get
a
response
in
the
response
type
that
we
were
originally
looking
for,
so
I
can
see
that
there
is
a
breakfast
and
brunch
place
and
those
are
the
coordinates
for
it.
Here's
the
address
us
awesome.
This
was
a
success.
A
The
last
thing
that
we
did
for
this
demo
just
to
again
go
from
nothing
to
wow
in
five
minutes
was
we
went
and
created
a
really
quick
app,
so
we
went
into
powerapps
to
create
a
blank
canvas
app
and
we
named
it.
Yelp
demo
from
here
we're
going
to
create
a
blank
app
and
it'll
take
a
second
to
load,
because
powerapps
is
a
little
slow,
sometimes
and
we're
able
to
start
creating
that
connection
again
between
the
connector
and
our
app
now
and
we're
going
to
only
be
pulling
from
one
data
source.
A
So
it's
important
to
know
that
in
powerapps
you
can
predominantly
use
a
connector
in
two
ways,
either
as
a
data
source
or
as
an
action
where
you're
actually
pulling
from
a
secret
flow
behind
the
scenes.
We
want
to
add
data,
and
now
we
can
see
our
Yelp
bootcamp
demo
connector
is
there
as
our
data
source
perfect
from
here
we're
going
to
go
and
configure
the
inputs
and
the
outputs.
So
what
are
we
going
to
be
searching
for
and
what
is
it
going
to
return
for
us?
A
We're
going
to
go
and
add
a
text
input
as
well
as
a
button,
and
what
that
button
is
going
to
do
is
search,
so
we
label
it
a
search
and
we
make
sure
we
set
our
results.
So
we
can
see
that
we're
searching
within
the
realm
of
Manhattan
here
we're
going
to
go
and
input
a
vertical
Gallery
so
that
we're
able
to
scroll
through
everything
and
configure
that
so
it
is
connected
to
our
to
our
connector.
So
we
can
go
and
say
we
want
this
to
be.
Our
result,
choose
a
result.
A
There
we're
able
to
go
and
configure
our
image,
as
well
as
the
description
of
the
restaurant.
So
here
we'll
say
that
this
is
where
we're
going
to
have
the
name
of
the
restaurant
be
returned
this
item.name,
underneath
perhaps
this
item
dot
rating.
So
we
can
see
how
many
stars
this
restaurant
has
and
last
just
a
little
image.
Give
me
a
little
picture
of
this
restaurant
here.
A
Now
we're
going
to
go
and
click
F5
preview
it
and
search
up
restaurants
and
again,
we've
hard-coded.
This
parameter
to
be
within
the
realm
of
Manhattan,
and
also
we
have
some
results.
We
have
some
Mediterranean
restaurants.
We
have
a
bunch
of
options.
This
was
how
quick
it
is
for
you
to
create
a
custom
connector.
A
A
A
Last
time,
I
was
able
to
show
you
guys
a
few
screen
recordings
of.
Thank
you.
Thank
you.
Yeah
I've
really
worked
to
make
sure
that
was
a
seamless
process.
Thank
you.
I
showed
you
guys
last
time,
a
really
awesome
demo,
created
by
an
independent
publisher,
leveraging
the
open,
AI,
connector
and
I,
actually
was
able
to
integrate
that
demo
with
the
Yelp
demo.
So
we
can
see
just
how
powerful
two
different
connectors
can
be
in
a
very
similar
use
case.
A
So,
let's
get
going,
let's
see
an
even
cooler
demo
we're
going
to
stick
with
the
theme
of
looking
for
restaurants
right,
because
that
was
how
we
were
going
to
be
leveraging
our
our
Yelp
demo.
So
we
have
this
ultimate
data
sample
generator
here
and
we're
looking
for
restaurants
near
Times
Square,
and
we
get
a
bunch
of
options.
It
just
lists
me
some
options.
We
have
Olive
Garden.
We
have
TGI
Fridays
I,
wanted
to
get
a
description
of
that.
A
Maybe
I'm
not
super
familiar
with
what
Olive
Garden
is
or
something
so
I
can
get
a
little
description.
What
should
I
be
expecting
from
this
restaurant
awesome?
Now
I
get
a
little
bit
of
description.
It's
an
Italian-American
restaurant
chain,
perhaps
I'm
vegetarian
and
I,
want
to
know
what
meal
options
I
have
there.
I
can
have
vegetarian
entrees
served
at
asterisk
asterisk.
Referring
to
our
original
search,
parameter
of
restaurants
near
Times,
Square,
awesome
I
got
some
examples
like
plant
parmesan,
stuffed
shells
marinara.
These
are
some
great
examples
of
vegetarian
options.
A
I
can
have
at
that
original
restaurant
that
we
were
calling
got.
It
got
it
that
makes
sense.
Maybe
I
want
even
more
options.
Maybe
I
want
to
know
vegetarian
appetizers
served
at
and
I
think
I've
decided.
I
do
want
to
go
to
Olive
Garden.
Let's
give
some
data
on
vegetarian
appetizers
served
at
Olive
Garden.
We
have
bruschetta,
I,
love,
bruschetta,
I
know
what
bruschetta
is,
but
maybe
I'm
not
familiar
with
some
of
these
things.
Okay,
I
can
get
a
description
of
that
as
well.
A
We
know
that
bruschetta
is
an
Italian
appetizer
with
slices
of
toasted
bread
and
tomatoes.
Great,
thank
you
for
that
Insight
ultimate
sample
data
generator.
We
are
also
able
to
call
for
an
image
of
bruschetta.
Maybe
I,
don't
know
what
that
looks
like
awesome.
Thanks
for
giving
me
this
information
I
can
also
then
go
and
say
perhaps
I
have
an
allergy
and
I
need
to
know
more
specifically
what
ingredients
are
being
used
in
there
again,
we
type
for
ingredients
in
asterisk,
referring
back
to
our
original
parameter
of
vegetarian
appetizers.
A
From
here,
I
can
then
go
and
say
that
I
think
I've
decided
that
I
do
want
to
go
to
Olive
Garden,
but
perhaps
I
want
to
go
to
a
different
Olive
Garden
location
than
just
the
one
year.
Times
Square
I
can
then
go
and
search.
Olive
Garden
locations
in
Manhattan
and
I
see
the
original
Times
Square
One,
but
I
can
also
find
one
in
the
Upper
East
Side
in
Midtown.
Maybe
I
didn't
grow
up
on
the
east
coast
and
I'm
not
super
familiar
with
these
areas.
A
So
I
can
then
go
and
ask
for
a
description
of
this
neighborhood.
What
to
expect
when
I
go
to
the
Upper
East
Side.
It's
a
very
important
question,
then
to
ask:
is
there
going
to
be
parking
in
Manhattan,
so
I
can
ask
for
parking
options
at
and
again
the
asterisk
will
refer
back
to
our
original
parameter
of
parking
options
at
Olive
Garden
locations
around
Manhattan,
which
I
think
is
super
duper
smart
and
you
guys
already
know
the
spoiler
of
what
connector
is
being
able
to
give
us
all
of
these
informations.
A
We
know
that
this
is
the
open,
AI
connector,
but
the
fact
that
this
is
able
to
actually
give
us
all
of
this
information
with
just
one
connector
is
super
awesome.
So
say
we
want
to
find
things
to
do
more
than
just
to
eat.
We
are
able
to
go
and
say:
oh
here
are
some
things
to
do.
I
can
visit
the
Empire
State
Building.
This
part
I
thought
was
super
impressive,
where
I'm
able
to
ask
for
parking
options
at,
but
it's
parking
options
at
things
to
do.
A
The
fact
that
contextualizes,
the
location
of
the
thing
to
do
is
super
impressive,
because
it
doesn't
dramatically
match
up
there
at
all,
but
again
I'm
able
to
know
that
places
to
eat
near
a
thing
to
do
so.
I
can
find
food,
I
can
find
parking
and
then
I
can
go
and
ask
for
an
image.
What
is
it
gonna
look
like
for
me
when
I
go
to
visit
the
Empire
State
Building,
there
is
a
little
picture.
A
What
is
it
going
to
look
like
for
me
as
I
walk
through
Central,
Park
and
I
thought
the
walking
through
Central
Park?
One
was
a
really
awesome
image
because
it
doesn't
just
show
Central
Park
as
a
whole
that
really
famous
zoomed
out
picture
of
overhead.
It
shows
what
it
actually
looks
like
as
you're
walking
along
the
path
of
central
Park,
and
the
last
part
that
I
wanted
to
call
out
was
that
this
connector
now
supports
Dolly
as
well
so
from
here.
I
can
then
go
into
the
action
in
powerapps
and
say:
okay,
create
image.
A
I,
don't
just
want
a
picture
of
loop
results.
I
want
a
picture
of
loop
result
while
it's
cloudy,
because
perhaps
it's
going
to
be
cloudy
when
I'm
going
to
visit
these
locations,
we're
going
to
regenerate
the
images
and
it's
going
to
give
me
back
an
image
of
this
attraction
of
whatever
I'm
doing
while
it's
cloudy.
These
aren't
just
images
that
are
necessarily
just
found
online
like
we're
using
some
kind
of
Bing
search
connector
here.
These
are
images
that
open
AI
is
going
to
be
generated.
A
So
there
is
a
little
picture
of
somebody
walking
through
Central
Park,
while
it's
cloudy
and
the
next
thing
that
we
can
do.
Of
course,
in
in
the
most
stereotypical
Dolly
demo
fashion
is
I
can
go
in
and
say
something
like
I.
Don't
just
want
a
picture
while
it's
cloudy
I
want
you
to
go
and
give
me
an
image
of
it
in
some
other
artistic
fashion.
So
we're
going
to
go
into
a
picture
of
loop
result,
while
I'm
gonna
delete
that
and
say
as
a
watercolor.
A
While
it's
raining,
perhaps
we're
gonna
have
some
Seattle
weather
in
the
east
coast.
We're
gonna
go
back
to
F5
and
regenerate
our
images,
and
now
we
will
have
to
see
our
watercolor
of
the
Empire
State
Building
in
the
rain,
or
our
picture
that
we
have
our
little
guy
over
here,
with
an
umbrella
on,
while
he's
walking
through
rainy,
Central
Park
for
those
people
that
I
presented
this
to
initially
the
first
time
in
the
boot
camp.
I,
lied
and
I
didn't
actually
say
that
this
was
going
to
be
the
open.
A
Ai
connector
I
used
this
demo
as
an
opportunity
to
evangelize
the
open,
AI
connector,
as
well
as
the
opportunity
to
evangelize
the
independent
publisher
program,
because
it's
really
important
to
note
that
this
fantastic
use
case
was
not
necessarily
created
as
an
alliance
between
Power
Platform
and
open
AI
themselves.
This
was
created
by
an
independent
publisher,
who
was
just
leveraging
open
source
code,
and,
what's
really
awesome,
is
that
anyone
can
do
this.
So
I'm
probably
sure
that
Troy
is
here
right
now.
A
A
A
Absolutely
there
is
so
we
have
lots
of
documentation,
step
by
step
on
how
to
create
a
custom
connector
happy
to
share
these
links
in
the
chat
once
I
hand
it
over
to
Matt,
as
well
as
step
by
step,
how
to
certify
it.
There's
also
a
ton
of
videos
using
different
connectors
as
the
example
on
YouTube,
some
with
low
code
Revolution.
Some
of
you
guys
might
know.
Daniel
laskowitz
he's
done
a
bunch
of
examples
as
well
happy
to
share
all
of
these.
C
C
Is
there
any
good
improvements
coming
for
custom
connectors
when
doing
Alm
between
environments
now,
obviously
we're
at
our
infancy
stage,
where
we're
just
taking
it
one
step
at
a
time,
but
we've
noticed
there's
quite
a
lot
of
information
out
there,
which
isn't
exactly
seamless,
it's
good,
but
it's
not
seamless.
So
that's
that's
what
I'm
after
we.
A
Do
have
planned
enhancements
in
the
Alm
space
for
custom
connectors
on
our
roadmap
and
where,
where
this
is
definitely
a
feedback
we
also
do
have
and
I'm
not
sure
if
this
is
in
your
realm,
so
much
Chris
but
Chris.
The
flow
specific
Alm
expert
is
in
the
in
this
call
as
well
Chris.
This
is
definitely
more
of
a
question
for
me
and
Samir,
but
do
you
have
any
additional
insights.
D
C
B
C
Actually
says
what
that
is,
why
it's
important
and
when
you
know
what's
actually
happened,
you
know
those
sort
of
things,
but
don't
do
me
wrong.
I
said
we're
we're
liking
the
custom
connectors
and
we're
about
to
start
work
with
old
Legacy
systems
that
we're
looking
to
move
on
to
the
Power
Platform
one
way
or
the
other
just
to
get
data
moving
again
so
that
that's
where
we're
interested
in
this.
So
any
information
on
the
Azure
secret
bit.
That
might
not
be
that
secret,
but
you
just
don't
tell
anybody
useful.
Can.
A
C
C
C
A
Worries
no
worries.
I
see
a
lot
of
questions
for
links
list
of
connectors
that
people
will
want
or
think
it's
interesting
I
will
drop
that
as
well
as
other
information
on
how
to
certify
your
connector.
How
to
create
a
custom.
Connector
I
will
share
that
as
well.
I
I
see
one
more
hand
raised,
go
ahead,
I
think
her
name
is
Ashok.
A
G
Good
thanks
your
thing.
Yeah,
it
looks
like
we
have
about
30
minutes,
left
yeah
nice
to
meet
everyone
thanks.
Thanks
for
all
your
interest
in
the
platform,
and
these
awesome
questions
here
and
Jocelyn
I
have
to
say
that
I
almost
fell
off
my
chair
with
that
demo.
That
was
so
awesome
to
see
the
the
dolly
pieces
and
everything
tied
into
an
awesome
canvas
app,
so
love
that
demo.
Thank.
E
G
Try
out
some
of
those
custom
connectors
and
pieces
more
myself,
yeah,
so
jumping
in
I'm
Matt
Johnson
from
Atlanta
Georgia
sharing
some
content
about
the
database
connector
today.
This
has
been
as
a
quick
overview
and
feel
free
to
chime
in
the
chat
as
I
go
along.
If
this
yeah
with
any
questions
on
this
content,
this
is
meant
as
a
quick
primer
for
anyone
less
familiar
with
the
dataverse
connector.
Definitely,
for
you
know
other
other,
more
advanced
questions
or
other.
G
G
Let
me
jump
right
into
our
content,
so
just
just
to
share
dataverse
fitting
in
with
our
low
code
platform,
so
you're
used
to
seeing
our
other
Power
automate,
powerapps
power,
bi
power,
virtual
agents
and
now
power
pages
and
other
pieces
right
as
a
set
of
low
code
tools
that
span
all
of
Microsoft
right,
Azure,
Dynamics,
365,
M365
and
other
pieces
right.
These
tools
make
it
possible
to
build
things
that
connect
these
simple,
apps
and
complex
business.
G
Apps
that
you
know
meet
your
workflows,
combine
data
from
across
all
these
different
sources
yeah
and
help
help
make
things
more
efficient,
underpinning
Dynamic,
365
and
all
of
our
low
code.
Apps
is
Microsoft
dataverse
as
a
way
to
support,
not
just
these
apps,
but
your
extensions
on
these
apps.
So
you
can
store
data,
build
custom
apps
with
different
You,
Know,
Rich,
business
logic
and
Integrations
right
within
this
app.
G
G
It's
easy
to
respond
to
any
changes
in
your
data
sources,
so
dataverse.
Of
course
you
can
use
the
built-in
tables
and
dataverse,
you
can
add,
custom
any
custom
entities
if
you're
tracking
you
know
custom
products,
types
of
inventory,
custom
processes
or
any
of
those
pieces.
You
can
add
custom
entities
and
dataverse
and
manage
those
events.
G
You
may
have
seen
the
last
stops
call
where
Nathan
helgren
and
our
database
team
was
sharing
more
about
virtual
virtual
tables
and
dataverse,
and
some
of
the
new
ways
that
those
can
be
set
up
so
that
a
dataverse
can
actually,
you
know,
reflect
any
data
source
in
SQL
directly
as
a
data
version
entity.
So
if
you're
building
cloudflows
building
apps
that
all
interact
with
dataverse,
you
don't
need
to
have
connections
to
those
other
sources
directly
handle
those
all
those
mappings
and
things
in
multiple
places.
G
You
can
do
it
all
from
dataverse
where
you've
brought
in
you
know
multiple
other
tables,
multiple
other
things
to
the
same
place,
and
you
can,
you
know
automate
all
from
that.
One
set
of
tables,
and
the
last
last
piece
we'll
see
in
the
the
number
here
is
around
querying:
creating
updating
data
in
flows.
G
B
G
There's
a
default
environment
that's
available
by
default
within
your
your
organization's
tenant.
You
can
also
create
custom
environments,
and
you
may
also
have
access
to
other
environments
that
others
have
created
or
that
are
used
as
part
of
your
apps.
If
your
organization
uses
different
Dynamics,
apps
has
different,
you
know
they
may
have
one
or
more
other
environments
tied
to
those
other
apps
that
they've
already
built.
G
I
can
confirm
which
environments
that
I
have
access
to
manage,
which
ones
that
I
can
access-
and
you
know
by
clicking
into
this
one
you
can
see
this
underlying
environment
URL
for
this
organization,
which
is
you'll,
see,
can
be
handy
to
refer
back
to
sometimes
as
you're
building
different
Integrations
with
this
specific
environment.
So
for
anyone
getting
started
with
dataverse,
you
can
use
this
Power
Platform
admin
Center
to
check
you
know
which
environments
you
have
access
to
manage
your
user
access.
You
need
by
default.
G
You
need
an
administrator
system
customizer
if
you're
doing
more
admin
type
tasks
you
need
within
this.
You
can
make
sure
that
your
user
or
other
users
you're
working
with
have
the
environment
maker
role
to
make
sure
that
they
can
create
and
run
cloudflows
in
this
environment.
Just
to
show
that
really
quick.
This
is
a
demo
user
right
now.
This
user
has
the
basic
user
security
role
as
well
as
environment
maker,
so
I
know
this
user
would
be
able
to
work
with
cloudflows
use
the
database
connector
all
these
other
pieces.
G
If
you
do
not
yet
have
a
dataverse
environment,
you
can
start
a
new
trial
for
different
pieces.
You
can
start
a
power
automate
trial
and
get
access
to
these
pieces.
If
you
have
Microsoft
teams
in
your
organization,
you
have
access
to
power,
automate
within
context
of
teams
and
if
you're,
using
a
dataverse
for
teams,
environment
it'll
show
up
as
type
dataverse
for
teams.
Here.
G
The
dataverse
connector
is
always
available
from
teams
for
that
usage.
For
other
environments,
you
do
need
a
premium
license
to
use
the
database
connector,
which
means
one
of
the
per
user
power,
automate
power,
apps
or
other
licenses.
But
if
you
don't
have
one
of
those
you
can
start
a
90-day
trial
just
from
power
automate.com
or
through
one
of
the
other
Dynamics
trial.
Experiences
that
I
mentioned
yeah,
so,
let's
say
you've
you've
successfully
signed
in
here
create
an
environment.
G
You
have
a
context,
you're
you're,
ready
to
get
started
here,
I'm
showing
the
powerapps
maker
experience,
but
I
also
want
to
make
sure
folks
have
seen
the
automate
URL
itself.
This
is
changed
recently
to
be
make.power
automate.com.
So
this
is
your
hub
for
everything,
power
automate.
You
can
also
reach
it
through
the
powerapps
pages,
but
sometimes
this
embedding
doesn't
load
as
fast.
So
sometimes
it
can
be
helpful
to
go
directly
here
to
to
power
automate
so
yeah.
Let's
look
at
a
sample
app
here.
G
I've
created
a
very
basic
model,
driven
power
up
and
just
to
show
the
steps
to
get
here
if
you're
following
along
and
the
recording
would
be
from
I
have
too
many
app
tabs
open
here,
creating
a
new
blank
blank
app
based
on
dataverse-
and
you
see
here
it
says,
model
driven
app.
This
is
creating
a
new
model
driven
power,
app
that
uses
these
same
view,
components
and
things
that
are
common
across
other
Dynamics,
365,
apps
and
other
a
date
of
respect,
apps,
so
I
created.
G
One
of
these
I
gave
it
a
name
and
I
selected
a
table
for
this
demo,
app
I
selected
the
contact
table
type
for
this
demo.
So
here
you
can
see
you
know,
I
can
manage
these
views,
the
sidebars
everything
you
can
customize
within
power-ups,
but
by
default
or
so
sorry.
From
from
this
context,
I
want
to
show
two
ways
of
interacting
with
your
power
automate
flows
from
you
know
from
this
app
and
kind
of
extending
this
app
to
have
more
automation.
G
G
Or
from
this
full
menu,
you
can
see
any
flows
that
you
have
that
are
related
to
this
contact
table
entity.
So
here
I've
already
created
one
flow.
That
has
this
context,
but
if
you,
if
you
have
a
model
driven
app
and
you
want
to
easily
publish
a
flow
that
anyone
with
access
to
this
app
can
trigger
Let
me
show
the
steps.
So
if
you
from
this
experience,
if
you
click,
create
a
flow,
it
brings
you
to
a
template.
G
G
You'll
select
the
environment
that
you're
using
right.
Now,
it's
just
default
as
the
the
current
environment
being
used
here,
you
would
select
the
contacts
table
and
add
other
steps
that
you
want
to
run
whenever
anyone
you
know
receives
this
context
from
the
flow.
So
from
these
other
steps,
you
would
have
all
of
the
details
of
this
contact
entity
available
for
use
and
other
steps,
and
you
can
add
other
dataverse
actions,
other
connectors
to
run
from
that
point.
G
So,
just
to
show
an
example
here
this
export
contacts
flow
whenever
one
of
these
rows
is
selected,
it's
getting
the
forecast
and
just
doing
a
basic
list
operation
in
dataverse.
This
could
be
extended
to
you
know:
email,
a
spreadsheet,
take
other
actions
from
dataverse,
and
so
on.
So
let's
say:
you've
shared
this
app.
You
want
to
make
sure
that
other
folks
can
run
this
flow
as
well.
This
isn't
just
something
you've
built
for
you.
You
want
it
to
be
available
to
your
team.
G
G
If
you
share
as
co-owner
that's
for
folks
who
want
to
collaborate
on
the
flow
with,
but
if
you're
simply
trying
to
share
this
flow
in
a
way
that
other
folks
can
run
and
use
the
same
process,
you
want
to
go
to
run
only
users.
Add
those
people
or
you
can
add
a
a
group.
I
believe
this
can
be
either
an
AED
group
or
a
group
team
in
dataverse
to
ensure
that
those
users
users
have
access
anyone
you
add
here
will
have
the
same
experience
if
that
trigger
is
being
used.
G
I'll
have
the
same
experience
here
where,
just
by
using
that
trigger
and
having
access
to,
you
know
View
and
run
that
flow
they'll
be
able
to
trigger
the
flow
from
this
context,
just
as
you
as
the
owner
of
the
flow
and
just
to
show
here,
if
you
have
dataverse
steps
in
the
flow
that
you
want
to
run
with
the
connection
of
that
other
user
right,
rather
than
your
connection
as
the
user
that
set
up
the
flow.
This
is
also
the
area
where
you
can
configure
that.
G
So
you
can
say
you
know
for
any
dataverse
actions
in
the
flow
any
other
connectors.
When
that
user
clicks
Run
for
the
float,
you
want
it'll,
prompt
them
for
their
connections
and
there
here
I'm,
seeing
my
connections
being
used,
but
based
on
those
other
options.
I
was
showing
from
the
flow
management
page
they'll
see,
they'll,
be
able
to
provide
their
own
connections
and
their
connections
will
be
used
for
any
of
the
steps
in
the
flow.
G
The
flip
side
of
this
was
for
any
other
automatic
process
where
you
want
to
take
more
automatic
steps
in
the
background.
So
maybe
you
have
a
you,
know:
guest
check-in
process
or
you're,
managing
volunteers
or
things,
and
when,
when
one
of
these
is
added,
you
want
to
take
other
steps
in
the
background
the
dataverse
trigger
when
a
row
is
added,
modified
or
deleted.
Lets
you
easily
respond
to
any
changes
to
any
table
in
dataverse.
G
Let
me
pull
up
the
definition
for
that
one,
just
to
show
an
example,
so
here
this
this
is
again
a
simple
example
just
to
show
these
pieces,
but
here
I'm
showing
anytime,
you
add
a
contact,
and
this
is
saying
anyone
in
the
organization
I
could
also
say
any
if
I
select
user.
This
is
any
contact
that
I
myself
have
added
the
parent-child
business
unit
or
business
unit
are
scoping
that
to
specific
parts
of
my
organization
that
I
may
have
set
up
within
dataverse
an
organization.
Is
anybody
at
all?
G
So
you
can
see
whenever
a
contact
is
added
here,
I'm
saying
any
contact
that
anyone
else
has
added
in
this
organization,
but
then
I've
selected
this
option
here
for
run
ads
so
run,
as
is
saying
for
the
dataverse
actions
in
this
flow.
Just
like
we
were
looking
at
this
from
the
manually
triggered
I
can
say
myself
as
the
flow
and
Connection
owner.
G
The
connection
being
used
for
this
trigger
I
want
the
other
database
actions
in
this
flow
to
use
that
context.
I
can
say
the
user
who
modified
that
context.
If
it's
you
know
the
change
type
modified
or
modifying
users,
the
user
who
added
or
modified
on
those
pieces,
I
could
also
say
the
row
owner.
If
you
know,
if
there's
a
specific
user
and
dataverse
that
owns
that
account
owns
that
other
data
and
if
other
operations
could
be
used
in
their
context.
G
So
here,
if
I
select,
modifying
user
and
I
select,
this
use
invokers
connection
option.
This
is
only
for
the
dataverse
connector
to
let
you
choose
which
other
dataverse
steps
you
want
to
be
tied
to
this
run
as
option.
Then
the
other
steps
in
this
flow
will
use
this
user's
identity.
So
if
you
had
other
steps
sending
email
through
dataverse,
adding
other
records
and
databers,
we
would
all
be
using
their
their
identity.
G
So
here
just
to
show
when
a
new
contact
is
added,
maybe
they're
doing
field
work
or
some
other
pieces,
and
it's
important
for
this
contact
Energy
to
always
have
a
snapshot
of
the
current
weather
as
they're
working.
So
we
can
say,
get
the
current
forecast
and
then
we're
going
to
add
that
forecast
as
a
note
to
that
record
in
dataverse,
so
just
to
show
what
that
looks
like
you
can
see
for
this
John
Doe
record
that
I
created
a
moment
ago.
G
You
can
summarize
that
content
you
know,
put
that
in
a
notification
or
other
other
records
that
you're
linking
from
here
yeah,
so
that
so
that
was
showing
mainly
tricking
triggering
flow.
How
to
share
that
with
your
organization
we
just
saw
triggering
a
background
flow
using
the
win.
Arrow
is
added,
modified
or
deleted
trigger
and
tying
that
to
other
dataverse
steps
and
making
sure
you're
still
using
the
right
connections
that
you
intend
to
you
for
that.
G
There's
a
lot
of
other
parts
of
the
database
connector
that
we
can
get
into
around
different
actions,
but
just
in
the
interest
of
time,
I
will
leave
it's
excellent,
cheat
sheet
from
Donnie
kaheel
as
a
reference,
so
this
walks
through
every
parameter
of
the
database
connector
and
has
great
great
examples.
So
you
know,
for
example,
all
the
different
filter
options
as
you're
working
with
you
know
all
the
different
data
types
and
dataverse
and
your
filtering
growth
is
coming
in
or
listing
grows.
This
syntax
is
needed
currently
to
send.
G
You
know
pass
these
filters
on
to
dataverse,
and
this
cheat
sheet
has
a
bunch
of
great
examples
that
make
that
you
know
really
easy
to
refer
to
anytime.
You
are
working
with
files,
rows
relating
other
records.
Those
other
pieces
and
I'll
include
the
links
as
well.
To
this
will
level
up
browser
extension,
so
this
makes
it
really
easy
anytime.
You
are
looking
at
a
contact
record
or
any
other
just
viewing
the
form
for
this
row
and
dataverse.
G
G
If
you're
managing
the
schema
for
this
also
show
within
the
powerapps
experience
the
tables
View
for
contact,
you
can
see
how
I
can
manage
the
schema
for
this
entity,
and
this
is
the
same
place
you
go
if
you
are
creating
or
modifying
other
other
custom
entities.
I
can
see
a
preview
of
the
data
here.
I
can
modify
the
forms.
That's
where
I
just
was
to
see
that
one.
The
view
of
one
contact,
The
View,
was
seeing
the
list
page
and
those
those
layouts
for
multiple
contacts.
G
All
that
can
be
managed
here
and
you
can
see,
especially
when
you're
working
with
flows.
These
shortcuts
here
for
copying
the
schema
name,
copying
The
Logical
name
have
been
added
recently
to
make
it
really
easy
to
preview
the
raw
metadata
for
this
table.
So
you
can
confirm
exactly
which
names
as
you're
building
different
Integrations
need
to
be
used
both
for
the
table
definition,
the
column,
names
and
other
pieces,
and
for
pulling
sample
data
for
this
table.
So
anytime,
you're
working
with
new
custom
Integrations
in
dataverse.
G
Sometimes
it
can
be
helpful
to
check
you
know,
make
sure
you're
working
with
the
right
internal
properties
in
those
pieces
from
this
View
from
the
powerapps
tables
table
browser
yeah.
So
I
mentioned
the
level
up
extension,
the
dataverse
cheat
sheet
and
xrm
toolbox,
another
tool
that
makes
it
easy
more
than
just
seeing
the
Syntax
for
things
that
has
more
Tools
around
browsing
browsing
your
tables,
creating
custom.
G
D
F
Yeah,
it's
certainly
something
which,
which
makes
it
more
reliable
to
Renee,
to
remember
the
schema
name,
for
instance,
and
do
stuff
like
this,
but
it
certainly
would
be
even
more
easier
not
to
go
into
this
experience
and
leave
the
other
experience.
So
it
would
be
great
to
see
an
improvement
in
the
dataverse
itself
and
in
terms
of
Select
columns
to
not
really
selecting
columns
in
terms
of
a
comma
separated,
make
it
really
a
drop
down.
Mark
and
and
drill
into
the
table
schema.
G
Yes,
our
roadmap
perspective,
so
we
are
looking
at
making
it
possible
to
directly
select
columns
so
have
a
more
advanced
Expression
Builder,
where
you
don't
need
to
use
the
odata
syntax.
You
can
use
the
same.
You
know
when
you're
customizing
a
view
in
dataverse
using
a
very
similar
interface
to
you
know,
just
add
the
attributes
you
want
to
filter
on
and
save
that
into
the
flow.
G
G
This
part
of
our
admit
is
a
separate
set
of
actions,
but
there's
other
places
where
we
you
know
we
want
to
improve
the
co-pilot
experience
directly
within
dataverse
and
other
places
as
well
to
save
save
effort
and
save
the
need
to
go
copy
and
parse
the
schema
for
here
as
well
so
I
guess
yeah
I
encourage
everyone
to
take.
Take
this
as
a
base
for
working
with
dataverse.
G
We're
definitely
looking
to
improve
a
lot
of
these
areas
further,
but
yeah
between
these
tools
and
these
capabilities
that
are
here-
and
you
know
these
new,
the
open,
API,
independent
publisher,
connector
and
the
other
Integrations
coming
up
looking
forward
to
see
what
you
all
create
and
hear
your
feedback
on
other
areas
that
this
can
be
can
be
streamlined.
I'm,
sorry
I
can't
see
the
chat
right
now.
A
G
G
Do
have
a
you
know:
individual
per
user
license
if
they're
using
you
know
these
Premium
capabilities
for
advanced,
connectors
or
sorry
premium
connectors,
including
the
dataverse
connector
in
their
flows,
but
definitely
we're
working
on
a
guide,
for
you
know,
scaling
scaling,
dataverse
usage,
you
know,
anytime
you're,
working
with
higher
volume,
amount
of
data
and
that'll
include
some
of
the
steps
around
service
principle
interactions
as
well.
As
you
know,
patterns
for
making
batch
or
bulk
calls
or
working
with
some
of
those
other
pieces.
G
C
Yeah
I
I've
got
another
question
about
a
weirdly
named
thing
when
you're
doing
run
only
and
you're
setting
the
flow
up
for
run.
Only
you
end
up
having
to
create
a
mail-enabled
security
group
in
exchange.
Then
you
have
to
go
into
the
data
verse
and
then
you
got
to
go
to
the
thing
called
teams
and
then
you've
got
to
make
a
pretend
team
up
that
references.
The
other
thing
that
you
just
enabled
in
the
mail
enabled
Security
Group.
G
G
Okay,
awesome
any
other
questions
on
the
database,
connector
or
other
pieces,
I,
I,
guess
or
I,
guess
any
other.
Any
requests
that
you'd
like
to
see
any
any
like
we
talked
about
the
usability
pieces
and
other
pieces
around
making
it
easier
to
manage
service
principles.
Then
group
teams
with
dataverse
curious
if
folks
have
other
other
pieces,
they'd
like
to
see
improved.
G
Yeah,
so
I
can
speak
to
one
one
area
we
want
to
improve.
That
is
making
it
easier
to
use
in
dataverse
it's
called
the
pre-image
of
the
change
that
comes
through.
So
you
know,
when
you
have
a
record
changing,
we
want
to
make
it
easy
to
respond,
like
you
know,
query
on
meaningful
changes
from
what
the
record
was
to
what
it's
changed
to,
which
can
make
it
possible
to
have
more
more
scope
triggers
avoid
infinite
Loops
between
states.
G
You
don't
intend
so
I
think
that's
the
main,
the
main
piece
we
have
around
infinite
loops
around
more
scoped
triggers
that
may
help
with
that
as
well,
but
definitely
yeah
right
now
we
have
a
warning:
that'll
appear
if
you
have
a
table
referring
to
itself
later
in
the
flow,
but
that's
I
know
that's
very
general,
it's
just
a
hint
that
that
may
happen,
but
what
you're
looking
for
is
just
making
sure
that
you
can
scope
those
pieces
right.
Yeah.
C
C
We
still
find
the
same
issue
is
that
you
modularize
your
flow,
so
instead
of
having
one
super
complicated
flow,
you've
got
free
flows
that
do
three
different
things
when
the
data
is
in
a
different
state
in
the
same
table,
but
because
they're
all
looking
at
the
same
table,
you
end
up
trigger
locking
on
an
admin
column
that
you've
put
in
that
says
all
right
when,
when,
when
the
first
action
happens,
change
that
column
to
new
all
right
and
then
the
second
flow
sits
and
looks
at
that
table
and
goes.
Has
that
real
chance?
C
G
Definitely
definitely
yeah
we'll
definitely
look
into
how
we
can
make
that
a
little
bit
smoother,
avoiding
yeah.
We
know
whenever
you
have
many
many
flows
triggering
on
the
same
pieces
as
well.
You
know
kind
of
hard
to
see
the
you
know
the
whole
layout
of
everything
tied
to
that
data
tied
to
those
same
tables
and
things
as
well.
So
there's
other
improvements
we're
going
to
make
that
make
that
that
easier
as
well
right,
okay,.
G
Awesome
awesome.
Well,
thank
thank
you.
Everyone
if
you
have
any
other
comments,
I
think
Jocelyn.
You
shared
my
LinkedIn
feel
free
to
Ping
through
there
through
the
this
community
area,
I
think
Jocelyn
and
I,
and
the
power
to
meet
PMT,
monitor
the
power
automate
community.
So
please
feel
free
to
use
the
ideas
and
other
parts
of
the
power
automate
Community
Forum
for
any
any
other
questions,
or
you
know,
sharing
things
you've
made
but
yeah.
A
A
We
enjoyed
learning
more
about
the
dataverse
connector
and
that
we
had
a
good
session.
As
always,
please
reach
out
to
me.
If
you
guys
have
any
other
questions,
you
guys
know,
I
see
my
LinkedIn
and
my
Twitter
and
I
look
forward
to
seeing
you
guys
next
month.
This
is
always
at
7
A.M
Pacific
time.
The
second
Wednesday
of
every
month.