Magento2: Export Products bug. I can't exclude attributes from CSV file.

[AleksLi]

I can't exclude some attributes from CSV file with with all products. Checkboxes don't work properly.

Preconditions

1. Magento 2.2.2 & 2.3.x
2. mysql Ver 15.1 Distrib 10.0.31-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
3. PHP 7.0.22

Steps to reproduce

1. Make sure you have products in your Magento 2.
2. Create a couple of custom attributes (color, size for example). Not sure this field is __required__. I think this bug will reproduced without custom attributes.
3. Go to BO-> System -> Data Transfer (Export).
4. Choose:
   __Entity Type__ select = Products
   __Export File Format__ = CSV
   __Fields Enclosure__ = unchecked
5. I tried to set checkbox on SKU field for example.

Expected result

1. I should get CSV file wihout SKU column (see the screenshot attached below).

Actual result

1. Here is what I get. The same screenshot attached below.

[oefterdal]

I think SKU is requiered since its also used for matching on import. So think the real bug is that you can set exclude on SKU.

[AleksLi]

@oefterdal I tried with other attributes but it failed either. Try to exclude other attributes from CSV. It will be the same result

[ghost]

@AleksLi, this is not a bug. By setting this fields you can exclude some products from export, not columns.

[simonmaass]

i agree that it is confusing - i also thought that it will exclude the column!

[arnoudhgz]

@engcom-backlog-pb @AleksLi @simonmaass according to the documentation the column should actually be excluded from the export.

I could reproduce his on 2.3.2

[m2-assistant[bot]]

Hi @engcom-Charlie. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento 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_!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-Charlie
Thank you for verifying the issue. Based on the provided information internal tickets MC-19661 were created

Issue Available: @engcom-Charlie, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[arnoudhgz]

I found out that the skip_attr (which is posted through the Exclude column) is not saved in the queue_message table.

[magento-engcom-team]

Hi @AleksLi.

Thank you for your report and collaboration!

The issue was fixed by Magento team. The fix was delivered into magento/magento2:2.3-develop branch(es).
Related commit(s):

• c1b7ba0b1fa7e1737a94d9307a9a40d115f42e09
• e01d260bb49313b3cc2ecbc993c4a16dd29e3856
• a16f08be22a8b1b0376ef9ddee66c7b43c0895a3
• cd05c5a96b7e397f7f18d08bb431e902747227c4
• a467c03e5642501718770688070d4d98d324b09f
• bf72e2374f84076641623215381aeb78569d83ea
• be2c55edf1c650a0cbcb02e248fd21d2754aa51a
• bc26eb16471d7d44525a8471b9e8847bd4f5d98a
• 5c6666895920f92ebeaf8cf078e9ce6c2a38b3be
• d178a55fdf4e95d02b085d0d2d7f05535321cdab
• 56bf57ecbd0caed993e20c9d389b900eebbf746b
• eb5f20130e50ba3ad235e1bd371ae1ff4025b5f3
• 900a707c9980c760137d573fa10b45eaf1414ee1
• 8632e6df4f4146e230bbb5b13432d8af797eeb9a

The fix will be available with the upcoming 2.3.4 release.

[simonmaass]

what a shame that this was not included in 2.3.3....

[ABARAUJOMGA]

While there isn't a 2.3.4 release, they could say something to us about how to make this work.

[rickyhub]

While there isn't a 2.3.4 release, they could say something to us about how to make this work.

I need a fix too please.
Regards