►
From YouTube: Import/Export weekly call 2nd of February 2018
Description
Recording of the import/export weekly call from the 2nd of February 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
Awesome.
Okay,
so
this
is
the
import/export
improvements.
Weekly
meeting
is
the
2nd
of
February,
and
we've
got
quite
a
bit
of
updates
this
week.
So
so
that
is
going
to
be
good,
I
think
so
I
will
start,
and
then
we
can
pass
on
to
anyone
else.
That
has
any
any
updates.
The
first
from
me
is
the
memory
allocation
problem
with
the
customer
import
and
that
has
been
merged,
so
that
is
done
and
in
2.3
develop
so
yeah,
that's
cool,
I'm,
happy
with
that
one.
A
That
was
an
interesting
problem.
Basically,
the
way
that
Magento
had
set
it
up
was
it
was
creating
an
object
for
each
row
in
the
database.
So
when
you
had
too
many
rows,
oh
I
think
it
was
25
thousand
rows
or
something.
Then
you
started
getting
into
memory
issues
and
so
I
updated
it
to
the
same
way
that
the
product
import
deals
with
it.
So
it
will
deal
with
just
the
data
it
needs,
rather
than
the
full
objects,
which
was
the
problem
we
had
before.
A
So
it
looks
like
just
the
customer.
Import
doesn't
have
as
much
love
as
some
other
parts
in
the
system.
Okay,
so
that's
yeah,
that's
done
that's
merged
I
think
it
should
have
already
synced
across
to
the
import/export
fork,
but
doesn't
matter
if
it
hasn't
just
yet
the
next
update,
since
he
is
not
in
the.
A
Is
this
one
to
do
with
the
filtering
using
multi
select
options
when
filtering
on
export?
We
have
a
fix
in
place,
it's
passed
code
review
and
is
currently
with
the
team
for
QA.
So
hopefully
that
will
be
and
will
pass
the
I
will
guess
it'll
be
early
next
week.
If
it
does,
because
we
have,
we
have
a
bit
of
a
backlog
on
some
testing
stuff
today,
at
least
so,
hopefully
a
next
week,
we
can
get
that
one
merged
as
well,
which
would
be
great.
A
The
final
update
from
my
point
of
view
is
I
had
a
call
earlier
with
with
room
R
for
this,
the
filenames
one
he
was
having
a
few
issues
with
his
integration
test
setup.
Unfortunately,
we
weren't
able
to
solve
that.
The
only
thing
left
is
the
he's
fix
the
code,
but
the
tests
are
failing,
and
so,
if
anyone,
if
anyone
knows
how
to
get
the
integration
test
running
on
maps
or
on
a
Mac
setup,
then
he
might
benefit
from
some
help.
A
Unfortunately,
I'm
running
Linux,
well
Linux
inside
of
Windows
machine,
so
I
wasn't
able
to
help
them
with
the
map
specific
stuff.
But
what
I've
agreed
is
I
will
take
over
in
fact,
I'll
do
it
just
now,
I
will
take
over
the
to
fix
the
test
here,
because
the
only
thing
that's
left
is
is
the
test.
So
I'll
just
make
a
note
here.
A
Updates
yeah
and
then
hopefully
again,
this
will
be.
We
can
move
this
on
to
QA
after
the
code
review,
that
is,
the
o
frederico
is
unfortunately
unavailable.
Today
he
had
a
customer
and
call
it
he
couldn't
get
out
of,
and
he
will
send
through
an
update
some
point
later
today,
probably
to
the
slack
Channel
with
how
far
he's
got
with
this
one
and
if
he
needs
any
help
with
this
at
all
and
I.
B
C
A
B
A
A
B
B
A
E
B
I've
changed
the
code,
so
you
can
use
multiple
values
of
the
empty
attribute.
So
if
you
try
to
import,
you
can
use
this
value
to
set
the
empty
value
to
Nu.
Ll
know
you
can.
If
you
want
to
use
the
zero
value,
it
still
works.
So
if
you
want
to
set
a
weight
to
one
or
zero,
it
will
work.
If
you
want
to
set
the
quantity
to
one
or
zero,
it
will
also
work.
But
if
you
want
to
set
the
quantity
empty
with
no
value
you
can
use
this
constant
I
have
edited
everything.
B
What
created
the
empty
attribute
value
constant
and
this
code
I'm
going
to
check
if
the
constant
has
been
used
so
I
can
set
the
attribute
to
empty
I'm
changing
the
validated,
because
when
you
are
trying
to
import
check
data,
if
you
are
using
the
check
data,
you
have
also
need
to
check
if
the
validator
is
working.
I
have
edited
the
quantity
validator
because
of
you
can
use
the
empty
value
to
set
attribute
empty
or
you
can't
use
the
default.
B
One
I've
changed
weight
at
the
beautiful
you
I
created
unit
test
editor
to
unit
test
of
quantity.
So
if
we
use
the
import
default
constant,
this
is
true.
If
you
use
another
one,
it's
false
I
have
created
a
new
unit
test
for
the
weight,
so
we
are
checking
the
weight.
Also
it's
based
on
the
quantity
unit
test,
but
it
will
only.
It
will
also
check
if
what's
the
value,
if
it's
true
or
false,
the
big
difference
between
quantity
and
way
this
quantity
can
be
negative.
Weight
can
not
be
negative.
I
just
thought.
B
You
know
this
is
a
big
change.
They
changed
not
on
the
code,
but
in
unit
tests,
I've
credited
product
tests,
so
we
are
using
the
setters
and
getters
are
working
I
modified
for
for
adding
this
new
field,
fuel
is
using
the
constant,
so
the
default
value
of
the
is
using
the
constant,
create
it.
A
constant
the
field
value
then
empty,
attribute
constant.
So
this
is
now
working.
B
If
you
want
to
set
importing
products
with
empty
attributes
or
erasing
the
attributes,
you
can
use
the
empty
value
of
constants,
so
I
created
pull
request
to
the
P
to
the
Magento
to
rip
repository.
So
now
we
are
waiting
for
for
the
core
team
or
David
to
to
validate
and
check,
and
if
okay,
it
will
be
added
to
2.3,
and
we
need
to
create
backward
to
to
2.2
and
2.1
I.
Do
yes.
A
One
question
I
have
at
the
moment
is
I
think
as
part
of
enterprise.
There
is
the
scheduled
inputs,
yes,
so
you're,
probably
if
you
should
have
access
to
the
enterprise
repository,
if
you
will
probably
will
probably
need
to
do
something
there,
as
well
with
regards
to
adding
that
field.
When
you
set
up
a
schedule
in
food
as
well
I'm
having
we
don't
have
enterprise
at
this
moment,.
A
B
A
Is
it
difficult
to
explain
yeah
yeah
so
either
either
we
add
as
something
I
don't
know
in
dev,
Docs
or
we'll
need
to
figure
out.
What's
the
best
way
or
maybe
description
below
here,
oh
yeah
yeah,
that
might
be
a
good
option.
Yeah
yeah
I
think
that
could
be
a
great
option
actually
adding
in
the
description.
Also.
B
When
you
download
the
sample
file,
that
could
also
be
a
very
good
idea
to
have
something
here.
It
with
default:
okay,
mm-hmm
yeah,
to
make
it
so
much
as
possible,
complete
mm-hmm
there.
We
need
to
talk
about
yeah
with
with
people
of
the
Deaf
Doc's.
How
we
have
issue
together
or
first
think
we
have
to
wait
about.
The
quality
team
is
everything
okay
can
emerge,
and
then
we
called
with
the
deaf
dogs
yeah.
A
So
I
would
recommend
going
and
adding
the
description
in
any
way:
okay
and
maybe
also
adding
into
the
sample
file.
If
you
can
okay,
no
problem
and
then
yeah
once
once,
the
whole
thing
is
is
kind
of
ready
to
merge
them.
We
can
go
on
about
what's
the
best
documentation
approach
as
well.
Yes,
very
good.
B
Cool
very
good,
the
only
thing
I
didn't
create
was
the
integration
tests,
because
truly
I
never
done
that
before
Oh
mom,
so
I
need
to
have
some
more
explanation.
How
about
to
run
them
running
the
the
unit?
Testing
is
okay,
I
have
changed
that
and
you
test
that
in
a
PHP
unit.
So
that's
no
problem
with
the
integration
tests.
I
need
to
find
out
how
to
do
that.
Okay,.
A
A
And
well,
there
is
that
there
is
a
pin.
Magento
command,
yes
allows
you
to
run
them,
but
there
is
also
a
way
of
setting
it
up.
So
you
run
individual
individual
tests,
so
it's
probably
probably
a
better
option
and
I'll
send
through
that
to
the
slack
group.
I
guess
this
should
be
under
dev
I
think
it
is
that's
okay
tests
run
and
then
you
can
specify
whether
you
want
to
run
integration
or
unit.
E
E
Sorry
I
couldn't
I
had
the
problem,
so
I
would
have
something
one
second,
that
I
get
there.
So,
regarding
my
issue,
it's
so
first
of
all,
I
realized
that
our
multiple
issues
under
one
and,
for
example,
the
first
issue
as
I,
could
confirm
and
fall
now.
It's
only.
He
is
the
part
of
when
the
visibility
would
give
incorrect
values,
for
example,
and
where
this
was
one
second,
that
I
share.
E
E
E
E
So
just
taken
away
this
function,
it's
not
the
issue
here
and
another
function
that
now
I
don't
be
called
but
I.
So
essentially
my
question
is
and
both
had
in
the
comment
that
was
supposed
to
have
lower
case.
It
was
and
I,
don't
know
what
the
reason
of
this
is
doesn't
really
make
sense,
but
it
wasn't
done
in
one
case
and
it
was
done
in
another
case.
My
suggestion
would
be
just
to
not
lower
case,
because
I
don't
see
the
reason
of
that.
E
A
A
E
A
E
B
E
So
in
possible
options:
it
is
it
that
method
that
I
show
you
before.
It's
actually.
What
happens?
It's
not
that
it's
a
place
on
store,
ID
values,
because
it's
actually
just
hard-coded
the
string
and
that
gets
run
late.
Translated
automatically
it's
in
your
locality,
but
it's
impossible
for
the
program
to
know
what
was
below
College
of
origin
and
bo2
to
make.
E
D
E
C
E
B
E
B
E
B
B
This,
if
you
have
a
new
attribute
scholar
and
you
have
the
product
with
attribute
value,
Reds
and
attribute
value
blue.
If
those
attribute
options
are
not
created
in
the
before
by
hands
in
the
admin
area,
it
will
not
work
to
import
them.
It
will
not.
The
current
import
will
not
create
mute
option
rate
and
attribute
option
blue,
so.
B
I
think
the
best
option
will
be
to
use
the
admin
value.
Will
it
be
the
best?
No
because
of
if
you
want
to
use
an
other
system
to
export
or
import
your
data
in
it
can
be
difficult
because
you
have
to
translate
everything
you
understand,
so
maybe
there
should
be
a
possibility
when
you
export
data
from
a
gentle
that
we
ask
in
which
language
you
want
to
export
the
data.
E
E
A
E
E
A
Yeah,
okay
sounds
great
Perry:
do
it
fabulous
yeah?
Okay,
that's
good
good,
update,
I,
think
from
everyone
yeah
does
anyone
else
have
anything
to
talk
about,
otherwise,
I
think
we've
all
got
enough
to
to
get
on
with
for
this
week.
I!
Guess
again!
If
you,
if
you
feel
that
you've,
you
want
something
different
to
do.
There
are
some
poor
requests
to
have
a
look
at
if
you
want
to
otherwise
yeah
just
drop
a
message,
and
the
slack
and
we'll
be
able
to
find
stuff
for
people
to
do
and
just
a
quick
update.