Skip to content

Import Customer with Feature B2B Company #39860

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
5 tasks
Yoann-D opened this issue Apr 24, 2025 · 1 comment
Open
5 tasks

Import Customer with Feature B2B Company #39860

Yoann-D opened this issue Apr 24, 2025 · 1 comment
Labels
Issue: ready for confirmation Reported on 2.4.7-P8 Indicates original Magento version for the Issue report.

Comments

@Yoann-D
Copy link

Yoann-D commented Apr 24, 2025

Preconditions and environment

  • Magento version 2.4.7-P8

  • B2B Company is enabled

Steps to reproduce

Customer import no longer works since 2.4.7-p8

When importing a customer file via Magento, and the customers are already all present in the "company_advanced_customer_entity" table,

We get an import error.

Indeed, the "processDefaultStatus" function was added since 2.4.7-p8 (vendor/magento/module-company-customer-import-export/Model/Import/Customer.php). This function checks for non-existent IDs in the company_advanced_customer_entity table to import them.

Image

Except that if all the customers are present, the "$nonExistingIds" variable is empty. This throws the error:

[2025-04-24T10:02:58.178003+00:00] report.ERROR: Error during Customer Import Cron: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 1, query was: INSERT INTO company_advanced_customer_entity (customer_id) VALUES [] []

To correct this, I added the condition

Image

Expected result

Import success

Actual result

Import error

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”.
Copy link

m2-assistant bot commented Apr 24, 2025

Hi @Yoann-D. 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.


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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: ready for confirmation Reported on 2.4.7-P8 Indicates original Magento version for the Issue report.
Projects
Status: Ready for Confirmation
Development

No branches or pull requests

2 participants