►
From YouTube: Import/Export weekly call 16th February 2018
Description
Recording of the import/export weekly call from the 16th 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
A
Projects
are
now
going
to
be
using
Zen
hub
for
an
overview
for
the
board
for
the
reporting
and
that
sort
of
stuff,
and
so
here
I've
set
up
copied
over
all
the
estimates
we
had
previously
and
it's
very
similar
to
the
github
project
site
and
excuse
me,
but
it
allows
us
to
to
do
a
bit
more
of
a
detail
reporting
which
is
useful
for
the
planning
side,
which
was
missing
with
the
github
projects.
As
far
as
I
could
see.
A
Yeah
another
thing
of
interest:
I
guess
for
everyone
is
we
are
looking
to
kind
of
expand
or
get
a
bit
more
help
from
the
community
side.
So
at
the
moment
we've
got
a
lot
of
people
contributing
with
us
code.
We
have
a
lot
of
stuff
in
QA
and
also
stuff
that
I'm
helping
people
out
with,
but
what
we
would
like
to
do
is
get
more
people
involved
with
the
review
Pro
and
the
review
processes
as
well.
A
A
A
Hopefully
that
means
that
next
week
we'll
be
able
to
move
this
into
the
QA
phase,
as
it's
currently
in
the
review
phase,
yeah
trying
to
think
what
else
we
have
this
task
from
Adam
he's
provided
as
code
view.
But
again
lots
of
the
tests
are
failing,
I've
reached
out
to
him,
and
he
says
he
will
get
on
to
that
at
some
point:
I'm,
so
I'm,
okay,
not
pushing
that
myself
at
the
moment,
Peter
is
still
on
holiday,
I
believe
until
next
week
he's
got
the
empty
row
tasks
again.
A
B
A
B
The
first
one
which
is
raised
by
the
issue
that
was
created
is
that
the
import
process
allows
you
to
create
products
with
trailing
and
living
spaces,
but
since
the
admin
panel
doesn't
allow
that
it
kind
of
give
you
some
trouble,
because
Magento
will
get
confused
by
the
SK
use
with
spaces
when
trying
to
save
from
the
admin
panel.
That's
like
be
the
first
issue
raised
by
by
that
github
issue,
but
that
brings
two
other
things.
B
What
happens
is
when
you
try
to
create
a
product
with
already
existing
SKU
magenta
will
append
and
sequence
number
after
replacing
the
original
see
you
so
with
maintain
uniqueness
of
the
SKU
in
the
system,
there
have
been
some
discussion
around
this.
We
agreed
that,
for
us
is
not
the
best
way
to
handle.
B
B
B
That's
that,
in
my
opinion,
is
the
first
decision
to
make.
Then,
if
that
is
a
yes,
if
they
should
have
the
same
behavior,
then
the
next
thing
to
define
will
be
what's
the
correct,
SKU
management
process,
should
we
allow
leading
on
trailing
spaces?
Should
we
for
with
them?
And
given
that
decision
we
need
to
change
here.
The
import
process,
or
the
mean
final
process
to
that
that
rule
on
the
sku
man
and
then
the
other
thing
which
is
kind
of
separated.
B
So
so
it
could
be
worked
without
relation
to
the
all.
This
is
changing
the
behavior,
this
behavior
of
a
machine
to
changing
the
SKU
when
they're,
when
you're,
trying
to
say
and
SKU
that
is
already
present
in
the
database.
That
could
be
worked
as
a
separate
thing.
I
think
if
we
all
agree
that
that's
an
issue
that
needs
to
be
solved
so
that
that's
kind
of
a
summary
of
yeah.
A
Cool
I
appreciate
that
I
wish
more
people
would
be
in
this
call.
So
we
can
discuss
this
with
a
bigger
group,
but
since
no
one's
here
we'll
just
make
a
decision
amongst
ourselves
because
I
don't
want
it
to
drag
on
anymore
I,
think
it
would
be
good
just
just
to
get
it
working,
and
so
let's
go
first
on
to
the
first
question:
whether
or
not
the
processes
should
be
the
same.
A
A
C
Don't
you
think
guys
that
spaces
are
like
tricky
in
SKUs
I
mean
they're
a
little
confusing
they
they
can.
They
can
cause
those
those
issues
like
in
both
theorem
when
you
import
this
from
from
a
CSV
or
if
we
create
it,
it's
important
when
we
support
customers
in
you
know
managing
their
stores,
it's
it's
important
for
them
to
understand
the
flow,
and
it
would
be
easier
for
the
customers
from
our
observations.
C
A
Yeah,
so
we
have
some
feedback
from
people
with
regards
to
not
manipulating
SKUs
that
come
from
a
CSV
or
or
the
ERP
system
which
which
I
agree
with,
and
it's
just
the
question
of
whether
if
we're
not
gonna
manipulate
it,
so
a
space
is
a
fully
valid
character.
So
we're
not
going
to
manipulate
it
from
the
ERP
system.
Then
we
shouldn't,
then
we
shouldn't
also
manipulate
it
from
an
admins
yeah.
In
that
case,
that's
correct
right.
A
So,
but
then,
because
it's
a
valid
space
is
a
valid
character.
Then
then
we
just
have
to
say:
okay,
it's
a
completely
valid
skew
in
that
case,
and
if
someone
adds
that's
Cuban,
that's
completely
up
to
them
and
we
can.
We
can't
babysit
admin
users
anyway.
That's
true,
that's
true,
so
my
feeling
here
would
be
they're
valid
characters.
Let's
make
the
system's
as
flexible,
yeah
I
would
make
the
two
systems
as
similar
as
we
can
make
them
at
least
in
the
process.
So
then
it
just
becomes
a
case
of.
A
B
B
B
A
C
My
voice
matters
I,
would
agree
with
you.
I
didn't
hear
this.
This
comment
about
like
flexibility
and
letting
the
data
be
not
modified
when
you
import
them
from
from
the
earpiece.
This
is.
These
are
like
less
issue
II
that
the
ER
connections,
issues
that
so
yeah
if
yeah
yeah
I
just
agree.
Basically,
okay,
that's
right.
A
A
A
A
A
A
B
Got
a
feeling
which
is
I,
don't
like
my
data
to
be
modified
a
doc.
You
know
yep
I
me
as
a
user
as
a
much
into
user.
I
would
like
to
be
informed
that
I
am
using
SK.
You
guys
already
used
rather
than
machine
to
change.
My
scale
use
yeah,
but
I'm,
not
sure.
If
that's
okay,
that's
only
my
position,
I'm,
not
sure
if
that's
the
right
call
or
not
well,.
A
This
goes,
I
would
ever
say,
I
agree
with
that
in
the
sense
of
if
we
make
that
decision-
and
we
say
that
on
the
import,
we're
not
going
to
manipulate
data,
but
then
in
the
admin
section
this
is
a
form
of
manipulation.
So,
if
you
would
do
this
on
the
import
you,
if
you
had
the
right
setting,
it
would
update
the
product
correct,
but
it's
if
you,
for
example,
had
if
you
had
two
products
with
the
same,
if
you
in
the
CSV,
you
had
two
products
with
the
same
SKU
you
at
that
point.
A
Yes,
so
in
this
case,
I
am
okay
with
it
saying
that
we
would
for
now
at
least
we
say
that
problem
3
is
an
issue.
I
would
say
that
we
need.
Probably
in
this
case
we
need
to
talk
with
one
of
the
product
owners
with
regards
to
it's
just
a
double
check.
So
what
I
would
ask
Frederico
for
now
is
if
you
can
update
the
ticket
with
this
information.
A
Firstly,
I
would
recommend
putting
this
whole
email
on
the
ticket
just
just
to
give
the
visibility.
Okay
and
then
answer
the
next
steps,
essentially
for
yourself
and,
if
possible,
could
you
also
create
a
new
issue
with
regards
to
problem
3
and
assign
that
to
piada
and
ask
and
then
we'll
get
his
feedback
on
that
as
well?
Okay,
yeah.
A
A
B
A
A
If
you
have
time
when
it'll
be
yeah,
finally,
if
you
have
time
to
be
great
to
update
that
ticket
pretty
much
as
soon
as
the
the
call
finishes
just
so
we
don't
lose
the
information
anyway
and
just
so
it's
friendship
that
makes
sense
yeah
once
the
tickets
updated.
Could
you
also
post
this
in
the
slack
as
well?
Just
so
we
know
exactly
what
we
decided
just
so
everyone
who
wasn't
in
those
wants
decided
that
would
be
fabulous
cool.
A
A
C
C
I
felt,
honestly
speaking,
we
haven't
tried
that,
because
we've
agreed
with
our
customer
that
you
know
doing
this
for
800
products
is
like
not
an
option
for
them.
So
my
my
question
is:
is
there
like
any
chance
to
move
this
ticket
to
be
to
be
worked
on
like
sooner
than
in
phase
2,
because
it
will
take
another
I'm
afraid
a
longer
time
before
it's
done?
C
A
C
It's
mentioned
that
he
investigated
the
case
for
a
few
hours.
Maybe
I
think
I
have
in
my
mind
he
he
wrote
something
like
that.
So
maybe
he's
got
some
I,
don't
know
more
data
in
case
we
had
to,
like
you
know,
fix
this
internally,
which
I'd
like
to
avoid,
but
I'm
looking
for
chances
right
now.
The
customers,
basically
look
by
you,
know,
saying
ability
to
upload
and
manage
the
date
on
their
on
their
stage
server
for
now
and
they
come
to
life,
you
know
without
it,
so
we're
kind
of
stuck
yeah.
A
Okay,
so
basically,
this
is
the.
What
we
have
previously
agreed
on
working
through
I
would
suggest
that
so,
firstly,
yeah
there's
possible
to
switch
around
priorities
if
need
be,
and
so
what
I
would
suggest
is
the
stuff
that's
already
in
review
or
progress.
We
leave
as
it
is
mm-hmm,
and
so
if
we
were
to
switch
something
out,
it
would
be
one.
C
This
is
something
you
can
well
in
worst
case
scenario:
you
can
run
a
database
query
and
you
can
have
the
products
done
properly
and
the
other
thing
is
that
I
think
in
at
least
newer
magenta
versions.
It's
not
not
an
issue
anymore,
but
I'm.
Not
a
person
of
sure
of
that
question
is
how
many
I'm
not
sure
if
you
estimate,
like
the
time
needed
to
you,
know,
find
the
solution
and
if
it
matters
I'm,
not
sure
if
those
two
tickets
are
more
or
less
similar
finding
the
solution.
Yeah.
B
B
B
A
C
C
C
B
A
A
A
Exactly
on
the
import,
the
grouped
import
product,
the
linking
back
of
the
Associated
SKUs
needed
to
be
updated,
and
so
it
linked
correctly.
So
we
might
find
that
this
is
the
same
place
for
the
bundle
and
in
which
case
this
could
be
switched
with
this
one.
This
could
be
switched
with
this
one.
What
I
would
suggest
is
what
I
can
do,
is
I'll
reach
out
to
Adam
and
see
if
he
has
any
more
information
about
it.
Yeah.
C
A
A
A
A
That
it
is
something
similar
to
this
one
and
then
it
would
be
an
okay
switch
or,
to
be
honest,
if
it's
a
couple
of
lines,
then
you
might
find
that
it
would
be
an
okay
switch
for
this
one.
So
what
I'll
do
is
I'll
reach
out
to
Adam
about
that
and
and
I
get
back
to
you
yeah
once
he's
once
he's.
Given
me
his
information
on
that,
okay,
thanks.
A
A
C
He
can
confirm
that
you
know
this
is
basically
very
similar
to
the
products
or
at
least,
if
he's
got
such
a
feeling.
I
can
check
with
our
depth,
but
pretty
stuck
here
as
well.
So
looking
for
that
quickest
solution
possible
so
well,
I'll
wait
for
your
confirmation
on
slack
might
be
maybe
I'll
say
yeah.
A
So
I
think
what
we
might
do
is
we
may
change
the
time
of
meeting,
because
I
think
a
few
people
were
unable
to
make
this
with
regards
to
the
change
a
difference
in
time
zones
I'll
send
around
an
email
about
that,
as
well
just
to
check
with
people,
because
I
would
love
to
get
a
bit
more.
A
bit
more
of
the
team
that
a
develop
like
that,
like
we're
missing
pretty
pretty
much
everyone,
so
cool.