POST public-api/transactions/public/asset/move

This method moves the assets that are passed in, both Fixed and Inventory assets. For moving Fixed Assets, you don’t need to provide the from location or quantity fields. Requires the Allow Move permission, enforces Role Site and Asset Type security Accepts a maximum of 500 records at a time

Request Information

URI Parameters

None.

Body Parameters

Collection of AssetMoveModel

Name	Description	Type	Additional information
AssetTag	Required, the unique identifier of the asset to be moved	string	None.
FromSiteName	The site the asset is being moved out of, required for multi-quantity assets	string	None.
FromLocationCode	The location the asset is being moved out of, required for multi-quantity assets	string	None.
FromGroupTag	The group the asset is being moved out of, required for multi-quantity assets	string	None.
ToSiteName	Required, the site the asset is being moved into	string	None.
ToLocationCode	the location the asset is being moved into	string	None.
ToGroupTag	the asset tag of the group the asset is being moved into	string	None.
Quantity	the amount being moved, required for multi-quantity assets	decimal number	None.
RecordSource	Optional, the device performing the transaction (i.e. name of kiosk, mobile device, or PC)	string	None.
Note	Optional, any transaction notes to log with the transaction	string	None.
Condition	during move transaction, the asset condition could be set. if a valid value is specified, then the new asset condition value will be used to update the asset record as well as stored into the move transaction history.	string	None.

Request Formats

application/json

Sample:

[
  {
    "AssetTag": "sample string 1",
    "FromSiteName": "sample string 2",
    "FromLocationCode": "sample string 3",
    "FromGroupTag": "sample string 4",
    "ToSiteName": "sample string 5",
    "ToLocationCode": "sample string 6",
    "ToGroupTag": "sample string 7",
    "Quantity": 1.0,
    "RecordSource": "sample string 8",
    "Note": "sample string 9",
    "Condition": "sample string 10"
  },
  {
    "AssetTag": "sample string 1",
    "FromSiteName": "sample string 2",
    "FromLocationCode": "sample string 3",
    "FromGroupTag": "sample string 4",
    "ToSiteName": "sample string 5",
    "ToLocationCode": "sample string 6",
    "ToGroupTag": "sample string 7",
    "Quantity": 1.0,
    "RecordSource": "sample string 8",
    "Note": "sample string 9",
    "Condition": "sample string 10"
  }
]

Response Information

Resource Description

WaspResultOfListOfInt32

Name	Description	Type	Additional information
Data	Type specific result that always depends on the function called.	Collection of integer	None.
Messages	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.	Collection of WtResult	None.
BatchNumber	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.	integer	None.
HasError	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.	boolean	None.
HasHttpError	True if an API function call could not be fully posted to the server or the results could not be fully returned.	boolean	None.
HasMessage	True if any message is available.	boolean	None.
HasSuccessWithMoreDataRemaining	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.	boolean	None.
TotalRecordsLongCount	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.	integer	None.

Response Formats

application/json

Sample:

{
  "Data": [
    1,
    2
  ],
  "Messages": [
    {
      "ResultCode": 0,
      "Message": "sample string 1",
      "HttpStatusCode": 200,
      "FieldName": "sample string 2"
    },
    {
      "ResultCode": 0,
      "Message": "sample string 1",
      "HttpStatusCode": 200,
      "FieldName": "sample string 2"
    }
  ],
  "BatchNumber": 1,
  "HasError": false,
  "HasHttpError": false,
  "HasMessage": true,
  "HasSuccessWithMoreDataRemaining": false,
  "TotalRecordsLongCount": 1
}