POST public-api/ic/item/saveContainerItem

This is used to group similar container types together.

FIFO, LIFO, Moving Average, or null value

null: not applicable and no action will be taken for the sales tax vs non-sales tax indicator true: sales tax is applicable false; sales tax is not applicable

If null, assumes the new item will use the default "Global" number generator for Trackby Container Id if True, then this Item will have a private Trackby Container Id generator

Type specific result that always depends on the function called.

List of Messages. All APIs should return messages. If an API function returns an error you can find more information about the error or errors in this collection of messages.

This is a global batch number generated by a mass group of transaction records to be returned to the consumer on each call to rolling transaction rules. This requests that each group of Move/Add/Remove transaction batches is tied together. In prior products (such as Mobile Asset Cloud), all are set to null and the only time when the batch number is generated is for multiple check-out transactions but the old is to generate for each responsible party.

True if an API function result has an error message in the results. If this is false, the function succeeded but other informative messages may be available.

True if an API function call could not be fully posted to the server or the results could not be fully returned.

True if any message is available.

True if the server sent part of the data and there is more data available. Use with paging APIs to fetch data one page at a time.

This is the total number of records available in the database based on the query and filer conditions provided. It is possible that the value can change from call to call as users add and delete records so this should not be used to page through multiple recordsets of data. This is used, for example, to set relative scroll bar sizes. When paging through data using functions like the assetadvancedinfosearch, calculating TotalRecordsLongCount for every page full of data is an time-consuming operation. To avoid that extra calculation, and help prevent throttling, assign TotalRecordsLongCount to TotalCountFromPriorFetch in the AdvancedSearchParameters to skip recalculating this total page count and to page thru the records faster.