AbstractEntity and DefaultBackend delete values in the parent scope incorrectly for Custom EAV Entities' Attributes

[ioweb-gr]

Preconditions (*)

1. Magento 2.4.3-p1
2. A module which creates a custom EAV Entity

Classes responsible for the value saving
\Magento\Eav\Model\Entity\AbstractEntity
\Magento\Eav\Model\Entity\Attribute\Backend\DefaultBackend

Steps to reproduce (*)

1. Please install the provided module which creates a custom EAV Entity and try to edit the name value in the Content -> TestEntity menu.
2. Play around with deleting the store view scope value in name attribute.
3. See the video for detailed explanation
   module.zip

You will notice that whenever you try to save in the store view scope for the attribute name with an empty value or with the use default value checkbox:
one value is going to be deleted in the attribute for the current store id properly
but if there isn't a current value for the store id, the default value is going to be deleted.

There are no docs on the correct procedure to create a custom EAV Entity but even if there was one, this looks more like a bug, rather than missing documentation so I decided to post it here.

Expected result (*)

1. The AbstractEntity class and the DefaultBackend will delete values only in the currently edited scope and retain the parent scope value

Actual result (*)

1. The AbstactEntity class and the DefaultBackend will delete values in the parent scope one level above the one being edited.

Notepad_C0cqkEcRaw.mp4

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• 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 @ioweb-gr. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

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

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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[ioweb-gr]

Can't reproduce on the instances because it requires installation of a module.

[engcom-Echo]

@ioweb-gr,

Thank you for reporting this issue. We have tried to reproduce the issue in Magento 2.4-develop branch and
followed the following steps to replicate the issue:

1- Installed the provided module which creates a custom EAV Entity
2- Go to Admin > Content > Test Entity

3- Click on "Add New TestEntity" > Save And Continue Edit

4- Change Scope to other store view and change identifier > Save And Continue Edit

5- Check the screen for "Store view". Name field got blank.

6- Check the screen for "All Store View", Name field got blank.

Hence, the issue reported is reproducible and confirmed.

[m2-assistant]

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

---

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