B2B company save: "Allow Quotes" setting always disabled

[jbruni]

Preconditions and environment

• Magento version 2.4.8 - with B2B extension

Steps to reproduce

1. At admin, go to Customers > Company, and click the "Edit" link to edit a company.
2. Under "Advanced Settings", make sure to enable the "Allow Quotes" setting.
3. Click the "Save" button to save the company settings.
4. Verify the "Allow Quotes" setting after saving.

Expected result

Expected: company's "Allow Quotes" setting to be enabled.

Actual result

Actual: company's "Allow Quotes" setting remains disabled.

Additional information

When saving the company, the "Allow Quotes" gets always disabled, regardless of the chosen setting value, and even when the setting value is not changed at all (when we save the company after modifying another setting).

By debugging I found a workaround to turn the setting back to enabled: using the browser's Dev Tools, Network tab, I "copy as cURL" the edit's POST HTTP request and modify it, replacing the value for is_quote_enabled from true to 1 - and then running the curl command from the bash command line interface.

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 @jbruni. 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.

[jbruni]

@magento I am working on this

[m2-assistant]

Hi @jbruni! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

[jbruni]

@magento add to contributors team

[m2-assistant]

Hi @jbruni! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

[jbruni]

@magento I am working on this

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

[jbruni]

I tried to reproduce in a fresh install, and found the issue is not reproducible.

Conclusion: some custom or third-party extension is causing the issue.

Closing.