►
From YouTube: Community Demo - Integrate modern chart web part to Dynamics 365 data using Microsoft Flow
Description
Cool community demo showing how to implement no-code or low-code integration between SharePoint Online and Dynamics 365 using Microsoft Flow. Demo is taken from the SharePoint dev Special Interest Group recording on 10th of January 2019.
Presenter - Matti Paukkonen (Innofactor) - @mpaukkon
More details on the SharePoint dev community calls from http://aka.ms/sppnp.
A
B
Hi
everybody
and
greetings
from
darken
kind
of
cold
Finland,
and
my
name
is
Monty
Parkin
and
I
work
as
a
senior
architect
on
the
inner
factor,
which
is
a
Finnish
company,
and
there
is
my
Twitter
and
blog
address,
and
today's
demo
is
about
turbo,
boosting
your
quick
chart.
Web
parts
with
Microsoft
flow,
which
I
also
blocked
last
week
and,
as
you
may
already
know,
that
which
are
web
parts
got
updated
before
Christmas,
at
least
on
maintenance.
B
And
now
you
can
use
SharePoint
beast
as
a
data
source
and
my
demo
is
about
updating
weekly
count
of
opportunities
from
Dynamics
365
to
a
SharePoint
list
with
flow
and
then
displaying
it
with
quick
chart
web
part.
So
it's
really
really
a
local
solution.
Most
of
the
code
is
like
calculating
the
actual
week
number
so
to
the
demo
bin.
B
Here's
a
simple
list:
it
just
has
a
title
field
which
I
have
renamed
to
a
week
and
then
it
has
a
count
field
which
is
just
a
number,
nothing
more
and,
as
you
can
see,
I
already
have
some
data
added
to
it.
So
you
can
see,
see
the
chart
right
away
when
I
reach
a
page.
So
here
here
I
have
an
empty
page
and
then
I
just
add
that
we
chart
there
notice
the
cool
section
backgrounds
also
and
just
configure
it
there.
B
B
So
then
the
data
fields
count,
and
it's
all,
also
displayed
just
the
supporting
data
fields,
so
number
and
currency
I
think
I
found
out
that
those
are
supported
and
then
the
title
field,
which
was
renamed
as
last
week.
I
won't
do
any
sorting
because
it's
displaying
displaying
items
in
the
order
day
we're
at
it
so
I
can
actually
get
the
week's
right
and
maybe
I
have
some
labels
there
and
number
of
opportunities.
B
B
Okay,
here's
the
chart-
and
next
is
the
turbo
boosting
section
with
flow,
so
I
have
I'll
already
made
a
flow
here
which
we
can
actually
take
a
look
at
so
first
we
have
a
trigger
from
dynamics
365
which
actually
takes
hold
and
new.
When
entity
opportunity
is
created,
it
actually
fires
tonight
a
lasts
a
week
number
as
you
can
see,
here's
the
most
of
the
code
I
have
created
so
I'm,
not
actually
100%
sure.
B
Is
this
really
really
working
in
all
the
cases,
but
it's
kind
of
close
and
then
I
in
detail
as
the
case
counter,
which
is
just
an
integer,
then
a
little
conversation
between
week
week
days
so
current
day
of
the
week,
and
what
is
the
day
of
the
week
on
on
January
1st
current
year,
and
if
the
current
day
of
the
week
is
less,
then
we
just
increment
the
week
number
any.
It
worked
at
least
better
after
that
I
get
suggest
items
from
SharePoint
list.
B
That
was
the
opportunities
and
if
the
title
equals
the
current
week,
which
is
actually
the
variable
here
and
then
the
condition
if
it
returns
an
empty
body.
So
there
is
in
the
list
item
which
has
a
title
title,
which
is
current
week.
We
actually
creating
I'm,
creating
a
new
item
and
adding
account
one,
and
if,
if
the
item
is
found,
then
I
just
get
the
case
count
add
it
to
a
variable:
okay,
it's
not
visible
and
then
increment
it
by
1
and
update
a
list
item.
So
that's
it.
That's
kind
of
a
really
really
simple.
B
Most
of
the
time
it
took
to
figure
out
how
to
actually
count
the
week
number
with
flow,
so
how
it's
actually
working,
let's
see
the
chart
first,
so
there
is
all
the
opportunities
at
it
on
week.
One
then
I
call
that
a
dynamic,
CRM
and
I
already
have
a
new
opportunity
here
so
I
add
a
topic.
Pnp
community
call.
B
B
B
A
Great
amount
of
actually
elements
demonstrated
without
actual
code
and
and
to
be
fair,
I
think
the.
If
there
is
an
issue,
the
issue
is
within
the
code
part
of
this
one,
which
was
the
function
in
the
Asha
flow,
sorry
India
in
the
flow
right,
so
calculation
of
these
things.
So
if
there
is
an
issue
there
or.
B
A
A
Avoid
the
fact
that
this
multiple
flows
running
after
time
but
I
think
that
this
is
super
super
cool
demo,
because
it
shows
three
different
application.
It
shows
the
dynamics,
it
shows
the
flow
and
it
shows
SharePoint
and
what
would
be
the
budget
estimate
for
doing
all
of
this
custom?
That
would
be
insane
when
you
think
of
it.
So
you
would
have
to
have
some
sort
of
a
recurrent
running
a
sure
web
job,
which
is
executing
in
Asscher
using
dynamics.
A
B
A
Doesn't
have
to
be
dynamic,
it
could
be
a
custom
web
api
and
that
could
be
the
part
for
the
developers
to
write,
which
will
then
call,
for
example,
on-premises
or
will
replicate
data
from
own
premises.
Lob
systems
sequel
assure
database,
which
we
then
replicate
using
flow
or
the
relevant
data,
aggregated
data
using
flow
to
the
shipment
list,
and
then
we
surfaced
that
from
a
shipment
list,
because
we
don't
want
to
replicate
all
of
the
data.
The
shipment
list,
because
shipment
list
is
not
a
relational
database
table
like
everybody,
should
always
remember
right.