Why don't the Customer Attributes relations work while placing an order in the Backend?
It is the expected extension behavior. According to the Customer Attributes extension logic, attribute relations don't work for orders created in the Backend, since store admins are believed to know the store logic. That's why they are able to view all the attribute options to select from.
Related Articles
Why don't the Order Attributes relations work while placing an order in the Backend?
It is the expected extension behaviour. According to the Order Attributes extension logic, attribute relations don't work for orders created in the Backend since store admins are believed to know the store logic. That's why they are able to view all ...
My Order Attribute relations don't work, how can I check if everything is configured correctly?
Firstly, check which attribute is used as a parent attribute in the relation. The Order Attributes relations could be created only for parent attributes with the following types: Dropdown, Radio Button, Checkbox Group. Secondly, please, make sure the ...
Where are the custom attributes displayed in the order details?
According to the extension logic, all the Order Attributes are stored in a separate table. That is why they are displayed in the additional information block. Backend order view: Frontend order view: It is not possible to move Order Attributes to the ...
My Customer Attribute relations don't work, how can I check if anything is not configured correctly?
We'd recommend you check which attribute is used as a parent attribute in the relation. Customer Attributes relations could be created only for parent attributes with the following types: Multiple Select; Dropdown; Multiple Checkbox Select with ...
Is the Customer Attributes M2 compatible with the One Step Checkout extension?
The extensions work smoothly together. It is possible to add Customer Attributes of various types to be displayed on the One Step Checkout page. To make an attribute appear on the checkout page, the following option should be enabled in the attribute ...