Importing: non-default multiple value separator can't be used in custom multiple select attribute

[evs-xsarus]

Preconditions (*)

Magento 2.4-develop

Steps to reproduce (*)

1. Create a custom product attribute with type multi_select.
2. Create a catalog_product.csv that contains product data and at least 1 multiselect attribute with 2 options or set two option values to the product, save and make export
3. Separate options with custom separator, for example, |||
   
4. Go to the Magento admin panel -> System -> Import
5. Set Multiple value separator to |||
   
6. Choose your file and click the Check Data button

Expected result (*)

1. Validation should pass without problems

Actual result (*)

1. Validation fails and tells us we have incorrect values for our multiselect attribute
   

The code on https://github.com/magento/magento2/blob/2.3.1/app/code/Magento/CatalogImportExport/Model/Import/Product/Validator.php#L226

Fails to get the configured multiple value separator and pass it on in function $this->context->parseMultiselectValues.

NB I've actually imported the CSV programmaticaly and set parameter '_import_multiple_value_separator' as data in Magento\ImportExport\Model\ImportFactory->create().

Related tickets:

• CatalogImportExport multiselect values will fail validation with custom multiValueSeperator CatalogImportExport multiselect values will fail validation with custom multiValueSeperator #6984
• Importing: non-default multiple value separator can't be used in additional_images column Importing: non-default multiple value separator can't be used in additional_images column #11026

[m2-assistant]

Hi @evs-xsarus. 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 give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@evs-xsarus do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @AlexWorking. 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 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 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.

[magento-engcom-team]

✅ Confirmed by @AlexWorking
Thank you for verifying the issue. Based on the provided information internal tickets MC-17346, MC-17347 were created

Issue Available: @AlexWorking, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[Kipperlenny]

Please don't forget the wrongly closed ticket #8754 with a similar problem (Pipe Seperator)

[VivekShingala]

We are on Magento 2.3.5-p2 and facing the same issue with pipe separator for multi values. Is there any workaround for this issue?