This session creates, updates, and deletes Prices in bulk. The data for create and update is provided by the consumer via the form object. OsidForms are requested for each create or update and may not be reused.

Create and update operations differ in their usage. To create a Price, a PriceForm is requested using getPriceFormsForCreate() specifying the desired record Types or none if no record Types are needed. Each of the returned PriceForms will indicate that it is to be used with a create operation and can be used to examine metadata or validate data prior to creation. Once a PriceForm is submiited to a create operation, it cannot be reused with another create operation unless the first operation was unsuccessful. Each PriceForm corresponds to an attempted transaction.

The PriceForms returned from getPriceFormsForCreate() may be linked to the originating request through the peer Ids of the PriceForm. In the case where there may be duplicates, any PriceForm of the same peer Ids may be used for a create operation.

Once a batch of PriceForms are submitted for create, a CreateResponse is returned for each PriceForm, although the ordering is not defined. Only errors that pertain to the entire create operation are returned from createPrices(), errors specific to an individual PriceForm are indicated in the corresponding CreateResponse. CreateResponses may be linked to the originating PriceForm through the PriceForm Id.

For updates, PriceForms are requested to the Price Id that is to be updated using getPriceFormsForUpdate() where the reference Id in the PriceForm may be used to link the request. Similarly, the PriceForm has metadata about the data that can be updated and it can perform validation before submitting the update. The PriceForm can only be used once for a successful update and cannot be reused.

Once a batch of PriceForms are submitted for update, an UpdateResponse is returned for each PriceForm, although the ordering is not defined. Only errors that pertain to the entire update operation are returned from updatePrices(), errors specific to an individual PriceForm are indicated in the corresponding UpdateResponse. UpdateResponses may be linked to the originating PriceForm through the PriceForm Id.

The delete operations delete Prices in bulk. To unmap a Price from the current Store, the PriceStoreAssignmentSession should be used. These delete operations attempt to remove the Price itself thus removing it from all known Store catalogs. Bulk delete operations return the results in DeleteResponses.

Like all OsidSessions, PriceBatchAdminSessions are dedicated to single processing threads and a single authenticated user.