EAV attribute backend model 'ArrayBackend' filters non numeric values

[DiskoPete]

Preconditions and environment

• Magento ^2.4.6

Steps to reproduce

1. Create a new product attribute eg 'foobar' with

• a \Magento\Eav\Model\Entity\Attribute\Backend\ArrayBackend backend model
• a custom source model which has non numeric option values

2. Save the product with changed attribute 'foobar' values (eg through a REST API call)

Expected result

Changed/new attribute values are saved to the product.

Actual result

Attribute values are not saved

Additional information

The non numeric values are filtered here and won't be saved:
https://github.com/magento/magento2/blob/2.4.6/app/code/Magento/Eav/Model/Entity/Attribute/Backend/ArrayBackend.php#L67

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 @DiskoPete. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• 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.

[DiskoPete]

@magento I am working on this

[m2-assistant]

Hi @DiskoPete! 👋
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.

[DiskoPete]

@magento add to contributors team

[m2-assistant]

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

[DiskoPete]

@magento I am working on this

[m2-assistant]

Hi @engcom-November. 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

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

[engcom-November]

Hello @DiskoPete,

Thank you for reporting and collaboration!

We have tried to reproduce the issue on 2.4-develop, We found that the custom attribute value is not being saved and is being deleted when we try to change the value from REST API call, There is already an issue on Custom attribute being deleted.
The issue is open, Please refer to #37426 for more information.

You can refer the below screenshots

After using PUT to change custom attribute value, The custom attribute is being deleted.

Hence putting the Issue on hold.
Please let us know if we are missing something.

Thanks.

[DiskoPete]

Hi @engcom-November

Thanks for your feedback.
I agree that the mentioned issue is connected.

The fix I prepared will probably also solve the other issue.
#37677

[abukatar]

Hello @DiskoPete

Thank you for your contribution and collaboration!

An internal Magento team is working on this issue right now (as Jira ticket ACP2E-2647).

[abukatar]

@magento I'm working on it

[asim-blueprintprep]

This ticket is closed, but the linked MR is still open...does anyone have a link the the MR that fixed this issue?