►
Description
Agenda:
- Support of complex products Grouped and Bundle
- Mass operation with Source Items (Transfer inventory from one Source to another / Migration)
A
So
we
will
today
we
will
present
the
functionality
he
already
have
prepared.
So
this
first,
the
first
demonstration
of
this
functionality
devoted
for
migration,
ward,
transferring
data
between
sources
and
also
we
discuss
whether
it's
the
most
suitable
way
of
transferring
data
between
sources
or
not.
A
Unfortunately,
as
I
already
mentioned,
retarder
is
not
able
to
join
today's
for
today,
and
but
we
agreed
with
him
and
with
colleagues
from
magenta
order
management
to
discuss,
to
discuss
and
to
schedule
a
dedicated
meeting
tomorrow
and
discuss
whether
the
approach
we
chose
as
the
best
one
from
the
usability
point
of
view.
So
let
me
share
with
you.
Let
me
share
with
you:
come
to
the
room,
I.
A
So,
and
these
are
the
stories
you
can
see
on
my
screen
and
on
a
previous
meeting,
we
we
were
talking
about
source
level,
reservation
and
now
Sergey
is
working
on
some
prototype
and
actually
the
not
even
not
really
prototype
by
the
extension
point
which
needed
for
Paul
and
Paul
is
going
to
implement,
implemented
working
solution
because
the
reservation
and
the
level
of
sources
needed
on
his
project
and
after
that,
this
contribution
could
be,
it
could
be,
could
be
made
to
for
MSI
as
well.
So
we're
we're
syncing
up
whether
how
this
reservation
can
be
implemented.
A
What
statuses
of
this
reservation
could
be
could
be
added
and
whether
this
mechanism
of
source
level
reservation
should
be
optional,
should
be
switchable
not
so
today,
let's
talk
about
about
other
stories.
We
have
in
a
backlog,
and
today
we
will
discuss
the
possibility
of
support,
multi
source
and
functionality
for
a
bundled
product
from
group.
Product
Valerie
will
make
some
demonstration
and
will
will
describe
this
story
a
little
bit
after
that.
A
We
will
talk
a
little
bit
about
the
configuration
and
source
level
configuration
and
you
API,
which
which
currently
done,
which
we
don't
currently
help
in
in
MSI,
because
currently
all
the
configuration
we
have
is
a
stock
level
configuration
and
we
just
make
proxy
we
proxy
in
all
the
call
to
to
existing
elementary
configuration.
So
we
don't
have
own
own
API
for
this
and
we
even
don't
have
storage,
so
we
will
proxy
it
to
the
to
the
legacy
table.
And
after
that
we
will
discuss
the
story.
A
Whether
it
would
be
straight
forward
for
merchants
how
to
migrate
existing
data
after
the
after
the
migration
to
magenta
to
loot
3
with
msi
on
board,
whether
it's
a
most
suitable
way
to
migrate
to
from
single
stock
inventory
to
mounted
stock
one.
So
Slava
saw
will
make
a
presentation
and
because
earlier
because,
as
I
already
mentioned,
record
unfortunate
a
concern
and
make
this
presentation
by
himself
and
we
will
discuss
whether
there
are
some
drawbacks
flows
or
some
changes
should
be
introduced
to
improve
this
process.
B
B
My
opinion,
we
need
to
include
this
tourism
as
milestone
and
finish
it
as
big
as
possible
because,
as
you
know,
we
created
own
multi-source
inventory,
multidimensional
indexer.
This
ability
to
sort
the
data
per
dimension
now
okay
is
dimension
installed,
but
since
we
don't
have
support
for
group
added
bundled
products
in
the
illnesses,
we
need
to
use
legacy
in
this
for
these
types
of
products,
and
that
means
that
we
can
disable
legacy
catalog
inventory
model
and,
as
you
remember,
it
was
one
of
our
main
goals.
Replace
legacy
model,
this
new
one.
B
Regarding
the
group
of
products,
I
don't
see
a
huge
concerns.
It
will
be
pretty
familiar
with
two
configurable
code
of
illness.
We
need
to
check
all
of
children
and
if
one
of
them
is
saleable
that
mean
the
public
is
saleable.
I
have
only
one
not
just
concerned
about
default
entity
for
child
products.
We
can
choose
default
quantity
for
some
child
of
group
problems
because
generally
it
looks
like
stock
option
but
is
not
source
option.
B
C
B
B
B
B
B
So
you
can
see
that
we
have
required
options,
we
have
options,
she
bundle
together.
We
have
default
quantity
so
and
we
need
to
check
all
combination
of
this
so
generally,
it's
looks
like
big
story
and
we
need
to
use
some
temporal
table
during
indexation
in
the
same
way
as
now
is
use
it
in
for
for
making
this
field
ownership.
So
I,
don't
I,
don't
know
we
can
mark
open
public,
past
M
size
and
its
large
size.
A
A
A
A
We
would
need
anymore
existing
indexation
provided
by
catholic
inventory,
so
we
can
drop
that
indexation.
We
can
decouple
from
the
catalogue
an
inventory
indexation
and
we
can
drop
their
limitation.
We
can
say
help
44
souls
in
the
fall,
stop
and
the
fourth
source
in
the
fall
stock
could
be
considered,
could
be
treated
the
same
way
as
any
other
source
and
stopped
my
system
before
that.
We
have
a
special
meaning
and
special
limitation
for
this
antigen
assistant.
A
We
need
to
boost
the
priority
for
supporting
supporting
multi-source
capabilities
for
both
the
group
and
the
bundled
product,
because
before
that,
we
make
MSI
and
the
new
inventory
mechanism
to
be
coupled
to
Cadillac
inventory
existing
existing
implementation,
so
that
it
means
that
we
can
just.
We
can
just
dismantle
Cadillac
inventory
module
and
we
still
because
we
are
still
reusing
part
of
this
functionality
and
especially
indexation
mechanism
for
bundle
and
group
products
and
another
stuff.
If
is
the
configuration,
so
Thank,
You
Valerie,
for
presentation
of
of
the
store
is
devoted
for
group
and
bundled
products.
C
C
A
We
had
at
the
time
when
we
were
working
in
Cork,
so
they
little
bit
dated
at
that
time.
We
plan
to
make
a
calculation,
for
example,
for
bundle
for
group
product
on
a
level
of
source,
but
currently,
when
we
started
to
so,
for
example,
it
was
not
possible
to
to
deliver
some
variation
or
bundle
from
one
source
and
another
variation
from
another
options
from
another
source.
So
when
we
were
making
a
calculation,
how
many
bundle
product
we
have
we
supposed
to
calculate
the
variations
allocated
just
on
the
level
of
the
single
source.
A
A
C
F
F
F
F
F
F
G
A
A
A
All
this
operation
needed
from
from
the
merchant
point
of
view,
because
it's
hard
for
me
when
merchants
need
to
unassign
non
non
zero
non
zero
operation
because
usually,
probably
the
main,
the
main
steps
which
will
merchants
follow,
after
their
upgrade
from
magenta
to
the
two
to
magenta,
to
the
three
with
a
mess
on
board
and
when
he
would
like
to
start
using
the
NFI
he
will.
He
will
make
a
bulk
migration
from
default
source
to
some
newly
created
source
and
after
that
migration,
you
will
see
that
we
don't
make
an
assignment
from
the
default
source.
A
So,
for
example,
merchants
will
create
this
new
source.
He'll
make
the
transfer
inventory
to
this
new
source
and
the
after
that
inventory
would
be
transferred.
He
will
still
have
the
four
source
as
with
zero
quantity.
So
after
that
he
can
unassign
all
the
data
from
the
default
source
just
to
remove
this
default
source
zero
from
from
the
grid
from
all
the
grease
and
from
all
the
reports-
and
this
is
actually
what
probably
most
of
the
merchants
will
do
after
the
migration
to
magenta
to
the
tree
with
a
messiah
on
board.
A
If
they
was
like
to
use
multi
source
inventory'
functionality,
but
from
my
perspective,
they
assign
an
unassigned
source
to
inventory,
is
not
an
independent
operation
but
sounds
like
property
of
transfer
transfer
operation.
So,
for
example,
merchants
can
apply
the
transfer
I
won't
visit
here
and
he
would
like
to
unassign
data
from
the
from
the
default
source
and
the
also
Adam
I.
Don't
know
whether
there
are
valid
business
reason
to
to
have
an
assign
inventory
source
separation
which
just
create
an
empty
source
items
because
empty
source
items
currently
don't
in
fluent
the
sale
ability,
quality.
A
The
source
item
will
invest
in
segregation,
we'll
just
bring
the
zero
value,
so
they
will
not
affect
any
house
the
sell
ability
quantity.
So
that
was
a
question
I
wanted
to
discuss
with
the
record,
but
Ricardo
currently
is
not
on
a
call,
and
the
wheel
has
a
separate
discussion
with
him
and
with
Alex
tomorrow
afternoon.
But
I
would
like
to
raise
this
question
today
with
all
those
who
are
on
a
call
today,
Alessandra
and
Anton.
Maybe
you
have
your
opinion
regarding
that?
A
A
So
I
believe
that
the
system
should
follow
the
Polka
yoga
principle,
so
it
should
not
be
possible
just
to
easily
break
the
system,
because
if
merchants
will
apply,
some
calls
on
unwisely
and
the
system
should
be,
should
be
quite
straightforward
and
easily
to
use.
But,
for
example,
now
choosing
some
product
like
it
could
be.
It
could
be
a
state
for
single
single
stock
merchants
who
upgraded
to
a
messiah.
So
he
see
he
sees
that
there
are
some
additional
operation
appears
and
he
decided
to
unassigned
inventory
source.
Why
not?
A
So
as
for
me,
there
is
no
valid
business
case
for
merchants
to
make
an
unassigned
for
non
zero
source,
so
maybe
it
makes
sense
to
make
an
unassigned
operation
after
we
made
a
transfer
just
to
remove.
This,
for
example,
exist
default
source
22
zero.
If
he,
if
merchants
don't
want
to
bother
any
more
with
the
zero
quantity.
A
A
A
Yeah,
actually
that
so
or
intro
the
question
shouldn't
listen
to
check
if
they
try
it
on
a
sign
with
positive
memory
to
to
recommend
mass
transfer
on
a
sign,
yeah,
maybe
but
I
think
actually
like
from
my
perspective.
I,
don't
I,
don't
see,
I,
don't
see
any
business
case.
Why
merchants
can
want
to
make
an
honest
I
mean
from
the
non-zero
source
at
all,
because
this
actually
means
that
you,
you
want
to
drop
existing
inventory,
not
to
move
to
another
and
not
another
source,
but
just
drop
it
at
all.
H
So
as
far
as
the
product
has
quantities
in
other
sources,
this
shouldn't
be
a
problem,
but
if
the
merchants
want
to
unassign
the
only
source
associated
to
a
broader,
this
leaves
the
system
and
consistent
and
I
would
prevent
this
kind
of
inconsistency
to
happen.
So
probably
I
think
that
there
may
be
there
may
be
scenarios
in
which
merchants
want
to
unassign
a
stock,
sorry,
a
source
which
still
has
quantities.
Maybe
yes,
some
sources
get
damaged
so
along
with
all
the
products
countries.
H
So
there
may
be
a
case
in
which,
in
reality,
the
merchants
have
the
need
to
an
assign,
but
I
think
that
in
that
case
he
should
and
he
or
she
can
transfer
the
quantities
because
say
that
the
quantities
have
been
destroyed
along
with
the
source,
but
I
think
that
having
a
product
without
any
source
assigned
is
not
consistent
anymore.
So
probably
this
should
bring
to
disabling
the
product
or
something
like
that.
H
So
the
first,
the
first
and
easier
thing
to
do
is
probably
in
forcing
forcing
the
merchant
to
transfer
or
to
at
least
sign
second
source
to
the
product
before
before
and
signing
it.
So
some
checks,
some
validation
checks
that
prevent
an
assigning
the
only
source
assigned
to
a
product,
but
I'm,
not
domain
expert,
so
probably
I
would
I
would
ask
mark
for
for
real
news
cases,
but
I
agree
that
leaving
the
system
inconsistent
I
want
to
leave
the
system
inconsistent,
but
I
prefer
not
to
leave
the
system
inconsistent,
but.
A
H
I
mean
no.
If
the
product
is
saleable
and
at
a
certain
point,
I
remove
all
the
sources.
I
don't
have
any
more
available
quantity
for
that
product.
I
mean
in
consistence
by
by
inconsistent
I
mean
that
the
product
becomes
not
saleable.
This
can
be
real
case.
Real
use,
use
case,
but
I'm
not
eligible
to
say
it
is
so
by
inconsistent.
I
mean
that
you
lose
any
possibility
to
to
sell
that
product,
because
you
you
do
a
mass
unassigned
of
all
quantities
from
that
source
and
that
product
is
not
syllable
anymore.
A
Yeah
and
it's
not
saleable,
and
we
so
it's
not
restorable.
So
you
get
this
data
back
anymore
because
potentially,
if
the
data
was
transferred
to
another
store,
you
can
potentially
make
the
opposite
operation
and
make
the
transfer
back
to
get
that
quantity
back.
But
if
we
just
unassigned,
we
just
lost
the
data
yeah.
H
A
B
A
A
H
A
A
H
H
I
think
you
know
we
should
figure
out,
which
are
the
real
use
cases
merchants
can
can
have
I
mean
I
am
I,
understand
the
need
to
transfer
some
countries
from
a
source
to
another
and
then
I
understand
the
need
of
an
assigning
source
say
that
you
are
moving
your
your
goods
from
one
source
to
another.
This
is
a
real
news
case,
but
the
unassign
meant
is
is
I
confess.
H
D
A
D
A
A
H
A
So
looks
like
we
have
just
five
minutes
left
and
another
topic
is
pretty
big
to
fit
in
this
five
minutes.
So
I
proposed
to
finish
today's
meeting
I
will
share
their
accordion
of
today's
meeting.
We
in
MSI
it's
like
channel,
because
maybe
there
would
be
guys
we
will
share
their
opinion
on
this
on
this,
because
the
the
functionality
of
reassignment
is
pretty
important
for
us,
especially
because
it
would
be.
A
It
would
be
especially
important
for
the
on
board
in
on
MSI,
because
we
consider
that
all
the
existing
installation
are
single
stopped
and
they
somehow
need
to
be
migrated
to
the
multi
stock
and
if
we
will
provide
the
really
straightforward
and
easy
way
to
migrate
to
the
multi
stock
inventory.
This
will
definitely
ease
the
process
and
will
make
the
process
of
migration
and
the
satisfaction
of
merchants
who
use
em
aside
much
much
higher.
F
I
just
want
to
say
one
word
that
when
I
was
dating
cuz
SPR
I
was
expecting
then,
when
we
assigned
some
sources
like
we
do,
for
example,
when
we
create
configurable
products,
the
assign
source
and
you
after
this
immediately
said
some
items.
They
said
the
inventory
on
this
source,
but
when
I
saw
that
only
it
just
assigned
source
with
zero
quantity,
it's
for
me.
It
was
also
not
so
properly
on.
You
know.
Still,
you
would
need
or
manually
add
some
inventory
to
each
or
do
import,
but
still
you
have
work
to
do.
Yeah.
A
So
this
is
not
kind
of
a
kind
of
final
state,
it's
kind
of
beginning
State
or
intermediate
state.
So
merchants
still
need
to
make
some
operation
manually
whether
make
manual
update
of
the
quantity
wore
after
that
make
the
import
process.
But
if
he
needs
to
make
a
new
process
fever,
he
can
make
the
import
process
without
this
assignment
operation
at
all.
Yes,.
F
Right
away,
or
only
if
it
is
it
possible
to
really
when
you
assign
source
for,
for
example,
if
you
want
manage
with
hundreds
of
products,
for
example,
and
you
want
to
assign
some
them
all
for
some
source,
maybe
it
would
be
reasonable
to
set
quantity
for
the
source
and
then
then
it'll
be
useful.
Yeah.
F
D
A
That's
correct
Lori,
but
what
to
do?
For
example,
if
we
are
making
a
bulk
or
assignment
with
like
three
different
products,
and
each
of
this
products
has
different
quantity
like
100,
200
and
300
like
for
s.
Q
1
is
Q
2
in
his
career
three,
so
we
it's
really
hard
to
make.
This
deviation
because
the
quantity
could
be
different.
A
So
we
were
thinking
about
this,
how
how
to
make
it
more
usable
to
split
to
split
the
inventory,
but
actually
we
did
not
find
how
to
split
it
at
the
time
of
the
bulk
operation,
because
because
you
can
make
it
split
on
the
level
of
one
product,
but
it's
really
hard
to
imagine.
How
can
we
do
it
in
the
level
of
bulk
operation
when
we
are
working
with
many
products
in
the
scope
of
one
operation
makes.