►
From YouTube: MSI Open Demo. November 24, 2017
Description
1. Integration MSI with existing CatalogInventory code. Checkout @Bartłomiej Szymański
2. The general strategy of CatalogInventory and MSI integration @iminiailo
3. Static test which checks for required strict typing usage @Dwayne Hanekamp (presented by @vnayda)
4. Fix to Replace strategy for SourceItem import and cover that with Integration test (@larsroettig)
5. Introduce a link between Default Website and default Stock (did not work, because Default Website created with plain SQL query ) @Sinisa (presented by @iminiailo)
6. Product Import. Qty field supposed to be handled by MSI APIs and saved to Default Source Item @joshcarter (presented by @iminiailo)
7. Multi-Dimensional Indexes (@vnayda)
A
Not
a
lot
of
attendees
today
because
currently
holidays
in
the
United
States.
Yes,
yesterday
was
a
sense
given
day.
Today
is
the
day
after
since,
given
day
so
from
from
the
magenta
multi-source
inventory,
team
I
would
like
to
say
big.
Thank
you
to
all
the
contributors
who
work
in
with
us
for
making
the
msi
real,
who
contributing
with
own
time
with
own
ideas
and
own
code,
and
thank
you.
A
So
there
are
not
a
lot
of
attendees,
but
there
are
quite
a
lot
of
things
to
to
show
and
I
believe
those
who
would
watch
this
presentation
later
would
be
enjoying
seeing
the
status
update
of
the
functionality
which
will
present
today
so
I
sure
to
gender
a
little
bit
earlier.
So,
according
to
the
agenda,
Bartek
will
start
the
presentation
and
we'll
show
how
msi
is
currently
integrated
with
the
existing
kasich
inventory'
functionality.
On
the
example
of
checkout
process,
Oh
yep
so
Bartok
feel
free
to
share
your
screen.
Ok,
hello,
guys!
B
B
B
B
B
D
B
When
I
refresh
my
back-end
product
details
page,
you
can
see
that
legacy
Katoch
inventory
stock
item
quantity
is
set
now
271
according
to
latest
order
and
integrated
with
msi
inventory,
see
there.
There
is
also
the
same
number,
so
that's
it.
You
can
see
that
now,
where
MSI
catalog
integrated
with
old
Tokina
Tori
stock-
and
this
is
looks
quite
simple-
but
during
this
this
implementation
of
this
feature.
There
are
plenty.
A
A
So
what
we
are
going
to
do
this,
we
are
going
to
rob
this
data
robbed
this
resource
model
save
coal
into
a
round.
Plugin
and
actually
check
what
the
data
gonna
be
changed
and
save
the
data
to
the
default
source
item
and
synchronize
the
data
to
two
previous
table,
because
we
need
to
keep
the
previous
tables
so
the
stock
item
and
stock
status
up-to-date.
A
Another
thing:
if
when
we
have
the
stock
detection
operation,
for
example
during
the
checkout
process,
this
bar
to
show
you
so
all
of
the
place
is
supposed
to
be
a
refactoring
in
the
way
of
using
new
mechanism
of
ad
reservation.
Because
before
that
we
did
not
have
a
dedicated
API
for
the
stock
deduction.
All
the
API
we
had
was
for
the
stock
setting,
but
currently
all
of
that
legacy
code
supposed
to
be
changed
and
the
refactor
it
in
a
way
of
using
our
reservation,
append
service.
And
so
that's
the
second
case.
A
Another
case
we
sub
to
support
is
when
the
new
system
are
using
the
new
api,
so
the
ad
reservation,
for
example,
and
for
the
ad
reservation,
we
also
have
a
plugin
and
using
that
plugin
we
supposed
to
update
the
old
tables
for
the
stock
item
and
the
stock
status
and
update
the
quantities
of
this
data.
With
the
plain
SQL
queries
for
the
stock
item
and
the
stock
start
of
stables-
and
it's
very
important
here
to
use
a
plain
SQL
queries
to
prevent
the
circular
dependency
between
the
legacy
code
and
the
MSI
code.
A
So
we
no
need
to
use
the
stock
item
model
or
resource
model
inside
this
plugin
and
the
last.
The
last
use
case
we
need
to
consider
is
when
we
have
date
in
the
source
item.
Actually,
when
we
updating
the
default
source
item,
we
also
should
plug-in
I
this
behavior
and
we
need
a
the
legacy
tables,
storing
the
data
for
the
Catholic
inventory
stock
item
and
the
stock
status
table.
A
A
He
provided
a
static
test
which
actually
checks
using
the
whites
list
and
the
black
list,
all
the
all
the
files
being
changed
that
this
files
supposed
to
use
his
thick
typing
in
our
project,
because
currently
we
decided
to
follow
the
agreement
that
we
will
use
the
strict
typing
for
the
all
new
files
and
you
all
behavior
be
on
edit
in
the
scope
of
the
MSI,
but
sometimes
feel
good
about
it.
And
we
don't
have
the
precise
test
which
will
cover
the
functionality
and
prevails
and
prevent
us
from
making
a
mistake.
So
why
Larry.
E
E
E
Go
to
the
Travis
page
and
we
could
see
that
we
have
a
favorite
static
test
open
result
and
we
it's
good,
see
error
that
we
have
problem
in
our
class
without
static
declaration,
so
guys,
please
take
into
account
when
we
do
creative
code,
please
a
declaration
and
fix
static
test.
If
you
have
some
mistakes,
this
declaration,
they
think
that's
all
yeah.
A
A
So
actually
the
check
will
happen
among
this
list
of
modules
specified
in
a
white
list,
and
so
potentially
all
new
model
is
supposed
to
be
added
to
this
white
list
and
if,
for
example,
we
decide
that
some
particular
file,
for
example,
which
relies
on
a
legacy
code,
it's
okay
to
have
it.
So
we
have
another
black
list
which
would
be
subtracted
out
of
the
list
of
files
changed.
So
it's
also
possible
to
make
a
decision
that
it's
okay
to
have
the
file
without
stick
typing.
A
F
C
Okay,
yeah
at
the
mage
test
passed
last
weekend
on
Saturday
at
a
contribution
day.
I
fix
drat
and
the
red
bird
happens
in
the
past
because
we
match,
or
we
worst
murdering
some
delay,
delete,
behavior
and
yeah,
and
the
task
tell
ok
to
delete
behavior
works,
not
so
as
expected,
but
it
was
expected
and
now
I
described.
C
It
is
wrong
because
if
you
delete
a
shirt
in
every
source,
it's
not
good,
because
you
must
rebuild
many
Starks
and
it's
not
if,
once
source
don't
have
anymore
decide
on
you,
don't
want
to
delete
all
of
them,
and
now
I
documented
this
behavior,
so
I
really
create
in
the
future.
Some
wiki
page
about
this
behavior
and
also
I
fix
this
test
for
the
behavior
come
on.
This
was
my
task
as
a
dementia
test.
First
documentation
for
you.
Thank
you.
A
So
currently
we
just
fix
it
with
the
integration
all
tested,
behavior
that
we
can
import
data
for
one
particular
source
and
all
other
data
wouldn't
be
affected
for
other
sources.
So
same
flowers
for
your
contribution
and
let's
go
to
another
presenter
in
our
list.
So
that's
gonna,
that's
gonna
be
Sinisa,
but
sinistra
is
not
on
the
call.
A
First
I
see
Nisha
provided
really
good
integration
test
which,
which
is
covering
the
cool
checkout
process,
so
place
in
a
reservation
which
supposed
to
make
a
deduction
for
both
old
catalogue,
inventory,
api's
and
then
you
MSI,
inventory
API.
So
actually
this
integration
test
will
help
us,
so
it
could
be
short
as
an
end-to-end
scenario
which
will
help
us
to
check
whether
we
have
some
problems
with
integration.
For
example,
it
would
be
useful
for
Bartok,
who
is
doing
currently
the
synchronization
between
between
catalogs
inventory
and
the
inventory
catalog.
A
So
that
was
the
update
from
Tunisia
and
currently
I
will
show
you
the
result
of
work
which
was
contributed
by
George
Carter.
That's
our
new
contributor
from
London,
whom
I
met
on
the
mage
Titans
in
Manchester
and
actually,
unfortunately,
Josh
also
could
not
attend
today's
meeting.
But
he
sent
me
a
video
recording
of
his
work.
So
I
will
show
you,
the
video
recording
currently
so
I'm
sharing
my
screen
and
yep
and
let's.
A
Yes,
cool
so
here,
George,
making
some
show
showing
the
file
for
important
date
and
he
trying
to
pay
attention
that
there
is
like
100
items
for
the
SQ.
Now
he
makes
a
validation
of
that
file
and
after
that,
he's
making
import
of
that
file
with
the
data.
Now
we're
going
to
the
product
page
and
making
an
update
of
that
page
and
after
the
page
is
updated.
We
see
that
data
is
applied
for
the
default
source
and
the
default
source.
A
Quantity
is
100,
so
actually
the
same
as
we
had
in
our
import
file
now
George
making
making
changes
to
this
file
in
change
in
quantity,
from
80
to
from
100
to
80,
so
80
supposed
to
be
new
quantity
which
which
should
override
the
existing
one.
So
he's
saving
changes
in
that
file
and
he
is
going
to
upload
this
file
one
more
time
so
he's
going
to
import
page.
A
He's
he
is
choosing
the
product
import.
So
actually
this
task
is
adaptation
of
old
product
product
import
process,
because
you,
because
our
old
product
import,
also
test
quantity
data.
So
we
have
the
quantity
and
is
in
stock
and
the
different
different
configuration
of
the
stock
item.
So
now,
Josh
use
the
product
as
a
import
type
and
the
he
children
the
add
an
update
strategy
and
provided
this
new
update
file.
A
And
now
we
are
going
to
the
product
page
update,
updating
this
page,
and
now
we
see
that
quantity
was
updated
and
now
it's
80
not
hundred
as
it
was
before.
So
this
is
actually
the
presentation
which
Josh
made
for
MSI
and
actually
the
idea
of
of
the
story
he's
working
on
right
now
that
we
actually
I
will
show
you.
A
A
So
we
need
to
adopt
current
product
import
and
export
behavior
to
support
the
data
update,
which
should
lead
for
the
MSI
data
changes.
So
currently
we
just
made
so
we
just
presented
you
how
the
quantity
fields
updated
and
now
it
effects
the
new
Messiah
API.
So
we
made
we
made
an
integration
with
an
MSI
to
the
old
import/export
process
and
what
we
will
also
add.
So
we
will
extend
the
format
of
the
default
default
import
file
and
we
will
add
the
possibilities
to
specify
the
quantity
of
product
on
different
sources.
A
So,
for
example,
this
is
one
of
the
possible
format
how
the
data
in
a
quantity
field
could
be
represented
so,
like
the
quantity
of
the
some
particular
skew
on
the
source,
2
is
300
unless
sorcery
is
200,
the
source
for
is
600,
so
George
currently
is
working
on
the
next
ticket,
which
will
support
the
different
formats
for
the
quantity
field.
So
this
that
his
current
ticket
and
the
hero
he
will
show
his
update
pretty
soon.
A
E
Hey
guys,
if
you
remember,
if
he
already
he'll,
be
improvement
from
an
aside
project
to
Magento
or
system,
it
was
about
validation,
framework
about
improvement,
the
UI
components
on
and
now
looks
like
we
close
to
hell
one
more
big
improvement
to
Magento
framework.
It
is
related
again
to
UI
components,
to
fixing
some
bug
and
one
of
our
big
improvements
related
to
our
index
system.
E
We
don't
want
to
put
all
data
or
our
stock
data
in
our
in
you
know
single
tape.
We
would
like
to
have
one
stock
per
one
table
and
we
call
it
dimensional.
We
would
like
to
help
multi-dimensional
in
Texas,
but
uninsured,
unfortunately,
in
Texas
from
magenta,
don't
don't
provide,
possibility
to
help
multi-dimensional
indices
and
we
introduced
a
few
classes
if
you
interfaces
how
to
improve
this
horror-
and
you
can
see
that
we
provide
a
multi
dimension,
indexes
namespacing
early
primer
and
provide
a
lot
of
classes,
how
true
work
is
multi-dimensional
entities.
A
Yep,
thank
you
guys
and
I
believe
we
will
finish
the
multi-dimensional
in
this
pretty
soon
and
we'll
describe
that
on
our
wiki
page.
So
it
supposed
to
be
pretty
big
improvement
for
the
who
magenta
so
I
believe
that
was
the
last
point
in
our
today's
agenda.
So
we
can
probably
finish
our
today's
demo
meeting
and
and
guys
from
a
Twix
team
who
invited
me
and
Valera
to
to
their
office.
We
are
going
to
start
the
magenta
meet
up
pretty
soon
and
we
have
a
presentation
there,
so
we
can
them.
A
We
can
make
us
way
too
long
so
guys,
since
thank
you
a
lot
for
your
contribution
again
and
don't
hesitate
to
ping
us
any
time
because,
as
you
see,
we
have
quite
a
lot
of
different
interesting
tasks
on
and
a
sidetrack
and
where
we
are
pretty
close
to
the
to
the
final
bolo
for
ease
and
of
MSI
and
magenta
to
the
3ds.
Thank
you
very
much
and
thank
you
for
being
with
us.