store_view_code column has empty values in csv

[GovindaSharma]

Preconditions:

1. Magento 2.2.2
2. PHP 7.1
3. Create Website, Store and Store View
4. Create product and asign for this Website

Steps to reproduce

1. Go to Back Office
2. System > Data Transfer > Export
3. Choose:
   3.1. Entity Type = Products
   3.2. Export File Format = CSV
4. Press 'Continue" button at the botom of the page

Expected result

store_view_code column should contain data from product chosen store.

Actual result

store_view_code column is empty

[magento-engcom-team]

Hi @GovindaSharma. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me {$VERSION} instance

where {$VERSION} is version tags (starting from 2.2.0+) or develop branches (2.2-develop +).
For more details, please, review the Magento Contributor Assistant documentation.

@GovindaSharma do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[GovindaSharma]

@magento-engcom-team give me magento2.2.2 instance

[GovindaSharma]

@magento-engcom-team still waiting for vanilla Magento instance

[ghost]

@GovindaSharma , thank you for your report.
We've acknowledged the issue and added to our backlog.

[GovindaSharma]

ok thank you.

[GovindaSharma]

@magento-engcom-team .i will work on this issue and provide you solution.or is their another way you can suggest me.

[AlexNeri00]

#mm18mx

[magento-engcom-team]

@AlexNeri00 thank you for joining. Please accept team invitation here and self-assign the issue.

[magento-engcom-team]

Hi @AlexNeri00. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[AlexNeri00]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @AlexNeri00. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @AlexNeri00, here is your Magento instance.
Admin access: http://ec2-34-228-235-121.compute-1.amazonaws.com/i-17784-2-3-develop//admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[AlexNeri00]

@magento-engcom-team give me 2.2-develop instance

[magento-engcom-team]

Hi @AlexNeri00. Thank you for your request. I'm working on Magento 2.2-develop instance for you

[magento-engcom-team]

Hi @AlexNeri00, here is your Magento instance.
Admin access: http://ec2-34-228-235-121.compute-1.amazonaws.com/i-17784-2-2-develop//admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[vpodorozh]

@magento-engcom-team give me test instance

[vpodorozh]

@magento-engcom-team give me 2.2-develop instance

[magento-engcom-team]

Hi @vpodorozh. Thank you for your request. I'm working on Magento 2.2-develop instance for you

[magento-engcom-team]

Hi @vpodorozh. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[magento-engcom-team]

Hi @vpodorozh, here is your Magento instance.
Admin access: http://34.228.235.121/i-17784-2-2-develop//admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[vpodorozh]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @vpodorozh. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @vpodorozh, here is your Magento instance.
Admin access: http://34.228.235.121/i-17784-2-3-develop//admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

Hi @vpodorozh. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[magento-engcom-team]

Hi @Valant13. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[magento-engcom-team]

Hi @AlexNeri00. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[magento-engcom-team]

Hi @GovindaSharma. Thank you for your report.
The issue has been fixed in #19395 by @Valant13 in 2.3-develop branch
Related commit(s):

• ea9f3598a400878d8e1daeb7ef5a07410ebd242a

The fix will be available with the upcoming 2.3.2 release.

[zulus]

I upgraded to 2.3.1 and still have empty store_view_code values.