Customer Prefix is not saved in guest orders

[norgeindian]

Preconditions (*)

1. Magento 2.3.4

Steps to reproduce (*)

1. Set customer/address/prefix_show to required
2. Go to the frontend and purchase an order as guest
3. During the checkout process make sure, that the prefix is required and this way filled

Expected result (*)

1. I would expect that the prefix is saved in the database and is shown in the order view in the backend.

Actual result (*)

1.The prefix is not saved and not shown in the backend order view.

[m2-assistant[bot]]

Hi @norgeindian. Thank you for your report. To help us process this issue please make sure that you provided the following information:

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

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@norgeindian do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant[bot]]

Hi @krishprakash. 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: :point_down:

• [x] 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.

• [x] 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.

• [x] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [x] 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!

• [x] 5. Add label Issue: Confirmed once verification is complete.

• [x] 6. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

:white_check_mark: Confirmed by @krishprakash Thank you for verifying the issue. Based on the provided information internal tickets MC-33348 were created

Issue Available: @krishprakash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[m2-assistant[bot]]

Hi @AndreyChorniy. Thank you for working on this issue. Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• [ ] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 2. 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!

• [ ] 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[AndreyChorniy]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @AndreyChorniy. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @AndreyChorniy, here is your Magento instance. Admin access: https://i-27849-2-4-develop.instances.magento-community.engineering/admin_d039 Login: 8286f7e1 Password: a94881305837 Instance will be terminated in up to 3 hours.

[AndreyChorniy]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @AndreyChorniy. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[AndreyChorniy]

Hey @krishprakash,

I would like to ask you to recheck this issue once again on your side. Because I cannot reproduce this on Magento 2.4-develop instance

[sprankhub]

It is indeed shown in the billing and shipping address. However, it is not stored in the database in sales_order.customer_prefix.

[chirag-d-wagento]

@magento I'm working on it

[chirag-d-wagento]

#dmcdindia2020

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[norgeindian]

@chirag-d-wagento , any news regarding this issue?

[chirag-d-wagento]

@norgeindian integration test is remaining but i never write an integration test.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[sprankhub]

This is still relevant.

[BrocksiNet]

Is this not solved here: https://github.com/magento/magento2/pull/30419 ?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 28 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[norgeindian]

Is this not solved here: #30419 ?

In general, it seems so, but this PR has never been merged. So it still persists in my eyes

[engcom-Bravo]

Hi @norgeindian,

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.

Customer prefix is not stored in database.

Hence Confirming the issue.

Thanks.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-12298 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.