►
From YouTube: Import/Export Weekly call 19th Jan 2018
Description
Recording of the import/export weekly call from the 19th 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
Good
class,
wonderful,
alright,
so
this
is
whatever
it
is
week.
Three
I
guess:
yeah
week,
three
import-export
improvements
week:
three
I'll
give
you
a
quick
overview
of
the
kind
of
the
obvious
work
this
week
and
then
we'll
hand
over
to
people
who
want
to
share
something
about
some
of
the
work
that
they've
been
doing
so
we've
had
nothing
else
closed
this
week,
and
but
we
have
had
to
Newport
quests
one
from
myself
to
do
with
fixing
a
memory
error
in
the
customer.
A
A
Yeah
fixing
memory
issues
in
customer
import.
It
also
I
found
the
same
problem
with
customer
options,
I
believe
em.
So
if
we
think
this
is
the
way
to
go
that,
we
might
find
that
we
can
also
get
a
memory
or
performance
improvement
with
customer
options
and
one
other
part
of
the
product
import.
By
doing
the
same
thing,
basically,
Magento
was
working
with
an
iterator,
and
this
iterator
was
creating
a
full
customer
object
for
each
customer
or
each
results
when
all
it
needed
was
the
ID
and
the
email.
A
Yeah
so
as
I
was
saying,
this
pull
request
is
available,
feel
free
to
have
a
look
at
it.
If
you
don't
understand,
just
ask
me
a
question
and
I
will
do
my
best
to
answer
it
and,
like
I,
said
I'm
happy
to
see
how
this
progresses
and
I
more
than
happily
get
people's
feedback
as
to
whether
they
think
this
is
a
good
idea
or
what
the
second
issue
was
unable
to
use
the
filter
data
for
multi-select
on
export
mas.
This
guy's
name
is
Marcel,
I.
Think
I
think
that's
how
you
pronounce
me.
A
He
works
ECG
at
Magento,
but
wants
to
get
involved
with
the
community
side
as
well,
and
so
he's
provided
us
with
this
pull
request,
which
basically
fixes
some
problems
there
were
with
multi,
selects
again
open
for
like
open
for
a
pool
request.
So
if
you
feel
like
I
want
to
do
a
review
as
well
as
some
coding,
then
please
feel
free
to
jump
on
any
of
the
pull
requests
that
are
open
great
with
that
in
mind.
I
would
then
hand
over
to
Frederico
and
he
can
give
us
an
update
on
on
your
ticket.
Okay,.
B
Sure,
okay,
so
I'm
still
have
pending
to
update
the
ticket
description.
Sorry
about
that
I
will
try
to
that
today
because
they
did.
The
current
description
doesn't
properly
reflects
what's
happening
now,
so,
okay,
so
from
our
previous
discussion,
we
said
that
we
should
have
the
same
behavior
from
the
import
process
and
the
admin
panel.
B
What
is
the
the
part
that
is
adding
the
/
1/2
that
that's
/,
some
sequence
number
is
the
SKU
back-end
object,
the
one
that
handles
you
know
the
behavior
of
the
attribute.
So
what
happened
is
whenever
you
go
to
save
a
product?
There
is
an
event
triggered
the
before
save
that
will
end
up
here
in
this
SKU
class
under
before
save
of
the
SKU
working
class
will
call
this
generate
unique
SKU,
which
will
look
for
current
rescues
in
the
system.
B
I
will
append
this
slash
and
sequence
that
is
not
used
in
the
in
the
system,
so
my
idea
was
to
change
the
validation
method
for
for
this
back
in
class.
So
I
added
this
piece
of
code
here
which
checks,
if
or
if
already
exists
and
SKU
in
the
database
that
we
are
trying
to
save
it
will
send
an
exception
with
a
message
saying:
SKU
is
already
news.
We
of
course,
can't
discuss
what's
the
proper
message
so
by
changing
this,
this
call
in
the
before
save
is
not
needed
anymore.
So
I
guess
with.
B
B
This
validation
already
takes
care
of
not
having
into
account
the
SKU
of
the
entity
that
you
are
trying
to
elite.
So
this
valuation,
we
know,
will
not
break
the
ability
to
edit
the
product
and
then
the
next
step
is
what
happens
with
the
leading
and
trailing
spaces.
There
is
a
comment
here
from
Peter
who
says
his
opinion.
A
living
or
a
trailing
space
should
be
acceptable.
B
I
agree
with
the
opinion
because-
and
the
argument
is
maybe
the
customer
doesn't
have
the
ability
to
control
the
SK
use
in
systems
where
you
connect
machine
to
do
an
ERP.
The
customer
is
not
always
in
control
of
how
they
the
SKU
is
built.
So,
let's
say
in
some
case,
I
don't
know
for
what
reason,
but
maybe
you
have
there
is
the
possibility
that
you
can
have
an
SK.
You
will
be
needing
or
a
trading
space.
So
in
my
opinion
we
should
accept
those
as
valid
sk
use.
B
So,
in
that
regard,
the
import
process
already
allows
you
to
create
probes
with
leading
and
trailing
spaces
no
matter.
For
example,
if
you
have
like
this
issue
37,
if
you
provide
a
CSV
with
the
trailing
space
with
the
same
skill,
but
with
the
training
space,
the
import
process
will
create
a
new
product.
And
if
you
all
agree
with
with
the
argument
of
allowing
Trading
Spaces,
then
that
would
be
the
correct
behavior.
C
I
say
something
about
this,
so
I
agree
with
you
that
the
client
doesn't
have
a
control
of
this
sq,
so
it
my
me
needed
for
spaces,
but
at
the
same
time,
if,
if
it's
done
manually
or
someone
put
the
spaces
incorrectly,
which
for
me
I
saw
it
happen
like
way
too
much
too
many
times,
it
will
create
a
new
product
and
maybe
create
unexpected
result
and
the
space
you
don't
see
it.
So
it's
really
difficult
to
debug
this
kind
of
situation,
yeah.
B
B
B
This
is
for
the
AIB
model
entity,
abstract
entities
when
there
is
one
magenta
dress
to
do
the
comparison
in
the
database,
trying
to
get
trying
to
figure
out
if
the
value
that
you're
passing
its
unique
or
not.
There's
this
stream
function,
which
makes
the
admin
not
allowing
you
to
send
an
issue
37
with
spaces,
for
example.
So
that
is
something
that
we
will
need
to
work
on.
If
we
go
for
that,
but
so
I.
C
B
Okay,
so
I
will
stop
sharing
that's
where
I
got
so.
We
have
I,
think
the
discussion
of
allowing
or
not
leaving
on
trailing
spaces,
and
then
I
need
to
give
more
testing
to
the
import
process
on
how
what
happens.
For
example,
when
you
have
in
the
same
CSB
a
repeated
SKU,
not
sure
what
what
what's
the
behavior
right
now
currently.
A
B
Cool
okay,
so
yeah
I,
guess
well
that
that's
if
that's
intended
behavior
then
should
be
because
the
import
process
is
allowing
you
at
this
moment
to
to
to
either
ski
use
with
linear
and
trading
expenses.
So
I
guess
the
next
step
would
be
to
get
to
a
conclusion
of
what
do
the
woodland
and
throwing
a
spaces
and
make
the
admin
and
the
import
process
to
have
the
same
behavior.
In
regards
of
that
cool.
C
A
He
is
the
like
he's
the
product
owner
for
this
project,
so
I
think
if
there
is
anything
with
regards
to
yeah
like
changing
features
that
currently
exists
or
processes
that
currently
exist,
I
would
just
double
check
with
him
and
say
this
is
what
it's
like
now.
This
is
what
we
would
suggest
changing.
Is
this
okay
either
either
you
can
contact
him
or
you
can
send
me.
The
information
and
I
can
check
with
him
as
well.
A
I'm,
okay
with
that,
but
I
think
yeah
I
think
keeping
it
so
personally,
I
would
say
keeping
the
admin,
so
it
will
do
the
trim,
because
that
will
kind
of
help
with
a
bit
of
with
a
bit
of
human
error,
so
to
say,
whereas
with
the
import,
the
chances
are
that
CSV
will
be
generated
by
something
already.
So
we
should
trust
it.
It
feels
a
little
odd
having
having
it
do.
One
thing
in
one
case
and
one
thing
in
another
case
but
I-
think
that's:
okay,
yeah
I'm,
open
to
suggestions.
C
B
A
C
A
So
then
yeah!
So
then,
if
we
try
and
make
the
the
two
processes
consistent
as
possible,
then
I
think
we're
we're
going
down
the
right
route
here
there
and
but
yeah
just
put
together
our
plan
so
to
say
or
what
your
recommendations
would
be
and
then
you
can
send
them
to
piada.
You
can
include
me
as
well.
If
you
would
like-
or
you
know
you
can
include
the
whole
group
if
you
would
like
I,
don't
really
don't
mind
how
you
do
it,
but
yeah
just
check
with
him
with
regards
to
that
sort
of
change.
A
C
A
C
One
second
I
should
show
so
mine.
It
was
a
problem
with,
for
example,
with
obesity
issue
importing,
because
it's
translated
based
on
the
admin,
local
language,
but
it
doesn't
work
for
by
import
if
it's
in
a
different
language,
I
didn't
investigate
enough,
so
I
want
to
dedicate
a
bit
more
time,
but
the
first
thing
that
only
thing
I
looked
at
is
how
much
Enzo
treats
this
kind
of
situation
for
other
similar
attributes
and
one
that
I
was
thinking
is
the
product
type.
C
C
It
has
just
simple
or
configurable
or
downloadable,
and
it's
not
translated
and
that
way
works.
So
my
suggestion
is
other.
We
follow
this
example
and
use
a
string
like
it's
always
the
same.
I
ever
use
an
integer
value
that
will
decline.
How
to
map
it
or
I
can
try
to
investigate
more
to
understand
how
to
deal
with
the
translation,
I.
C
Know
your
suggestion
was
to
find
a
way
for
the
translation,
because
you
said
you
want
the
user
to
be
able
to
use
the
import
without
a
manual
essentially.
But
if
you
look
at
our
like
even
the
Associated
SKUs
or
the
computable
in
baton,
it's
already
you
have
to
understand
how
it
works
and
put
things
that
are
not
humanly
intuitive
to
work
with
so
I
think.
If
they
do
for
work
for
goes
out
to
boot,
we
could
expect
they
do
the
same
for
visibility.
A
C
Quite
specific
case,
because
it
creates
models
based
on
what's
that
value
and
if
it's
treated
class,
if
you
put
simple,
he
would
create
the
simple
model
of
the
attachment
and
from
that
on,
he
will
use
certain
methods
and
so
on.
So
it's
like
that.
It
would
be
really
difficult,
I
think
to
change
at
least
for
my
comprehension.
B
D
A
D
A
What
I
would
recommend
doing
is
getting
it
working
yeah
get
it
work
with
the
default
just
now,
maybe
after
it's
working
with
the
default,
we
can
show
it
to
piata
shown
the
like
pre-order
Kaminsky,
show
on
the
good
side
and
the
bad
side
of
it
honest
and
say:
okay,
how
does
this
fit
with?
Magento
is
vision
behind
it.
If
that
makes
sense,
are.
A
D
D
D
D
D
A
C
A
C
A
D
A
D
E
E
Let
me
show
you,
okay,
so
let's
say
we
have
to
import
certain
products
which
are
in
different
folders
and
the
products
images
name
have
the
same
name
like
in
folder
a
it
has
a
door
JPD
and
envy
it's
also
having
a
door
technique
while
importing
these
individuals
I
fix
the
issue,
but
I
recommended
something
to
David.
Yesterday,
I
want
to
talk
to
you
also
about
that.
E
My
recommendation
was
dead
shouldn't.
We
think
that
if
the
images
are
imported
from
certain
folders
from
some
other
directory
like
ABC
and
the
images
names
are
a
B
or
C
something
else
shouldn't
they
come
into
middle
toe
with
the
same
path
as
they
were
before
like
in
this
case.
We
have
folded
B
and
it
is
a
dot
jpg
and
when
I
hold
these,
these
becomes
like
this.
C
This
would
be
a
really
big
change
if
you,
if
we,
if
we
decide
to
do
this,
it
would
have
a
big
impact.
A
lot
of
importers
like
they
know
the
default
Magento
behavior
and
they
are
built
with
that
ecologist
and
I
can
say
from
my
own
experience,
I
didn't
several
that
I
have
to
take
account
of
that
Magento
deals
with
naming
in
that
way.
E
So
can
we
do
this
while
importing
the
bulk
products
like
we
are
importing
thousand
products
and
in
middle
toe
if
a
person
has
store
in
somewhere
else
and
he
prepared
a
CSV
with
with
his
product
images,
and
he
had
he
had
to
see
the
previous
images
in
neo
bin
into
a
system.
So
it
will
be
easy
for
him
to
traverse
through
the
same
hierarchy
as
he
was
using
before
it
will
not
impact
other
import.
Behavior,
but
I
know
it's
odd,
as
this
was
not
previously
being
used
in
default
agenda.
Behavior.
E
A
E
My
plan
I
planned
that,
let's
say,
is
like
folder
a
and
then
folder
ye
and
then
in
okay.
So
then
it
will
be
spotted
to
middle
tone.
If
we
talk
about
the
current
case,
it
will
be
a
or
a
underscore
one
or
a
underscore
two
okay.
So
if
we
do
something
like
we
embed
the
folder
names
with
images
name
like
a
B
and
a
then
it
will
be
important
to
middle
toe
in
the
same
hierarchy
like
folder,
a
folder,
B
and
then
a
according
to
the
you
can
say,
splitting
mechanism
of
magento.
A
Okay,
what
I
think
I
would
like
to
do
is
I'd
like
to
see
what
happens
in
each
case,
so
when
you're
importing
one
product
one
product
with
both
Bo
images,
multiple
products
and
multiple
products
and
multiple
images,
as
long
as
they're
all
consistently
behaving
in
the
same
way,
I
think
that's!
Okay,
my
concern
is
if,
when
you're
importing
multiple
products,
you
get
a
different
behavior
from
single
products,
then
I
think
we
have
a
problem,
but
if,
if
each
type
of
import
works
in
the
same
way,
then
I'm?
A
E
A
E
E
D
A
A
A
Otherwise
we
will
process
them
next
week
would
be
the
plan,
okay,
very
good,
very
good,
cool,
all
right
in
front
and
then
I
like
I,
said
I'll
get
back
to
you,
Uma
about
the
testing
and
Peter
I'll,
try
and
push
for
their
meeting,
otherwise
yeah
reach
out.
If
you
need
anything
and
yeah.
Thank
you
very
much.
No.