►
From YouTube: Import/Export Weekly call 3rd Jan 2018
Description
Recording of the import/export weekly call from the 3rd of January 2018.
This project focuses on the https://github.com/magento-engcom/import-export-improvements repository with the aim to provide some key bug fixes in the 2.3 release of Magento 2.
If you would like to get involved in the project please see the github issues or contact the Magento Community Engineering team for more information.
A
So
right:
okay,
it's
recording
now,
okay!
So,
as
I
said,
we
have
to
face
one
board
which
includes
all
the
all
the
issues
that
have
been
approved
and
kind
of
validated
as
well.
So
the
first
one
we
will
have
a
look
at
today
is
the
group
products
not
associated
on
import.
Basically,
when
you
are
importing
group
products,
the
products
themselves
will
be
imported
and
but
they
would
not
be
assigned
so
you'd
have
your
group
product,
but
no
symbol
of
products
assigned
to
it
and
PETA
borrowing.
Peta
already
has
this
poor
request.
A
It
is
against
the
main
repository
I'm,
not
100%,
sure
whether
it
will
stay
there
or
whether
will
migrate
this
to
our
repository.
But
that's
something
we
want
to
discuss
in
this
meeting
as
well,
and
this
issue
is
being
processed
by
Mateus
at
the
moment.
So
as
far
as
I
understand,
there
was
an
issue
with
getting
the
product
SKUs,
with
a
kept
less
rather
than
with
a
lower
case.
So
hopefully
this
is
this.
A
Progress
will
fix
that
issue
and
once
the
review
is
being
completed,
it
will
go
on
to
the
testing
step
as
well,
and
then
at
that
point
goes
three.
So
hopefully
there
will
be
nothing
to
do
with
this
one
and
if
there
is,
it
will
probably
be
up
to
Peter
to
do
it
since
it's
assigned
to
him.
But
if
you
would
like
to
you
can
jump
into
that
issue,
you
can
have
a
look
at
it
and
you
can
also
have
a
look
at
the
pull
request.
A
So
if
you
feel
like
you
have,
if
you
want
to,
if
you
want
to
make
a
comment
or
view,
then
feel
free
to
jump
onto
that
one
and
alright,
then
the
next
one,
which
is
also
assigned
we
have
assigned
to
Frederico
I,
don't
mispronounced,
anything
apologies
if
I
do-
and
this
is
okay
good.
It's
basically
that
you
can.
If
you
import,
ask
you
and
it
contains
space
in
it,
then
you
will
get
products
which
technically.
A
B
B
B
You
know
basically
overriding
the
SKU
that
you
entered
when
you
do
the
same
from
the
import
functionality,
it
will
throw
you
an
error
instead
of
behaving
the
same.
So
the
main
thing
here
for,
in
my
perspective,
is
you
know
to
define
what
would
be
the
preferred
way
from
Magento.
What
would
be
that
the
correct
way
to
handle
SK
use
that
already
exists-
and
you
know
change
it
this,
so
it
behaves
the
same
between
the
admin
and
the
import/export
process.
A
Yeah
yeah,
for
me
they
make
sense.
So
basically
we
need
to
figure
out
what
what
the
behavior
should
be
and
ideally
I,
don't
think
they
should
be
different,
but
I'm
not
sure.
We
also
had
two
other
comments,
one
from
Peter
and
one
from
another
user
I,
don't
know
what
their
name
would
be,
but
basically
saying
that,
especially
on
the
import,
the
skews
will
be
coming
from
an
SME
or
an
ERP
system,
and
so
the
skews
themself
should
not
be
manipulated
from
the
Magento
system.
A
In
that
case,
I
think
in
this
case,
both
of
people
are
saying
that
we
shouldn't
be
manipulating
the
scheme,
but
I'd
like
to
discuss
that
here,
a
little
bit.
Maybe
one
of
the
two
Eugene's
had
has
an
idea
about
this
from-from
kind
of
the
magenta
core
point
of
view
or
anyone
else.
If
anyone
else
has
a
an
opinion
here,
then
they'll
be
good
to
discuss
that,
and
then
we
can
figure
out
a
way
forward
here.
B
A
You,
how
would
that
behave
with
that
behave
differently
by
the
admin
or
as
well
as
the
input
there?
So
if
an
admin
was
to
enter
duplicates
q,
would
you
expect
it
to
throw
an
error
to
the
user
sake?
The
security
exists,
or
would
you
expect
it
to
try
and
build
the
unique
skill
from
what
you've
entered
I.
B
B
C
A
Okay,
cool
sounds
like
it's
fairly
unanimous
they're
great.
Thank
you
yeah.
It
sounds
like
it's
pretty
unanimous
there
with
regards
to
with
regards
to
the
admin
section
that
should
be
updated
to
to
show
that
this
product
already
exists.
At
that
point,
you
can
always
consider
adding
a
link
or
something
to
the
error
message
directing
the
user
to
that
specific
product.
A
Okay,
if
not,
then
I
think
that's
fairly
okay
explanatory,
so
Alfredo
Rico.
If
I
leave
that
with
you,
would
you
be
okay
to
update
the
ticket
with
what
we've
discussed
and
then
also
feel
free?
Since
we
already
talked
about
this,
so
you
can
start
working
on
on
this
issue
as
it
is
and,
of
course,
if
you
need
any
help,
that's
what
we're
here
for
reach
out
there,
either
me
or
someone
else
in
the
team.
A
B
I
can
just
one
question:
yes,
this
ticket,
so
this
ticket
will
we'll
cover
also
in
the
modification,
the
admin.
So
it
doesn't
happen,
be
you
know
the
one
it
just
throw
you.
The
error.
Yeah
L
mean
I
mean
we
are
talking
about
here,
not
only
the
import/export
functionality,
but
how
the
admin
work
so
just
to
be
completely
sure
that
this
ticket
will
cover
that
change
as
well.
Yep.
A
Person
personally,
I
would
suggest
that
yeah
we
covered
both
because
we
want
to
have
the
functionality
the
same,
but
if
you
would
like
to,
we
could
always
consider
having
two
people
work
on
this.
One
person
work
on
the
app
and
one
person
work
on
the
import.
If
you
think
that
would
be
beneficial.
Yeah,
okay,
I.
A
A
You
okay,
so
that
is
the
first
one
on
board
and
then
the
next
one
is
a
very
interesting,
complex
and
interesting.
One
I
think
this
is
probably
one
of
the
harder
ones
that
is
in
the
system,
and
it's
basically
that
the
system
as
it
stands
the
system
doesn't
allow
you
to
empty
data,
essentially
with
the
import.
A
This
one
we
currently
have
a
pull
request
in
place
to
the
end
comm
important,
oh
yeah,
so,
and
if
anyone
is
doing
work
on
these
issues,
the
pull
request
go
to
the
and
comm
import/export
improvements,
rather
than
the
main
repository
be
great
and
I.
Didn't
do
this
I
just
migrated
the
poor
request.
So
again
anyone
can
pick
this
one
up
and
continue
it.
A
A
We
were
talking
about
this
in
the
original
poor
request,
which
is-
and
we
were
talking
about-
the
fact
that
this
is
kind
of
counterintuitive
and
I
would
love
it
to
be
that
if
there
is
an
empty
value
in
the
CSV
that
it
would
be
treated
as
you
want
to
delete
it,
and
that
does
cause
could
cause
or
does
cause
in
this
case
a
few
issues.
He
had
already
set
up
that
way
and
hope
that
this
is
he.
A
A
B
D
So
let's
say
the
null
means
that
feel
the
this
filled
with
the
default
value
for
the
database,
but
the
problem
the
releases
that
it
introduces
backwards
and
compatibility
from
the
factional
points
of
view.
So
any
any
new
behavior
to
this
basically
should
be
configurable
like
some
some
buttons,
some
config
in
the
system
configuration
we're
going
to
say.
I
can't
remember
now
the
details,
because
I've
had
some
discussions
indeed,
but
it's
like
a
month
ago.
I
will
take
a
look
again
at
this
and
maybe
drop
some
comments
on
the
on
the
pull
request
or
issue
itself.
A
Okay,
okay,
does
anyone
from
the
kind
of
community
group
feel
like
they
would
like
to
take
this
on
at
the
moment
in
terms
of
helping
out
with
the
research
and
coming
up
with
an
option,
or
should
we?
Otherwise
we
can.
We
can
wait
a
little
bit
for
for
Eugene's
kind
of
research
there
as
well
I'm,
okay,
with
either
options.
A
A
A
So
in
term
there
are
certain
values
that
take
on
the
the
string
value,
such
as
visibility.
I,
think
visibility
is
a
good
example
of
this
one
and
because
it's
the
string
value
depending
on
what
look
Hallie
you
have
in
place,
you
will
get
different
results.
So
in
this
case,
in
the
case
that
the
person
has
noted
yeah
here
we
go
they're
using
the
Spanish
pack
and
when
they
use
the
actual
Spanish
translation,
which
is
what
you
get
when
you
run
the
export
as
an
admin
in
in
the
Spanish
locale
II.
A
A
D
A
Go
we
have
six
people,
so
there
are
one
two
yeah
three
of
us
from
Majuro
and
three
community
members.
There
are
more
issues
in
here,
but
these
are
the
kind
of
these
four
of
being
kind
of
highlighted
as
the
the
higher
priority
issues
does.
Anyone
feel
like
this
is
the
sort
of
thing
they
would
like
to
take
on
this
issue
with
regards
to
locality
and
and
options.
A
A
D
A
Said
please
have
a
look
through
them
and
see
if
there's
anything
from
those
titude
that
you
think
you
would
really
like
to
take
on
I
would
encourage
you
feel
free
to
feel
free
to
take
a
risk,
and
we
will
support
you.
So
if
you
don't
feel
comfortable
with
something
this
is
about
learning
and
about
we're
here
to
help
you
out
as
best
as
possible,
so
feel
free
to
I,
don't
know
to
come
and
talk
to
us
and
say
I'll
help
out
with
there
empty
rows.
A
I'll
help
you
gene
kind
of
figure
out
a
few
options
or
you'll
help
me
figure
out
something
as
well.
That
would
be
great
okay,
so
there
are
a
few
other
things
I'd
like
to
talk
about
with
this
call.
The
next
one
is
with
regards
to
migrating
of
issues
or
pull
requests.
So
at
the
moment
we
have
but
I
think
they've
all
just
be
migrated
yet
so.
A
We
don't
currently
have
anything
in
place
that
will
do
the
same
thing
with
the
pull
requests.
Part
of
me
would
be
happy
to
leave
the
poor
requests
in
the
import-export.
This
would
be
kind
of
partially.
My
job,
or
one
of
my
roles
in
this
I
think
will
be
important,
is
to
make
sure
that
we
haven't
already
started
something
else
yeah.
A
Does
anyone
have
any
strong
opinions
with
regards
to
migrating
or
pull
requests
across
I
migrated
one
across
because
it
needed
more
work
and
we
were
gonna
pick
it
up
and
I've
left
these
three,
because,
as
far
as
I
can
see
they're
relatively
far
on
in
terms
of
quality
in
terms
of
fixing
in
so
I,
don't
see
an
issue
with
I.
Don't
see
a
need
to
migrate
these
across
if
they're
already
pretty
close
to
being
approved.
A
Maybe
this
is
more
a
question
for
Yugi
to
loop
them
I,
don't
know
how
sorry
question
I
know:
I
I'm,
not
sure
whether
we
should
migrate.
These
pull
requests
across
or
just
leave
them
as
they
are
I
personally
I
think
we
should
just
leave
them
for
now.
Yes,
very
good,
because
doesn't
level
where
they
are.
Oh,
that's
true,
that's,
okay,
cool!
A
Yeah
so
feel
free.
Just
message:
either
message
mean
slack
or
send
an
email
across
I
think
everyone
has
my
email
by
the
way
and
I
can
add
you
in
and
then
finally
yeah
does
anyone
have
any
questions
or
kind
of
thoughts
at
the
moment
and
if
not,
then
I
have
one
question
but
I'll.
Just
let
you
guys
yeah
if
you
have
any
questions,
feel
free
to
raise
them
now
and
then
afterwards,
I
can
ask
you
my
question.
C
A
So
this
yet
so
the
two
projects
in
here
is
just
from
kind
of
my
point
of
view
to
work
on
making
it
a
bit
more
obvious
as
to
which
of
the
higher
priority
issues
in
which
of
the
lower
priority
issues.
If
new
issues
come
into
the
magenta
one,
so
dementia
two
main
repository
and
then
of
course,
will
migrate
them
across.
We
will
also
discuss
priority
and
with
new
issues
or
ongoing
issues
as
well
in
these
meetings.
So
if
something
comes
in
and
we
decide
yes,
this
is
I
priority.
A
Then
at
that
point
we
can
and
triage
it
and
make
sure
that
it's
in
the
appropriate
phase
so
to
say,
but
my
my
plan
is
just
to
have
these
phase.
One
is
the
high
priority
which
we
can
work
on
and
then
once
those
are
complete,
we
move
on
to
Phase
two
and
so
on
and
so
forth.
So
I
don't
know.
Does
that
answer
your
question?
Okay,.
A
A
Do
you
feel
it's
too
much
or,
for
example,
Ms
I
have
weekly
meetings
and
I
believe
in
those
meetings
they
will
demo
new
features
on
new
pool
requests,
bug
fixes
as
well.
So
we
could
do
something
similar
and
it's
just
up
to
up
to
the
team
whether
they
feel
they
needed.
Piata
Kaminsky
is
the
PIO
from
the
magenta
side.
So
we
will.
We
will
demo
stuff
with
him
and
it's
just
whether
we
need
it
every
week
or
whether
we
want
to
kind
of
I
would
suggest,
maybe
at
the
beginning
to
do
it
weekly.
A
A
A
A
So
then,
yeah
I,
think
that
covers
pretty
much
everything
and
what
I
would
love
people
to
do
is
just
to
have
a
look
over
the
issues
that
are
in
the
phase
or
form
and
and
try
and
find
something
that
they
feel
comfortable
or
maybe
a
little
bit
uncomfortable
taking,
but
are
willing
to
kind
of
take
it
in
to
work
on
it
and
feel
free.
If
you
found
something
or
you
have
any
other
questions,
yeah
come
to
me
and
just
we
can
talk
through
stuff.
A
D
A
Also,
if
you
feel
like
it,
you
can
have
a
look
through
the
other
issues
and
say
if
you
feel
that
something
is
a
higher
priority
or
should
be
higher
priority
or
then
we
can
also
discuss
that
as
well
for
the
future
meetings.
I
think
we
will
set
it
up.
We
can
discuss
issues
so
if
someone's
developing
something
if
they
have
something
they
want
to
discuss,
what's
going
to
demo
and
otherwise
we
will
use
it
to
kind
of
assign
tasks
and
reprioritize
tasks.