Import Customer with Feature B2B Company

[Yoann-D]

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.

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

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

[m2-assistant]

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.

• 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

  - 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]

Hi @Yoann-D,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Lates 2.4-develop instance and we are not able to reproduce the issue.Could you please elaborate the steps to reproduce and help us to proceed further.

Thanks.

[engcom-Bravo]

Hi @Yoann-D,

This issue is being closed since it has not been updated in a long time.Please feel free to reopen or raise a new ticket if the issue still exists.

Thanks.