Saving orders in bulk
SaveBulkOrderSummary API to save the
summary of multiple orders to the index. You can integrate Sterling Order Management System Software with
Order Service by using the built-in Order Search integration
to save order documents to the writable index in batch.
You can use the SaveBulkOrderSummary API for history mass sync to save history
orders as well by using the saveTo optional parameter in the bulk save request. The
saveTo optional parameter accepts an index name and all the orders in the bulk
request are indexed to that index. This helps you to segregate historical orders and index them into
separate indices that are created for the past years, while migrating orders to search index. This
feature is available only when the use_index_name_in_request property is set. Pass
IndexName during the first insert of orders. For any further updates on the orders
the index name is not required. If you pass index name on update of an order, it gets updated in the
index where it already exists and the index name that is passed is ignored. After the initial
migration is completed, the property must be reset back to the factory value so that the save
operation can identify the index where the order is present and update it. A failure of resetting
the property after the initial migration can cause duplicate orders and data integrity issues.