You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Another website (e.g. Second Website) besides the Main Website.
Steps to reproduce
Create a custom EAV attribute for the customer entity. There are many ways to do this, but here's Adobe's Add a custom text field attribute.
Make sure the attribute appears: Admin Panel -> Customers -> All Customers -> Click "Edit" on any customer -> Select Account Information; the new attribute should be there.
Populate the new attribute with anything and click Save and Continue Edit (this should work).
On the Associate to Website dropdown select the "Second Website" and click Save and Continue Edit.
Edit the new attribute once again, and click Save and Continue Edit.
Expected result
The new attribute updates its value.
Actual result
The new attribute maintains its previous value set with Main Website scope.
Additional information
Allowing for custom attributes is a basic but powerful feature, and this issue prevents custom attributes from working for customers belonging to any website other than the Main Website.
If it helps, on this Abobe article, it says that "The scope of the Customer custom attribute is Global only, while other entities support the Global, Website, and StoreView scopes." However, I found a reference to the new attribute on the table "customer_eav_attribute_website". I also tried removing the entry from that table but it doesn't fix the issue.
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”.
The text was updated successfully, but these errors were encountered:
Hi @mc-christian. 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.
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.
Preconditions and environment
Steps to reproduce
Expected result
The new attribute updates its value.
Actual result
The new attribute maintains its previous value set with Main Website scope.
Additional information
Allowing for custom attributes is a basic but powerful feature, and this issue prevents custom attributes from working for customers belonging to any website other than the Main Website.
If it helps, on this Abobe article, it says that "The scope of the Customer custom attribute is Global only, while other entities support the Global, Website, and StoreView scopes." However, I found a reference to the new attribute on the table "customer_eav_attribute_website". I also tried removing the entry from that table but it doesn't fix the issue.
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: