Customer address unique attribute not validated

[bartlubbersen]

Preconditions

1. Magento 2.1.3
2. PHP7

Steps to reproduce

1. Add a new customer address attribute that should be unique.
2. Save the value in two different addresses with the same value. (via Admin)

Expected result

1. It should throw an error that the value must be unique.

Actual result

1. It is saving both addresses with the same value.

Comment

I tested this with two existing addresses and with adding a new address in both cases the problem exists.

[veloraven]

@bartlubbersen thank you for your report.
What Magento edition do you use?
New customer address attributes are enable in Enterprise Edition only. So if you use EE please report this issue via the Support portal of your account or Partner portal if you are a partner reporting on behalf of a merchant. Github is intended for Community edition reports given no account management for CE users. This will allow for proper tracking of issues at the account level.
If you use Community Edition please address your question at programming questions forum or Magento Stack Exchange. As it is not a native behavior of Magento CE and we can not treat it as an issue

[bartlubbersen]

@veloraven,
We are using CE and not enterprise, however this still is a bug and not a question. Since you can also add custom address attributes via setup scripts, so it still needs solving.

[ishakhsuvarov]

@bartlubbersen Please look into the Pull Request #9712 proposed by @bka and @storbahn
It is aimed to fix this issue, and is already merged in the branch develop. Hope that helps for now.

[magento-engcom-team]

@bartlubbersen, thank you for your report.
We've created internal ticket(s) MAGETWO-81796 to track progress on the issue.

[mukdam]

Also issue in customer attribute unique in magento 2.2.0

[m2-assistant]

Hi @sdzhepa. 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).

  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.

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

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

• 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!

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

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

[sdzhepa]

We are not able to reproduce this on the latest code 2.4-develop
Seems it was already fixed