►
Description
In this 36-minute Developer/Maker - focused demo, Chakkaradeep “Chaks” Chandran introduces viewers to a new Microsoft Power Automate trigger (Item Modified) and action (Get changed Properties on item) for when SharePoint list items are updated. Owners may specify conditions and time interval in Flows. Update activity is communicated to item owner via Microsoft Teams channel messaging. Upon receiving a notification, owner may initiate a next-step Workflow. Demo plus 12-minute Q&A covering licensing, future enhancements, and more. This PnP Community demo is taken from the SharePoint (PnP) Community call – August 2020 – Monthly sync call recorded on August 11, 2020.
Demo Presenter: Chakkaradeep “Chaks” Chandran (Microsoft) | @chakkaradeep
Supporting materials:
• Microsoft Power Automate Community suggestion - Create a trigger for SharePoint list columns | https://powerusers.microsoft.com/t5/Power-Automate-Ideas/Create-a-trigger-for-SharePoint-list-columns/idi-p/88671?WT.mc_id=m365-15744-cxa
Learn more:
• 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
So
obviously
you
know
we
had
this
user
voice
item
that
actually
is
one
of
the
top
user
voice
items
right
now
that
talks
about
it
would
be
nice
to
have
a
trigger
if
a
certain
column
in
a
sharepoint
that
is
modified
and
also
to
understand
what
column
was
modified
right.
That's
also
one
of
the
typical
things
you
would
want
to
do
in
this
case.
A
From
the
user
wise
item,
you
can
see
that
if
the
status
column
is
modified
or
if
the
assigned
to
is
modified,
so
then
you
could
go
and
make
something
that
is
very
particular
to
your
business
scenario
when
things
get
modified
in
the
list,
so
it
took
a
long
for
us,
but
I'm
happy
to
announce
that
this
is
now
available
to
everyone.
And
if
you
go
to
this
user
voice
link,
I
have
also
given
instructions
on
what
is
available.
I'm
when
I
come
back
from
vacation.
A
Yes,
I
am
on
location,
and
just
you
know,
I
love
vessa,
so
much
and
of
course
the
community
here.
So
I
just
came
out
of
my
location
for
this
hour
to
deliver
this
session,
but
when
I
come
back
from
location
next
week,
it
will
be
documented,
as
well
in
our
power
automate
documentation
portal
to
drive
the
scenario
with
an
example.
A
So
the
the
scenario
is
really
simple:
something
got
modified,
I
want
to
know
what
got
modified
and
then
then
get
the
current
value
and
and
then
go
about
doing
my
workflow
building
my
workflow.
So
let's
first
go
into
where
you
can
find
this
in
your
tenant.
If
you
go
to
our
automate
website.
So
if
you
go
to
power
automate
website
and
create
a
flow,
and
if
you
choose
the
sharepoint
for
your
trigger,
you
should
be
able
to
see
when
an
item
or
file
is
modified.
A
So
one
of
the
things
we
did
simplify
this
time
is,
we
have
one
trigger
and
you
could
choose
a
trigger
to
target
either
a
list
or
a
library.
So
you
don't
have
to
go,
find
another
trigger
for
file.
So,
for
example,
here
I
can
say
you
know
the
site
address
it
comes
up
there
you
go
and
then
I
could
say:
here's
the
list
or
library
name
right.
So
you
can
see
that
I
have
both
list
and
library
name.
B
A
So
it
gives
me
all
of
the
libraries
and
lists
available,
so
it's
not
very
particular
to
list
it's
not
very
particular
library,
so
you
can
choose
one
in
the
same
trigger,
which
I
find
this
is
a
very
good
direction.
Going
forward,
you
will
see
is
making
this
change
across
the
triggers.
So
we
don't
confuse
customers
and
you
have
one
trigger.
You
can
keep
changing
between
the
list
and
library.
A
So
once
you
do
this,
you
know
you
have
the
other
options
as
well
the
folder,
and
even
if
you
want
to
just
pick
the
columns
that
you
want
say,
for
example,
if
you
have
12
more
than
12
lookup
columns,
you
know
that
won't
work
because
of
the
threshold
we
have.
So
you
could
choose
a
particular
view
to
bring
a
very
specific
columns
back,
so
this
trigger
will
give
you
the
ability
to
run
only
when
items
are
modified
in
that
particular
list.
I
have
selected
here
now.
A
So
when
you
think
about
this,
this
is
the
second
question
to
the
riddle
right.
So,
okay,
something
got
modified.
What
got
modified
right!
So
that's
something
I
want
to
understand.
So
now
you
could
say:
well,
I'm
looking
at
the
site
called
list
experiences
and
asset
manager.
So
I'm
going
to
just
select
the
same
thing
here.
A
Asset
manager
and
for
the
id,
so
I
can
choose
the
id
from
the
trigger.
So
then
it
gives
me
whether
it's
a
file
or
an
item.
The
id
is
consistent.
I
can
get
back
the
item
or
the
file
that
associated
with
it,
and
then
you
have
an
interesting
two
options
since
and
until
so
you're
getting
changes
for
a
particular
item.
A
You
can
specify
the
time
interval,
because
this
is
a
workflow
and
and
yeah
things
get
executed
at
certain
point
in
time.
Changes
happen
at
certain
point
in
time
in
in
sharepoint,
and
then
changes
happens
certain
point
in
time
in
power
automate,
meaning
that
the
run
could
be
later
than
you
know.
Change
happened
in
sharepoint,
maybe
five
minutes
or
15
minutes.
So
you
would
want
to
understand
what
does
the
change
happen
for
this
particular
item
since
a
time
interval?
A
Now
you
could
go
and
and
manage
your
own
time
interval
here,
but
we
thought
that
would
be
really
bad
for
users.
So
the
when
an
item
or
file
is
modified
trigger
comes
with
tokens
that
you
can
use
in
place
for
the
sims
and
until
properties
in
this
action,
meaning
that
the
trigger
knows
when
it
was
last
checked.
A
You
know,
when
did
it
last
check
for
the
flow
run
or
for
item
modifications
using
that
you
could
depend
your
business
logic
to
go
with
the
flow
logic
of
when
it
checks
for
modifications
with
the
sharepoint
list?
So
if
you,
you
know,
go
through
the
dynamic
property
here
and
and
actually
scroll
at
the
bottom.
A
Let
me
just
do
this
to
return
the
token
you
will
get
trigger
windows
stop
token
and
trigger
window
in
token.
So,
since
is
basically
trigger
window
start,
so
at
what
time
you
will
start
and
then
the
until
is
trigger
window
in
token.
So
now
this
will
make
sure
that
your
action
is
checking
for
changes
between
that
interval
of
time,
and
here
the
interval
time
is
whatever
the
power
automate.
Connector
checked
with
sharepoint.
A
What
was
the
last
time?
When
was
the
last
time
you
checked
what
is
interval
if
you
are
not
very
familiar
with
this,
how
to
handle
it,
just
look
at
the
documentation
and
put
these
two
values
in
and
you
will
be
using
the
out-of-the-box
way
of
handling
interval
times.
If
you
are,
you
know
someone
that
is
very
keen
to
manage
this
within
yourself.
You
have
the
power
to
go.
Do
it
to
manage
the
specific
intervals
you
want
and
using
those
specific
intervals
to
get
changes
now.
A
One
thing
this
action
requires
is
the
ability
to
understand
that
something
was
changed
and
that
does
not
come
for
free
right,
because
we
need
a
way
to
track
all
of
the
different
changes
that
happens
in
that
particular
list.
So
to
do
that,
this
action
requires
versioning
turned
on.
So
that's
the
only
caveat
here
and
we
have
this
in
the
right
there
in
the
information
icon.
If
you
click
on
it,
it
will
actually
give
you
that
this
must
have
versioning.
A
The
list
must
have
versioning
turned
on
no
there's
also
another
important
thing
here,
because
it
depends
on
versioning
it
that
directly
correlates
to
how
farther
can
you
go
back?
If
you
just
have
you
know
only
one
item
to
be
stored
as
versioning,
then
you
can
only
go
one
n
minus
one
right.
If
you
have
five
versions
stored,
you
can
go
n
minus
five.
So
that's
the
important
thing
here,
but
again.
A
One
of
the
things,
if
you
open,
show
advanced
option
is
we
have
some
interesting
option
there,
which
is
include
minor
versions?
So
you
know
most
of
the
time
the
major
version
is
considered
as
the
version
that
is
available
to
all
users
in
a
given
list.
But
sometimes
you
might
have
business
logic
that
you
want
to
apply
on
minor
versions
as
well,
but
do
understand
that
if
you
choose
to
do
that,
you
should
have
some
issue.
A
The
workflow
should
be
running
in
the
context
of
someone
that
do
has
access
to
minor
versions
and
can
read
minor
versions
out
from
the
list.
So
the
default
option
for
this
is
include
minor
versions.
It
does
not
include
minor
versions,
let's
say
no,
but
you
can
obviously
change
that
to
s
and
if
you
are
able
to
access
the
microphone
versions,
you
can
go
ahead
and
access
them
and
the
properties
here
now,
so
these
two
are
done.
So
the
next
thing
is
great.
I
put
this
workflow
how
the
heck
do.
A
I
know
that
something
was
changed.
How
is
power?
Automation
is
going
to
help
me
find
that
so,
let's
go
see
how
that
is
going
to
work
here
here,
I'm
going
to
choose
the
condition
right
and
I
want
to
know
what
properties
some
of
the
properties
that
changed
and
maybe,
in
my
business
logic
I
know
exactly
what
I'm
targeting
right.
A
So
we
have
something
called,
has
column,
changed
and
then
followed
by
the
column.
Name
right,
so
you
can
see,
has
column
change,
id
has
column
changed,
asset
tag,
model
serial
number
purchase
date.
Color
device
photo
everything
right.
There
is
also
a
status
now,
if
you're,
very
specifically,
focusing
on
status.
Now,
what
you
can
do
is,
you
can
just
say
in
your
condition,
has
column
change
status
is
equal
to
true.
A
That
is
it
that's
how
you
can
now
understand
that
that
column
was
changed
in
that
specific
time
interval
from
the
get
changes
at
get
changes
to
action.
So
it's
really
really
simple.
You
can
go
to
the
dynamic
properties.
Look
at
the
format
has
column
changed.
It's
answering
the
question
yes
or
no,
but
in
terms
of
the
programming
it's
actually
true
or
false,
and
then
you
use
that
in
the
condition
and
say
true
now,
if
you're
someone
that
wants
to
get
the
collection
and
and
do
more
on
your
own,
we
have
that
as
well.
A
Yeah
there,
it
is,
has
column,
changed
a
collection
showing
which
columns
have
changed.
So
this
is
a
collection,
so
you
can
also
do
something
if
your
job
is
not
about
condition,
but
you
just
want
to
enumerate
every
column
that
has
changed
and
do
some
parallel
things.
So,
for
example,
I
can
say,
add
an
action
and
do
a
switch
right,
choose
a
value,
and
I
can
go
down
here
as
column
changed,
and
then
here
I
can.
B
A
So,
instead
of
just
doing
condition,
you
also
switch
to
a
parallel
group
now
to
go.
Do
that
so
a
lot
of
great
options
here
and
again,
if
you're
going
to
use
the
get
changes
action
you
do
need,
versioning
turned
on,
which
is
there
in
the
documentation
and
how
backwards
you
could
go
is
depend
on
just
dependent
on
that
version
in
setting
and
for
the
trigger
you
don't
need
any
versioning,
because
trigger
does
not
depend
on
versioning.
It
just
depends
on
the
fact
that
something
changed
in
the
list,
so
this
is
great.
A
If
you
got
list
in
your
tenant
awesome,
if
you
can
try
it
out
the
issue
tracker
template,
that's
one
of
the
templates
available
out
of
the
box
with
the
microsoft
list
app
now.
The
issue
tracker
is
great
to
track
things
in
my
list
and
have
a
lightweight
system
then,
depending
on
let's
say
a
powerful.
You
know
project
management
tool
or
something
like
that.
So
it's
very
specific
to
my
team,
my
my
feature
group
and
here's
an
example
of
that
now
at
some
point
in
time.
A
Let's
say
we
do
want
to
promote
some
of
the
items
to,
in
this
case,
let's
say:
visual
studio.
You
know
devops
azure
devops
and
create
a
a
feature
card
for
my
engineers
to
now.
Consider
it
as
a
very
major
item,
because
pms
have
discussed
about
all
the
issues
and
we
have
promoted
an
issue
to
azure
devops,
very
common
scenario.
I
think
across
the
board-
and
we
see
customers
doing
that
now
with
power
automate.
This
makes
it
really
simple
right.
A
You
could
also
go
manually,
say,
select,
an
item
and
then
go
to
automate
menu
and
have
a
flow
that
can
actually
say
create
workflow
item.
But
that's
that's
like
1980s
right
I
mean
we
are
in
2020
and
we
need
something
that
is
much
more
easier
and
predictable
to
go.
Do
the
job-
and
I
know
from
my
team
that
if
the
statuses
won't
fix
right,
the
statuses
won't
fix
and
the
priority
is
critical.
A
I
do
want
the
decision
to
now
go
to
my
engineering
team
to
go.
Do
further
investigation
to
see
how
we
can
unblock
the
issue
and
and
have
a
fix
one,
our
other
way
or
our
proposals
and
brainstorming
that
so
I
need
engineering
heads
to
go
and
do
that.
So
that's
the
scenario
here
and
now,
with
this
new
trigger
and
get
changes
action,
I
can
actually
go
do
that
right.
So
I
can
now
say:
hey
something
got
modified
in
this
list.
A
The
status
column
modified
if
the
status
column
was
modified,
then
is
the
priority
of
that
item
is
critical.
If
the
priority
of
this
item
is
critical,
then
we
need
to
create
an
azure
devops
feature
card.
In
my
team's
project
and
and
that's
how
the
scenario
is
going
to
play
out
right,
so
are
you
all
with
me
still
yep?
That's
that's
the
scenario
so
now
I'm
just
going
to
refresh
this
page
most
of
the
time,
it's
good,
if
I
refresh
and
make
it
the
crunch.
A
So
I'm
going
to
open
this
item
and
by
the
way
you're
seeing
another
demo
here
which,
if
there
is
time
I
can
go
through
today
or
I
can
find
time
when
the
feature
is
actually
released.
This
is
a
feature
about
formatting,
the
header,
the
footer
and
the
body
of
the
form,
so
that
you
can
have
this
white
view
with
properties
under
every
section
customized
and
have
a
header
and
a
footer
to
drive
some
useful
scenarios
in
the
experiences
that
your
users
use
to
form.
A
So
it's
a
little
distraction,
but
I
can
come
and
give
a
you
know
a
session
about
this
once
the
feature
is
released,
but
we
have
been
showing
this
feature
across
various
webinars
and
demos
that
we're
doing
as
part
of
the
microsoft
list
product.
So
here
I'm
going
to
change
the
progress
to
try
to
move
this.
A
A
I
see
some
while,
while
we
wait
for
this,
I
do
see
some
chat
messages,
I'm
just
looking
through
that.
Okay,
so
there's
a
question
around
minor
version,
awesome,
there's
a
question
around.
Would
there
be
a
reason
that
the
scenes
version
and
anti-version
would
always
return
one
dot?
Oh,
even
if
the
current
version
is
6.0,
I
do
not
know.
A
It
really
depends
on
your
versioning
settings
on
how
this
is
all
configured.
So
we
don't
do
anything
beyond
that,
but
it
may
happen
that,
since
an
until
version
are
lower
than
the
current
version
in
the
cases
where
flow
did
not
check-
or
there
are
some
logics
that
it
did
not
appear
to
run.
So
that's
why
we
have
this
incidental
version
for
you
to
figure
out,
and
the
current
version
of
boolean
value
is
current
version
in
the
get
action
changes
to
to
drive
some
scenarios
using
that.
A
Let
me
check
now
so
there
it
is
it's
running.
So
what
this
has
now
done
is
one
thing
I
did
not
show
you
in
the
flow.
Is
it
actually
sent
me
a
team's
message,
so
it
went
and
looked
at
the
assign
to
column
in
my
list
and
it
sent
a
message
to
that
user
in
the
same
two
column,
a
teams
message
so
here
it
is
issue
change
to
won't
fix,
right
issue,
blah
blah
blah
was
changed
to
one
fixed
though
it
marked
as
critical.
A
Please
do
we
can
promote
it
as
a
bug,
so
I'm
gonna
create
a
bug
and
I'm
gonna
say
we
need
to
find
a
fix
for
this,
as
it
is
important
from
an
experienced
point
of
view
and
I'm
going
to
hit
submit
yep.
That
happens
all
the
time,
no
need
to
panic,
and
now
it
actually
created
it
sent,
and
then
you
saw
immediately.
I
actually
got
a
message
back
saying:
a
bug
was
created
with
the
azure
devops
link
here
like
that.
A
Now,
if
I
go
back
to
my
azure
devops
link,
you
can
see
there
is
the
item
that
I
just
it
just
got
created,
and
then
you
can
see
that
there
is
also
user
comments
we
need
to
fix.
We
need
to
find
the
fix
for
this
as
it's
important
for
the
experience
point
of
view,
so
whatever
I
gave
in
the
comments
has
come
back
here
now.
A
You
could
even
put
your
user
comments
as
a
discussion,
but
that's
something
I
would
say
is
something:
it's
a
pain
that
I
go
through
every
day
in
making
sure
I
can
format
these
things
right
in
a
way
that
I
can
read,
users
can
read
them,
but
that
aside,
you
saw
the
scenario
now
item
got
changed,
status,
remark,
critical
and
that's
right,
a
stereo
one
fixed
and
critical,
and
it
got
created.
So
I'm
gonna
delete
this.
A
So
I
don't
create
any
trouble
to
my
azure
devops
here,
so
we
can
go
ahead
and
see
how
the
workflow
works
here,
and
I
promise
you.
This
is
only
going
to
create
a
teams
message
and
this
flow
only
if
the
stainless
column
has
changed
and
the
priority
is
equal
to
critical
here
is
the
here's,
the
workflow
to
prove
that.
So
when
an
item
our
file
is
modified
right.
So
I
have
that
particular
trigger,
and
I
also
have
the
particular
action
talking
about
get
changes.
A
A
I
check
if
it's
true
and
then
I
go
ahead
here
to
say
if
statuses
won't
fix
and
priority
is
critical
right
now
I
get
the
status
value
from
the
current
item
right.
So
if
I
put
here
status
right,
so
I
do
get
the
status
value
when
an
item
is
created
or
modified
trigger
output,
because
the
trigger
ran-
and
I
do
get
the
value
when
the
trigger
rank.
So
I
do
get
the
status
value
status
is
a
choice
column.
A
Right
priority
again
is
a
choice
column,
so
you
get
a
priority
value,
so
I
say,
status
is
equal
to
one
fixed
priority
is
critical.
Then
I
move
on
to
my
next
block,
which
is
yes.
They
are
true.
What
am
I
supposed
to
do
now
and
now
I
can
say
post
the
choice
of
options
as
the
flow
bot
to
a
user.
So
now
I
can
create
my
own
choice,
create
bug,
ask
more
details
and
go
through
the
flow
issue.
A
All
the
you
know
give
all
the
values
here
and
then
I
wait
for
the
action
and
now
I
can
then
say
from
that.
You
know
waiting
action
that
I
have
here
goes
to
choice
of
options,
because
it's
waiting
for
the
option
to
be
completed
by
the
user,
I
can
say,
select
an
option
if
it's
create
bug,
then
I
go
create
a
work
item
and
now
then
I
post
a
message
as
the
flow
bot
to
a
user.
A
Very
simple,
straightforward.
It's
exactly
right!
You
had
planned
in
the
way
how
I
explained
how
this
is
going
to
work,
so
that
is
the
power
this
trigger
and
action
gives
to
now.
Take
your
business
workflows
to
the
next
level
with
item
modified
trigger
and
get
changes,
action
for
your
action.
So
that's
that's
my
demo
and
that's
what
I
wanted
to
share
today.
We
do
have
15
minutes.
I
would
like
to
use
this
15
minutes
of
visa
to
to
answer
some
of
the
questions.
A
B
A
So
I'm
going
through
comments,
there's
a
comment.
I
wrote
the
message
about
since
version
intuition
just
noticed
context
of
google
content.
Approval
was
turned
on.
Okay,
awesome.
Yeah
again
it
really
comes
down
to
your
versioning
settings
so
make
sure
that
the
versioning
settings
is
right,
so
users
can
get
the
right
experience
when
they
build
workflows.
On
top
of
that,
in
terms
of
licensing
there's
another
question,
even
if
you
immediately
exit
the
flow,
if
the
specific
column
wasn't
changed,
it
still
counts,
as
one
so
licensing
is
about.
A
Api
calls
now
runs,
do
not
account
to
licensing,
so
it
doesn't
matter.
If
you
have
1000
runs
or
million
runs,
licensing
does
not
come
into
effect,
licensing
come
into
effect
in
the
api
calls
and,
and
you
make
in
the
connector,
whether
it's
the
to
sharepoint
or
to
any
other
thing.
Every
step
is
basically
an
apa
call.
So
that
would
be
what
it
comes
to
licensing
and
in
your
scenario
where
you
exit
the
flow
and
specific
column
wasn't
changed.
A
If
that
involves,
you
know,
get
changes
action
then
there
is
one
step,
so
that
step
requires
an
equivalent
to
a
call,
and
I
think
the
trigger
is
also
accounted
for
the
api
call.
So
there
will
be
three
steps
you
would
check
now,
I'm
not
a
licensing
expert,
but
that's
something
you
would
need
to
probably
clarify
with
power
automate
team
on
how
licensing
works,
but
mostly
you
should
be
okay,
it's
not
going
to
overwrite
or
you
know,
bring
down
the
licensing
just
because
you're
checking
something
and
then
terminating
from
the
flow.
A
So
going
to
next
question,
any
plans
to
include
item
version
details
along
with
flow
trigger,
adding
a
trigger
condition
for
based
on
specific
column.
So
item
version
detail.
We
we
have
plans
for
the
next
step,
for
this
feature
is
to
actually
give
you
old
values
and
new
values.
That's
something
that's
missing
right!
So
what's
the
old
value,
you
got
the
new
value
from
the
trigger,
but
really
when
the
change
happened,
what
was
the
value
of
that
property?
So
in
this
case
you
know
status
quantum
change
in
that
get
actions.
A
I
want
to
get
the
value
of
the
status
column
as
well,
what
got
changed
and,
if
possible,
give
the
previous
version
as
well
the
the
version
value
that
is
harder
for
us
to
solve,
just
because
we
have
to
traverse
the
versioning
tree
and
give
you
the
worship
details,
but
that's
something
we're
working
on.
You
know,
after
the
current
priorities,
which
is
basically
packaging
and
stuff
once
that
is
complete,
we'll
come
back
to
this
and
enable
the
scenario
for
getting
previous
value
and
new
value.
A
Along
with
the
version
details.
Maybe
we
will
also
have
an
action
that
says,
get
version
details
and
give
the
version
property
version
number.
It
will
give
you
all
the
details
for
that
particular
version.
Next
question:
we
are
looking
for
graph
api
to
change
flow
approval
action
so
that
we
can
approve
reject
from
non-flow
screen.
A
What
would
be
nice
to
have
is
when
a
specific
field
column
is
modified,
so
we
thought
about
that
a
lot
whether
we
need
a
trigger
that
can
eliminate
the
step,
but
the
api
calls
everything
is
very
expensive
on
our
site,
so
cost
wise.
It
will
be
an
expensive
thing
to
do,
and
that
would
also
mean
that
for
that
trigger
to
work,
you
have
to
enable
versioning
so
you're
stuck
with
the
fact
that
the
trigger
itself
now
will
require
versioning
on
the
list,
even
though
we
don't
need
versioning
just
to
track
modification.
A
So
we
decided
to
split
that
and
provide
customers
value
in
two-fold
customers
that
don't
care
about
these
versioning
right
that
get
changes.
They
can
just
use
item
modified
customers
that
do
care
about
getting
changes.
Now
they
can
add
a
get
changes,
action
and
then
make
sure
that
versioning
is
turned
down
and
whatnot.
So,
from
an
experience
point
of
view,
the
experience
we
have
right
now
simplifies
for
all
of
the
scenarios
and
different
type
of
user
segments.
A
If
we
had
gone
with
one
trigger
for
like
hey,
you
know
when
an
item
is
modified
and
by
the
way
you
can
also
say
which
column
confused
a
lot
of
us,
because
from
day
from
from
the
start,
you
have
to
enable
versioning.
Otherwise
even
the
modification
won't
work,
and
it's
very
also
from
cards
wise.
It
was
very
expensive
for
us
back
and
forth
to
go
back
and
get
things
done.
A
I
hope
this
is
coming
to
logic
apps
as
well.
I
think
it
will,
but
it
won't
automatically
give
you
the
out
of
the
box.
You
know
running
because
it's
logic
apps
are
based
on
polling,
so
you
have
to
make
sure
that
you,
you
have
that
logic
as
well
by
by
going
through
the
polling
polling
of
the
trigger,
but
will
there
be
an
action
defining
current
previous
values?
So
I
think
I
just
answered
that
about
previous
values
and
current
values.
That's
something
we
will
add
now
you
know
at
this
point.
A
We
don't
have
that
support.
Yet.
Has
anyone
ever
heard
someone
say
that
they
are
a
licensing
expert?
True,
absolutely
not,
but
there
is
someone
in
microsoft
that
can
help
you,
so
the
the
the
project
here
would
be
finding
that
person,
but
unfortunately,
that's
not
the
product
team,
because
team
doesn't
really
make
decisions
on
how
business
is
won
at
microsoft
question
here.
A
Will
there
be
a
search
for
ms
list
in
teams
app?
If
you
know,
I
think
there
are
plans
across
the
board
to
make
search
experience
consistent.
So,
while
I'm
not
the
pm
for
that
team,
it's
a
very
different
team
altogether.
I
do
know
that
there
are
projects
and
work
going
on
to
enable
those
experiences
and
when
that
experience
comes
up,
I'm
pretty
sure
that
you
will
be
able
to
search
within
the
list
as
well.
A
A
Is
this
urban
gcc
today
we
yeah
this
should
be
available
in
gcc
dci
because
the
sharepoint
connector
is
available
and-
and
you
can
use
that
there-
this
is
a
premium
feature.
It's
not
a
premium
feature.
It's
included
in
the
standard
features
resource
12
lookup
threshold
can
be
bypassed
using
a
view
in
power
animate.
Yes,
so
you
select
in
the
trigger
or
get
changes
action.
You
know
all
of
our
actions
have
the
property.
A
That
is,
you
know,
limit
columns
by
view,
so
that
will
give
you
all
of
the
views
available
in
the
list,
and
a
good
thing
is
that
out
of
the
box
templates
come
with
views
built
in.
So
if
you
use
a
template
like
here
a
list
from
a
template
like
asset
manager,
you
can
see.
I
already
have
asset
manager
views
that
I
get
out
of
the
box.
So
that's
one
of
the
ways
we
suggest
powerapps.