►
Description
Recording of the import/export weekly call from the 23rd of July 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
All
right,
so
this
is
the
import/export
weekly
meeting
I'm
joined
by
casting
this
week,
ty
as
always
that
that
he
cannot
make
it
this
week,
but
he
has
given
what
we
have.
One
update
from
his
side,
which
we
will
get
into
yeah,
so
big
update
is
that
last
week
we
had
one
two
three,
four
five
poorgrass
merged
one
anti,
which
was
to
do
with
improving
of
the
error
messages
for
super
attributes.
So
it
now
gives
you
the
information
that
you
need
to
actually
be
able
to
debug
it,
which
is
great.
A
We
then
had
two
issues
from
Causton
that
would
merge
the
first
one
is
validation,
failure
or
making
validation
fail
when
you
supply
a
required
field,
but
with
an
empty
string
and
then
the
second
one
was
setting
the
story
be
correctly
when
you
are
importing
products
for
categories
for
categories
exactly
and
then
there
were
two
little
fixes
from
my
side,
one
to
do
with
the
sample.
Customer
CSV
was
in
the
wrong
format.
A
A
But
now
those
have
been
merged
and
they
will
be
in
the
next
release
from
the
2.38
line,
which
is
good
great.
We
also
have
one
poor
request,
that's
being
put
in
from
you
custom
to
do
with
import
validation
on
duplicate
values
and
multi-select,
and
that's
going
through
the
QA
process
I
put
in
today,
yeah
so
review.
So
if
it
looks
good,
we're
just
gonna
put
that
through
QA-
and
hopefully
we'll
have
some
feedback
next
week
on
there
or
at
some
point
this
week
on
that
someone.
A
All
right,
so
the
next
big
thing
is
what
to
do
so.
What
we
I've
talked
with
Frederico,
who
has
been
helping
us
out
in
during
the
phase
one
side
of
stuff.
Unfortunately,
he
is
unable
to
continue
at
the
moment
and
which
is
a
shame,
but
I
appreciate
the
help
he
gave
us
beforehand,
and
so
we
have
two
issues
here
that
he
started
with
the
development
of
the
first
one
was
Magento,
it's
possible
to
duplicate
this
duplicate
SKUs,
sorry,
while
importing
and
the
second
one
was
Magento
modifying
the
SKUs.
A
Now
the
the
one
that
he
was
working
on
at
the
time
was
sq
uniqueness,
so
basically
the
one
he
was
doing
was
making
sure
that
Magento
doesn't
modify
the
SKUs
on
import.
The
the
reasoning
behind
this
is
so
at
the
moment
it
does,
but
the
reasoning
behind
doing
it
is
because
for
imports,
whether
that
be
CSV
or
through
the
API,
or
something
like
that,
it
is
coming
from
a
system,
and
we
do
not
want
to
manipulate
the
SKUs
there.
A
B
B
A
B
A
A
Yeah
and
then
we
have
the
obscurity
and
use
error
message.
The
problem
that
we
were
having
here
is
everything
where
it's
fine,
apart
from
the
case
when
you
duplicate
the
product,
don't
know
so,
if
you
already
have
a
product
and
then
you
click
the
duplicate
button,
it
just
fails
in
the
background
and
I.
Don't
think
it
actually
shows
you.
The
error
message.
B
A
A
A
Know
how
that
works?
Maybe
that's
a
that's
a
good
place
to
start
from
your
if
you
want
to
I
know
from
we
have
this
copier
class,
so
what
you
might
be
able
to
do
is
during
the
copier
class.
It
does
the
clearing
does
whatever
at
that
point,
but
yeah.
That's
a
good
idea
check
check
how
that
might
be
the
first
step.
If
you
want
to
work
on
this
one
know.
B
A
Check
how
it
does
it
in
magenta
one
and
then
then
update
it
to
to
work
appropriately
either
clearing
it.
So
when
you
click
Save,
it
says
please
I
have
asked
you
that
would
be
OK
for
me
or
making
it
so
that
you
cannot
add,
ask
you
that
already
exists
I'm,
just
making
sure.
As
long
to
be
honest
as
long
as
there
is
the
error
message,
there
saying
you've
tried
to
duplicate,
but
the
product
still
has
a
SKU
and
then
allowing
the
user
to
change
that
SKU.
B
A
A
B
A
A
B
A
Leave
this
one
on
a
side
and
anyone
else
that
comes
in
and
and
ask
for
something
to
do.
We
can
point
him
in
this
direction,
but
I
think
in
fact,
I
could
I
might
pass
this
one
on
to
our
QA
team
to
see
if
we
can
get
them
to
reevaluate
this
and
because
this
I
think
then
you
might
have
fixed
this
with
the
other
one.
But
I
will
double
check.
A
All
right
other
than
that
I
will
update
slack
with
the
update
from
this
meeting
and
I
will
also
you're
already
assigned
on
your
task
and
I'm
gonna
go
through
and
update
the
issues
to
make
sure
that
we
are
up-to-date
because
I
think
after
merge
issues
haven't
been
closed
and
I
can't
figure
out.
Why
not
so
I
need
to
look
into
our
tool
in
from
that
side,
because
we
had
67
before
and
we've
closed
five,
and
we
still
have.
B
A
That's
all
that's
all
good,
alright
and
then
I
think
that's
enough
for
enough
for
now.
So
let
me
know
yet
reach
out.
If
you
have
any
issues
or
if
you
want
some
more
information,
feel
free
to
reach
out
to
me,
or
you
could
also
reach
out
to
Federico,
see
how
far
he
got
and
as
far
as
I
understand
the
code
is
because
I
did
some
of
the
testing
myself.