►
From YouTube: Magento MSI Open Demo. August 3, 2018
Description
Todays Agenda:
REST API for MSI tutorial presentation by @Kevin Harper
https://github.com/magento-engcom/msi/wiki/Inventory-configuration-Design-and-DB-structure
https://github.com/magento-engcom/msi/wiki/Module-Structure-in-Magento-MSI
A
Let's
start
the
demonstration
today,
we
will
show
you
the
progress
done
during
this
week
and
especially,
we
mostly
will
fix
in
several
issues,
I
found
by
Kevin
Lee,
who
were
working
on
on
REST,
API
tutorials
for
MSI
and
the
longest
crate
in
this
tutorial,
and
he
was
testing
and
queuing
our
REST
API.
So
he
created
several
issue
and
we
should
get
this
even
this
week.
So
we
chose
the
fixes
and
the
let's
follow
the
agenda
which
ensured
several
minutes
ago
in
a
side
channel.
A
B
So
the
point
is
of
the
issue
was
in
in
step,
step
4,
as
we
can
see,
we
inside
here
a
z-wave
I'm.
Sorry,
we
others
we
have
this
talk
with
such
nature.
Sales
channel,
which
contains
with
website,
is
called
UK,
but
in
prayer
conditions
we
created
two
websites
which
has
a
site
called
as
UK
site
and
us
side.
So
it
means
that
that
this
code
is
isn't
valid,
but
we
do
not
get
any.
We
not
get
got
any
error
and
was
able
to
proceed
next
when
we
navigate
to
admin
panel
and
the
refresh
this
stock.
B
Refresh
this
talk
agreed,
we
get
the
exception.
No
such
entity
exception
no
section.
No
such
action
section
was
called
by
a
help
service
which
calls
get
website
website
named
by
quote
something
like
this,
and
this
area
excuse.
The
website,
repository
and
website
repository
can
found
actually
can
found
any
website
with
code
UK
and
through
this
exception,
in
order
to
prevent
it.
I
wanted
a
new
chair
to
the
sales
channel
sales
channel,
validator,
and
let
me
show
it
so.
B
B
A
C
C
A
C
A
Mm-Hmm,
so
we
like
the
mini
root
cause
of
the
issue
that
we
like
when
new
service
for
order
shipment
was
introduced.
There
was
no
possibility
so
because,
before
that
we
had
the
possibility
to
create
shipment,
we
have
shipmen
repository
and
after
that,
like
one
one
and
a
half
year
ago,
another
service
like
border
/
ship
was
introduced,
and
this
new
service
became
a
new
entry
point
for
the
shipment
creation
via
Web
API
and
there.
If
you
let
me,
can
you
can
you
please
have
an
open.
B
A
So
we
are
talking
about
this
entry
point,
so
we
need
to
investigate
the
shortest
ship
border
interface,
and
this
ship
border
interface
provides
a
possibility
to
add
extension
attributes
to
shipment
entity
which
going
to
be
created
in
the
scope
of
this
service
education
and
actually,
this
shipment
creation
argument
interfaith.
The
main
idea
of
this
interface
is
to
specify
the
extension
attribute,
which
would
be
after
that
hydrated
and
transmitted
to
shipment
entity,
but
the
implementation
of
this
service,
currently
in
magenta.
A
Does
not
does
not
make
any
hydration,
so
the
extension
attitude
comes
here
and
not
used
anymore,
so
fixing
this
issue
or
like
testing.
So
it's
a
time
when
Kenan
came
in
was
preparing
the
tutorial.
He
actually
found
the
issue
in
core.
So
probably
we
need
to
fix
it
in
corpus.
Currently,
it's
not
possible
to
extend
the
shipment
in
pore
and
we
start
with
this
problem
on
an
aside,
but
potentially
it's
applicable
for
any
other
extension
of
shipment.
A
So
just
thank
you.
Thank
You
Juan
for
your
presentation
looks
like
we
managed
to
fix
the
last
issue
and
probably
after
we
will
fix
this
issue,
we
need
to
we'll
need
to
add
the
Edit
documentation
for
this
step,
also
in
the
in
the
tutorial
created
by
cannon.
But
now,
let's
stop
talking
about
different
bugs
and
I'm,
given
the
work
to
Kevin,
who
will
show
you
the
demonstration
offer
of
the
tutorial
for
REST
API
and
the
MSI.
D
Okay,
hello,
everyone
I.
What
first
of
all
before
we
begin
I
want
to
thank
Natali
and
Sergey
for
unblocking
me
making
this
tutorial
possible.
What
I
have
here
is
a
MSI
tutorial,
that's
based
on
the
existing
order.
Processing
tutorial,
that's
been
around
since
two
out
one
and
what
I've
done
is
gone
through
each
step
of
the
process.
First,
you
configure
environment
and
you
create
some
sources.
I
have
a
bunch,
create
some
stocks
and.
D
This
is
not
published,
yet
won't
be
a
couple
more
days
to
get
some
more
reviewers
to
make
sure
everything's,
accurate
and
there's
no
typos,
and
also
this
is
a
first
step
in
in
the
final
product,
because
I
want
to
add
more
like
migrating
products
and
using
bulk
actions
and
just
make
it
a
little
more
a
couple
offensive
and
MSI
specific.
So
once
again,
thank
you
to
everyone
who
helped
me
make
this
possible
any
questions.
A
A
It
going
to
be
just
a
global
configuration
also,
we
need
to
add
additional
section
for
configuration
for
on
a
source,
editing,
page
and
additional
stock
level
configuration
on
a
stock,
editing
page
and
also,
we
will
add
the
big
orders
column
to
the
product,
editing
page,
which
will
represent
the
source
item,
configuration
and
all
the
stock
item.
Configuration
gonna
be
shown
in
the
advanced
inventory
on
a
product
page.
A
So
here
actually
in
this
document,
I
describe
where
all
these
configuration
options
gonna
be
how
they
are
going
to
be
reachable
the
admin
UI
and
how
these
options
gonna
be
to
magenta
scopin,
and
also
we
here,
I
described,
proposed
database
structure
how
to
handle,
how
to
store
and
how
to
query
this
data.
Because
for
us,
it's
pretty
important
to
to
make
a
possibility
of
the
fall
backs.
A
So,
for
example,
if
we
need
to
resolve
the
configuration
for
a
particular
source
item,
for
example,
if
we
want
to
retrieve
the
configuration
for
a
particular
source
item
by
sq
and
by
source
source
code,
it's
potentially
possible
that
this
corresponding
record
would
be
absent
in
the
database
so
that
we
need
to
make.
We
need
to
make
fallback
on
a
source
level
and
after
that,
on
a
on
a
stock
on
a
global
level.
A
So
we
need
to
go
upper
level,
make
making
a
fallbacks
and
that's
why
I
described
how
could
be
achievable
using
this
table
structure
and
using
what
SQL
queries
we
can
do.
The
main.
The
main
idea
here
was
to
to
store
all
the
configuration
options
as
independent
records
in
an
alacrity
database
table
and
that
potential
potential
drawback
of
this
solution
could
be
that
if
merchant,
if
merchant
uses
a
lot
of
configuration
on
on
the
lowest
level.
A
So
on
the
level
of
the
source
item
on
a
level
of
the
stock
item,
there
would
be
too
many
records
created
in
this
database
table
and
this
field.
Potentially
will
lead
to
performance
degradation
but,
as
we
discussed
on
one
of
our
previous
meeting
Bismark,
it's
not
sounds
like
a
pretty
common
case,
but
just
to
make
it
sure
I
created,
created
additional
polls
in
in
select
channel
and
ask
people
here
whether
it's
what
percent
of
of
products
in
a
catalogue
merchants,
usually
adjust.
A
Inventory
configuration
options
per
product
and
currently
in
MSS,
like
channel
people
mostly
voted
for
for,
like
saying
that.
Usually
it
is
less
than
ten
percent
of
products
in
a
catalog
have
adjustments
on
the
level
of
the
product
and
also
I
created
the
similar
this
in
our
poll
in
Twitter,
but
actually
in
Twitter
country,
we
have
a
little
bit
different
results.
A
So
here
during
this
week,
I
describes
in
a
module
structure
in
magenta
side
that
we
have
several
kinds
of
module
and
these
kinds
of
module
module
modules
holding
the
api's
module
module,
which
holds
the
implementation
of
business
logic
for
for
eight
guys
allocated
in
the
API
module,
and
also
we
have
to
kind
of
modulus,
are
responsible
for
admin
UI
and
for
fronting
TI.
So
all
the
Emmett
cave
test
should
be
located
in
the
admin
UI
or
front-end
here
modules.