Magento Community Edition: Version 2.4.5 - Import Stock Sources Added Extra Column in Import CSV File, Validation message is not understandable to the end users.

[RocktechnolabsDev]

Preconditions and environment

1. Magento Community Edition 2.4.5 without sample data is installed.
2. Website have products
3. 2.4-develop instance with inventory enabled.

Steps to reproduce

1. Login into admin > System > Data Transfer > Import, Select "Stock Sources" option from Entity Type drop down.
2. Select "Add/Update Complex Data" option from Import Behaviour drop down.
3. Rest of fields leave as it is.
4. Upload prepared CSV file for import the Stock Sources as per the below attachment. Or by adding new/extra column with name of "Test" (Column name should start with capital letter)
5. Click on check data, "columnNameInvalid" Validation message is not understandable to the end users. While same case checked with "Advanced Pricing" entity, Validation message is easily understandable to the end users.

Expected result

Validation message is understandable to the end users, As working with "Advanced Pricing" entity

Actual result

columnNameInvalid

Additional information

Please check provided screenshot and CSV file for your reference.

CSV files

advanced_pricing.csv
stock_sources.csv

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 @UtsavRock1811. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

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

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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-November. 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.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-November]

Hi @UtsavRock1811 ,
Thank you for reporting and collaboration. Verified the issue on Magento 2.4-develop instance but unable to reproduce the issue with below steps performed:

1. Imported Stock sources with valid csv file - No issue. imported successfully.
2. Imported Stock sources with invalid CSV file by removing mandatory column - No issue. Expected error message is displayed.
3. Imported Stock sources by adding extra invalid column. Imported successfully with no errors.
   
   
   Kindly recheck the issue on Magento 2.4-develop instance and provide missing steps if any if the issue is still reproducible.
   Thank you.

[RocktechnolabsDev]

Hi @engcom-November,

I think you are checking with new/extra column with name in lower cases, Same case i have checked and it is working fine, Can you please check with provided csv file by me or Make first letter in capital of new/extra column.

I have added new/extra column with name of "Test" and it's throwing the error message, And validation message is not understandable to the end users.

Thank you.

[engcom-November]

Thank you for the update @UtsavRock1811 ,
Verified the issue again on Magento 2.4-develop instance as per above steps and the issue is reproducible. Hence updating the description and confirming the issue.