Import data 2.2.6 Value for 'product_type' attribute contains incorrect value

[ankit-sf]

Preconditions (*)

1. magento 2.2.6 (vanilla instance)

Steps to reproduce (*)

1. create an attribute with code product_type http://i.prntscr.com/AwUJuhizQKatBwNwRa1S7Q.png with type: dropdown scope: global sortable, comparable: no
2. add it to a family and create a product.
3. go to import profiles download sample file then reimport sample file

Expected result (*)

1. [Screenshots, logs or description]
2. import should be completed

Actual result (*)

1. Value for 'product_type' attribute contains incorrect value, see acceptable values on settings specified for Admin in row(s): 1, 2, 3, 4, 5, 6
   http://i.prntscr.com/lsI-FNJnTzO0gEttdZp1wA.png

2. Also reproduced on earlier versions.

[magento-engcom-team]

Hi @ankit-sf. 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 (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

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

• yes
• no

[ankit-sf]

@magento-engcom-team give me 2.2.6 instance

[magento-engcom-team]

Hi @ankit-sf. Thank you for your request. I'm working on Magento 2.2.6 instance for you

[magento-engcom-team]

Hi @ankit-sf, here is your Magento instance.
Admin access: https://i-19346-2-2-6.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[ankit-sf]

yes, i confirm that i was able to reproduce the issue on vanilla Magento instance following steps to reproduce

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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: 👇

• 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-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!

• 5. 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

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

Hi @ankit-sf why you think this is a bug? if you add some aditional atributes you need to add this to your csv file, so sample csv is not working any more, if you add some additional attributes in default attribute set. this is not a bug.

[ankit-sf]

no that's not the case. because newly added custom attributes is not required field.
the issue is that after adding a field, any CSV import doesn't work without that attribute and there is an error.

@ankit-sf This what i'm talking about, you need to use your custom attribute set, not default, you set VALUE is not required, but not an attribute, if you add this to you custom attribute set you dont have an error.

@ankit-sf in sample csv file

[ankit-sf]

@engcom-backlog-nazar i'll check and revert in some minutes