Hi @oskar-olaussen. 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.

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.

Hi @oskar-olaussen,

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.

A customer group with code "öööööööööööööööö" (16 characters) is created.

Hence Confirming the issue.

Thanks.

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

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

@magento I'm working on this

@oskar-olaussen, what is the use case, when you need a customer group code both:

1. longer than 16/32 symbols
2. contain no Latin symbols?

@ihor-sviziev Well the main point is to have the system working logically when there are multibyte characters present. So either prevent user from having them in the customer group code or fix the unexpected behaviour. Please note that I chose an extreme example where there are just multibyte characters present. The same unexpected behaviour will happen if you have a long customer group code with some of the chars being multibyte.

I came across this when I was trying to match customer codes with an external system that had customer group identifiers longer than 32 characters and containing multibyte chars. Tried then truncate the customer group codes to the max allowed length in Magento but noticed that the code saved did not match the input given.

A more realistic example: If I save a customer group called "Käärijä-fanien alennusryhmä kesä" what currently gets saved is "Käärijä-fanien alennusryhmä ".