►
From YouTube: Demo: Power Apps present production line
Description
This holiday demo by community member Clarissa Gillingham (@ClarissaGillin2), features a present production line using Power Apps.
For more information, visit https://powerapps.microsoft.com/
This demo was taken from the December Power Apps community call
https://youtu.be/VTqpi_izZ9Q
Stay connected
Twitter https://twitter.com/microsoft365dev
YouTube https://aka.ms/M365DevYouTube
Blogs https://aka.ms/M365DevBlog
A
B
The
first
thing
that
we
we
do
is
we
have
a
flow
that's
going
to
bring
in
that
data,
noticing
that
sharon's
put
that
record
that
response
record
in
our
database.
Now
we
need
to
convert
that
into
a
present
record
and
then
start
getting
that
ready
to
go,
and
then
the
elf
supervisors
use
a
model
driven
app
and
the
elf
workers
use
a
canvas
app
to
actually
go
through
the
process
of
making
the
present.
B
We
already
know
who's
naughty
and
who's
nice,
so
let's
go
making
some
presents,
and
this
kind
of
shows
the
the
kind
of
process
that
we've
got
going
on
here,
and
everything
that
you
that
you'll
see
in
this
fit
is
obviously
powered
by
microsoft
database
and
it's
really
cool
that
you
can
have
this
kind
of
two-tier
system,
almost
of
being
able
to
present
the
model
driven
app
for
more
kind
of
like
process
based
supervising
tasks
and
also
be
able
to
present
the
like
more
kind
of
user.
Interactive
canvas
that
piece
as
well.
B
So
I'm
just
going
to
briefly
touch
on
how
this
actually
looks
in
terms
of
the
data
model.
So
what
we
have
is
we
have
a
response
that
comes
in
and
that
response
triggers
off
a
present
to
be
created
and
that
present
has
different
attributes,
different
columns
in
it
like
a
status
and
a
recipient,
and
it's
also
allocated
to
one
alpha
at
a
time
and
it's
made
using
a
recipe.
B
So
this
is
something
that
you
know,
obviously
we're
using
it
for
christmas
presents,
but
the
beauty
of
creating
models
in
this
kind
of
way
is
that
you
can
look
at
it
and
say:
oh
actually,
you
know
what
else
kind
of
uses
recipes
and
components
and
ingredients
and
instructions.
You
could
use
this
in
a
you
know
a
restaurant
application
or
you
could
use
it
in
multiple
different
other
production
line
scenarios.
B
So
enough
kind
of
just
talking
about
it.
Let's
actually
see
it,
so
I'm
just
going
to
kill
my
share
a
second
and
bring
back
the
correct
screen
and
we
will
find
out
who
is
our
winner
of
the
first
person.
You
can
see
how
many
you
can
see
how
many
nice
people
we've
got.
Look
at
all
of
these
emails
that
have
come
through.
B
This
is
amazing,
but
we'll
see
who
is
the
lucky
winner?
Who
actually
was
the
first
person
to
first
nice
person
to
answer
our
questionnaire,
so
we've
got
our
our
email
that
lets
us
know
that
new
nice
person
has
filled
out
the
questionnaire
this
would
be.
Obviously
this
is
my
account,
but
this
would
be
the
account
for
an
elf
supervisor,
and
so
we
need
to
click
here
to
kickstart,
the
present,
and
in
doing
so
we
find
jamie
you're,
the
winner
you're,
the
first,
the
first
person
to
to
fill
this
out
and
be
nice.
B
We
can
view
in
the
model
driven
app
and
we've
also
got
this
thing
along
the
top
which,
if
you
haven't
seen
before
this
is
a
business
process
flow,
and
this
allows
us
to
really
easily
kind
of
streamline
the
supervisor's
role
because,
rather
than
having
to
look
through
here
and
go
oh
well,
maybe
what
do
I
have
to
do
now?
They
can
just
click
here
and
see.
Okay.
The
first
thing
I
need
to
do
is
I
need
to
allocate
this
present
to
a
specific
self
we
hit
enter.
B
Getting
in
the
way
of
the
process
and
these
business
rules
are
really
really
easy
to
set
up,
because
you
just
start
off
with
a
condition,
and
you
can
add
these
different
rules
to
your
condition.
So
in
this
case
we've
got
if
this
present
has
been
allocated
to
an
elf.
So
if
the
allocated
two
contains
data
and
the
resource
step
has
not
yet
been
confirmed,
then
we
know
that
it's
allocated
perfect.
B
This
is
where
we
come
to
the
canvas
app.
So
he's
got
his
christmas
present
production
like
he's
just
come
in
to
work
for
the
day
to
start
his
shift,
he'll
log
in
as
himself
and
he'll
see
that
there
we
go
jamie's
present
needs
resourcing.
It's
immediately
come
through
the
system.
He
doesn't
need
to
to
do
anything
to
to
find
out
what
his
new
jobs
are.
He
can
just
go
ahead
straight
away
and
make
them.
B
So
let's
have
a
look
at
the
needs,
resourcing
steps.
So
the
first
thing
that
bob
needs
to
do
is
he
needs
to
go
and
collect
items
from
a
stockpile
and
what
we
have
in
the
system
is:
we've
got
this
stockpile,
which
has
all
the
different
ingredients
and
components
that
all
the
elves
have
access
to
and
as
the
elves
are
going
through
and
collecting
resources
for
the
presence.
These
items
are
ticking
down.
B
So
currently,
if
we
just
have
a
look
at
stock
amount
of
metal,
we've
got
200
and
we've
got
a
maximum
capacity
of
250
and
obviously
we
need
to
pick
up
some
metal
to
make
our
toy
car.
So
let's
simulate
bob
going
off
and
collecting
all
of
those
items
perfect
submit
the
resourcing
step,
and
you
can
see
we
get
this
nice
little.
B
But
what
we'll
also
see
if
we
come
into
our
stockpile
is
now
we've
got
199
bits
of
metal,
so
this
helps
us
to
maintain.
You
know,
keep
track
of
that
inventory
who
needs
this
as
well.
I've
just
got
another
email,
so
I'm
just
going
to
go
up
to
the
top
as
a
supervisor.
I
then
get
notified
that
bob
has
flagged
the
resourcing
step
for
this
one
complete
perfect.
B
So
then
I
would
go
over
to
bob
station
in
the
elf
factory
and
I
would
go
and
confirm
whether
whether
that's
been
completed
so
we'll
say
that
bob
did
a
good
job
excellent
and
we
can
either
tick
it
here
or
we
can
just
tick
it
up
here
again
following
our
business
process
flow,
and
we
know
the
next
step
is
manufacturing
and
maybe
bob
isn't
very
good
at
making
toy
cars.
So
what
we
might
want
to
do
is
switch
out
to
a
different
elf.
Let's
say
felix
excellent,
so
we've
submitted
that
to
the
next
stage.
B
All
of
them
can
be
managed
by
different
or
allocated
to
different
people
and
managed
by
one
person
who
is
just
going
between
their
emails
and
the
and
the
model
driven
app
just
really
quickly
be
able
to
just
flag
yep,
that's
been
done,
that's
been
done
perfect
and
now
we
can
see
excellent,
that's
been
flagged
and
at
each
step
of
this
process
as
we're
moving
it
through
the
business
process.
This
status
is
getting
updated
automatically
and
that
data
can
then
be
reported
on.
B
B
B
And,
of
course,
there's
multiple
other,
you
know
different
different
recipes
and
instructions,
and
all
of
these
are
perfectly
configurable
on
the
back
end.
So
if
we
were
to,
for
example,
come
into
here
and
have
a
look
at
recipes,
we
can
see
that
for
the
diamond
ring,
we've
got
different
recipe
components
that
we
need
to
add
in
and
link
to
this
actual
recipe
in
a
one-to-many
relationship.
B
B
Your
elves
know
their
new
instructions
and
what
to
do
so.
This
is
kind
of
the
power
of
doing
it
in
this
in
this
way
perfect,
so
I
believe
that
that
is,
you
know
the
present
production
line.
If
anyone
has
any
any
questions
about
any
specific
part
of
how
that
how
that
works,
please
go
ahead.
Otherwise
we
can
jump
to
jesse's
part,
so
we
can
find
out
what
we
do
with
all
of
this
data.
Now
we've
got
it.
A
Fantastic,
we
had
people
in
chat,
even
speaking
up
and
saying
you
know
what
I
made
an
app
similar
to
this,
to
handle
the
registration
and
checking
for
people
financially
impacted
by
the
pandemic.
The
gentleman
named
daniel
pointed
that
out,
and
so
he
made
a
similar
app
to
that.
You
know
one
of
the
things
I
really
love
about
your
demo.
Is
it's
just
fun
for
one
that
was
great,
but
for
two
so
many
times
in
power
apps.
When
we
see
a
demo
of
something,
we
only
see
a
canvas
app.
B
Well,
actually,
this
one
was
my
first
databus
solution
because
I
had
previously
been
working
with
with
sharepoint,
so
I
was
really
excited
to
to
get
get
to
grips
with
with
using
database,
and
you
know
it
really
seemed
like
this
is
kind
of
one
of
the
the
reasons
for
me
why
databus
kind
of
stands
above
you
know
using
things
like
sharepoint.
It's,
because
you
can
have
that.
B
You
know
that
different
tier
system
of
having
a
back
end
and
a
front
end
so
that
you
can
have
people
who
are,
for
example,
like
the
elves
on
the
front
line,
they're
not
going
to
be
as
tech
savvy
or
have
like
dynamics,
365
training
or
anything,
and
they
don't
need
to.
They
can
just
use
the
the
canvas
app,
whereas
your
people
who
are
a
bit
more
kind
of
integrated
with
the
data
and
the
processes
they
can
use.
Something.
A
Yeah
exactly-
and
it
goes
back
to
what
we
just
said
at
the
end
of
sharon's
presentation.
Unlike
how
easy
it
is
to
build
right,
you
write
some
code
to
build
your
model
driven
app.
I
mean
your
canvas
app.
You
built
that
from
scratch,
but
you're
model
driven
out
you
just
configured
those
screens
to
meet
your
needs
right
and
that
probably
went
real
quick.
I
imagine
your
model
driven
development.
There
was
what
one
tenth,
maybe
of
your
canvas,
app
development
time.
B
So
we
have
you
know,
just
as
sharon
was
saying
about
getting
her
requirements
for
me,
producing
that
that
kind
of
diagram
of
that
data
model,
that
is
where
the
majority
of
the
kind
of
model
driven
app
time
goes,
is
in
setting
the
actual
model
and
then
once
you've
got
that
model.
As
you
say,
it's
really
really
quick
and
something
that
I
only
found
out
about
during
the
process
of
making
these.