You are here:
Omnistudio Data Mapper Setup for Order Management Integration Layer
Order Management Integration Layer requires the OrderBackSync and OrderItemBackSync Data Mappers to update order records.
These Data Mappers have these features:
-
Map fields from incoming messages to order record or order item record fields.
-
Support custom field names and dot notation.
Dot-notation example:
Account.PrimaryContactId__r.IsPartner__cwill allow you to update a contact's field from an order.
Data Mapper can negatively impact performance because of additional DML and SOQL transactions. If you know the field names that need to be updated and those fields are not a lookup to a related record, then you can send the field names and their values in the fields and specify the updateMethod to be directfieldupdate. This slightly improves performance by avoiding Data Mapper-related DML and SOQL transactions.
Order-Level Notification
Order-level notification messages contain sections that update order record fields. To perform updates, Order Management Integration Layer requires a Data Mapper named OrderBackSync, which will map the fields in the incoming notification messages to the corresponding order record fields.
OrderBackSync is invoked by the following types of order-level notifications:
Order Item-Level Notification
OrderItem-level notification messages contain sections that update fields and attributes. For field updates, Order Management Integration Layer requires a Data Mapper named OrderItemBackSync, which will map the fields in the incoming notification message to the corresponding order item record fields.
OrderItemBackSync is invoked by the following types of order item-level notifications:
- Notification Examples for Order Management Integration Layer
Order Management Integration Layer can send field updates for the following notifications. When the fields container is included in a notification, the corresponding Omnistudio Data Mapper is invoked: OrderBackSync or OrderItemBackSync.
