Why don't the Order Attributes relations work while placing an order in the Backend?

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 the attribute options to select from. 

      • Related Articles

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

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

      • Order Attributes | GraphQL methods

        Queries amOrderattrAvailableAttributes (cartId: String!) description: get the list of available order attributes amOrderattrAttributesRelations description: get information about order attribute relations Mutations saveAmOrderattrValues (cartId: ...

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

      • Order Attributes API

        1. Amasty\Orderattr\Api\EntityDataRepositoryInterface - class for managing order attributes in the backend: POST /V1/amasty_orderattr/entityData, method="save" - create an attribute; PUT /V1/amasty_orderattr/entityData/:entityId, method="save" - edit ...