POST public-api/assets/createFixedAssets

Internal. This is used to help identify errors if any.

Required. It is the primary identifier of an asset and it will be unique.

A brief description for the asset.

Internal. This helps to differentiate between a Fixed Asset (1) and a Multi-Quantity Asset (2).

Required. This is the identifier of the asset type (i.e. Laptop, Phone, Text Book).

Read Only. It is the description of the asset type inherited from the asset type record.

The department in which the asset belongs to.

The name of the department the asset belongs to.

Required. It is a site name where the asset is located.

Read Only. It is a site description.

Required. It is the location of the asset inside of the site where the asset is located.

This is the unique tag associated with the parent asset (group) the asset belongs to.

If true then the asset will behave as a group and allow other assets to become associated with it.

If true then any transaction that applies to this group asset will apply to all associated children assets.

If true then any audit performed on this group asset will apply to all associated children assets. Put another way, counting this asset during an audit will count everything inside of or associated with it.

The unique identifier of the vendor the asset was purchased from.

Read Only. It is a vendor's contact email.

Read Only. This is the name of the vendor's contact.

Read Only. This is the vendor's email.

Read Only. This is the name of the vendor.

Read Only. This is the vendor's website.

This is the serial number of the asset, typically unique.

This indicates the current condition of the asset, the condition must already exist in the system.

This is the name of the manufacturer of this asset.

This is the model number of the asset.

This is the category the asset belongs to (i.e. electronics, laptops, books). The category must already exist in the system.

This is the length of time the asset is typically checked out.

This indicates how much time is needed between when an asset is checked in and when it can be checked back out.

Read Only. If the asset is checked out this will be true.

If the asset type is depreciable then the individual asset can be set to depreciate by setting this flag to true and setting a purchase cost.

This indicates that the value of the asset will depreciate down to before it should be disposed.

Read Only. This field will only contain a value for any asset for which depreciation settings have been configured and calculated. After depreciation has been calculated for this asset, this field will contain the Assets Depreciated Value. See Depreciation in the help for more details.

Read Only. The equation to calculate is BookValue = AssetPdCost - AssetCurrentDepreciation. This field will only contain a value for any asset for which depreciation settings have been configured and calculated. After depreciation has been calculated for this asset, this field will contain the Assets Depreciated Value. See Depreciation in the help for more details.

This is the date from which the asset begins to depreciate.

For Multi-Quantity assets this is the default cost of the asset. For Fixed Assets, this is the purchase cost.

This is the name of the person to whom the asset is checked out to. This could be a Customer, Employee, or Vendor.

This is the unique identifying number of the Customer/Employee/Vendor to whom the asset is checked out to.

Read Only. This indicates the current status of the asset. 1 is for active and 2 is for inactive.

This is the name of the attachment to use as the default.

This will be True if this asset has attachments.

This is for Multi-Quantity assets. It Indicates the amount/quantity available at the location.

Read Only. This is the name of the employee who takes ownership of this asset.

This is the unique identifier number of the employee who takes ownership of the asset.

Read Only. This is the first name of the owner.

Read Only. This is the last name of the owner.

This is the provider of the warranty for the asset.

This is the date on which the warranty begins.

This is the date on which the warranty ends.

This is the purchase order number of the asset.

This is the date on which the asset was purchased.

This is the cost of the asset when it was purchased.

This is the geographical latitude of the asset.

This is the geographical longitude of the asset.

This is the geographical altitude of the asset.

The geographical timezone in UTC indicating where the asset is located.

This indicates the accuracy with which the geolocation was captured.

This ia a list of custom fields associated with the asset.

This is a list of attachment GUIDs to add to this asset. The attachment must exist in the system already and this just links the attachment with this asset.

This is a list of attachment GUIDs to remove from this asset.

This is a list of attachments associated with the asset. This list is the GUID of the attachment and the file name of the attachment.

Read Only. This indicates if the asset is checked out and has a due date.

Read Only. This is the date the asset was created in our system.

Read Only. This is the date the asset was last updated in our system.

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.