Issue at product import when provided with custom options-type: file (Created Product does not contain price for custom-option and show only the first file type extension provided)

[ATIFYAQOOB869]

Preconditions and environment

• Magento version: 2.4.7
• PHP-8.3

Attached the CSV used during the testing.
export_catalog_product_20240606_161012.csv

Steps to reproduce

1. Create a CSV file for product import.
2. Add the necessary data for the product along with custom_options.
3. Add the type: file and other data for the custom_options column. Make sure to add more than one file_extension attribute.
4. Navigate to System>Import.
5. Choose Entity type: Products and Import behaviors: Add/Update. Leave the remaining settings as default. (separators: ",")
6. Validate and Import the Product.
7. Check the created product customization options section on the edit product page. The price is missing and file extension show only the first extension provided in the CSV.

Expected result

Actual result

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @ATIFYAQOOB869. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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.

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Bravo, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[engcom-Bravo]

Hi @ATIFYAQOOB869,

Thanks for your reporting and collaboration,

We have verified the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Steps to reproduce

• Create a CSV file for product import.
• Add the necessary data for the product along with custom_options.
• Add the type: file and other data for the custom_options column. Make sure to add more than one file_extension attribute.
• Navigate to System>Import.
• Choose Entity type: Products and Import behaviors: Add/Update. Leave the remaining settings as default. (separators: ",")
• Validate and Import the Product.
• Check the created product customization options section on the edit product page. The price is missing and file extension show only the first extension provided in the CSV.

The price is missing and file extension show only the first extension provided in the CSV.

Hence Confirming the issue.

Thanks.