Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Create Other Asset by rest API custom fields

So i have added script that will allow me to import from excel info for other assets and it creates the assets fine.

In the CMDB ci Types i added a new custom field of MAC Address to the Other Asset type and it shows up and i can add info to it.

I have manually created assets and entered info on them in the right side menu and it saves etc.

When i use Rest API and do a get of all my other assets the

custom_fields_values and all its sub keys are empty.

I tried to create an asset via script and specify it and when i run a get it shows the custom fields info but nothing shows up on the asset in the web gui.

Columns in the spreadsheet are

Name
Manufacturer
Type
Status
Model
Serial Number
Asset ID
IP
Description
Owner
User
Site
Department

#Building the JSON request



$assetInfo = @{

    other_asset = @{

        name = $excelData.Name

        description = $excelData.Description

	site = @{

		 name = $excelData.Site

	}

	department = @{

		name = $excelData.Department

	}


	asset_type = @{

		name = $excelData.Type

	}

	status = @{

		name = $excelData.Status

	}

	manufacturer = $excelData.Manufacturer

	ip = $excelData.IP

	model = $excelData.Model

        serial_number = $excelData.'Serial Number'

	user = @{

		email = $excelData.User

	}

	owner = @{

		email = $excelData.User

	}

	custom_fields_values = @{

		custom_fields_value =@{

			name = "MAC Address"

			value = $excelData.Description	


		}

	}


    }

}










# Convert the payload to JSON format

$jsonInfo = $assetInfo | ConvertTo-Json -Depth 4


$jsonInfo




#Submitting the request


$JsonWebToken = "YOUR_WEB_TOKEN"




$Headers = @{ "X-Samanage-Authorization" = "Bearer $JsonWebToken";


              "Accept"                   = "application/vnd.samanage.v2.1+json"


              "Content-Type"             = "application/json" }



$UriBase = "https://api.samanage.com/"

$URI_Part = "other_assets.json"


$URI = $UriBase + $URI_Part 

$URI



$WebResults = @()



try {

	$WebResults += Invoke-RestMethod -Uri ( $URI ) -Headers $Headers -Method POST -Body $jsonInfo -ResponseHeadersVariable ResponseHeaders

} catch {

	Write-Error $_.Exception.Message

	$_.Exception.Response.GetResponseStream() | ForEach-Object { New-Object IO.StreamReader($_) } | ForEach-Object { $_.ReadToEnd() }

}

Find more posts tagged with

Accepted answers

ShadowTech

So an update on this, the script was working its just not displaying because I added it to the CI rather than to the screen, apparently two different items in the system.

So I created the custom field and added it to the Other Assets form, however it didn't display until i created a Dynamic Form Rule. Now on this the only built in system fields i could use are:

Asset Status
Department
Name
Site

So i just utilized the Asset Status and set it's True condition to Not Equals Disposed and then set the action to display the Form and then I set the False condition to also show the form. This gets it showing up and now when I import the data it seems to work.

Just figured i would close the loop on this one.

All comments

jeremymayfield

Since you have the basic asset creation working, the key to hitting those custom fields via the REST API lies in the custom_fields_values array. Custom fields aren't top-level attributes like name or description. Instead, they are nested objects that require the ID or Name of the field to map correctly.

{

"other_asset": {

"name": "Asset Name from Excel",

"asset_tag": "TAG-12345",

"custom_fields_values": [

{

"name": "MAC Address",

"value": "00:1A:2B:3C:4D:5E"

}

]

}

Field Name vs. ID: Using "name": "MAC Address" is easiest, but it is case-sensitive and must match exactly what you typed in the CMDB CI Types setup. If you change the field name later, the script will break. Using the "field_id" is more "permanent" if you can pull it from a GET request first.

The Endpoint: Ensure you are POSTing to: https://api.samanage.com/other_assets.json

Headers: Don't forget to include:

Accept: application/vnd.samanage.v2.1+json
Content-Type: application/json
X-Samanage-Authorization: Bearer [Your_Token]

ShadowTech

Thought i was good with the JSON i had here's a sanitized version

$jsonInfo

{

  "other_asset": {

    "model": "6930",

    "status": {

      "name": "Unlabeled"

    },

    "user": {

      "email": "user@domain.com"

    },

    "asset_type": {

      "name": "IP Phone"

    },

    "department": {

      "name": ""

    },

    "owner": {

      "email": "user@domain.com"

    },

    "site": {

      "name": "Organization Name"

    },

    "ip": "",

    "name": "Mitel - 6930",

    "custom_fields_values": {

      "custom_fields_value": {

        "name": "MAC Address",

        "value": "14:00:E9:08:C1:E1"

      }

    },

    "description": "14:00:E9:08:C1:E1",

    "manufacturer": "MITEL",


  }

}

Now as i have been digging in if i query the configuration items i can pull back the MAC address that i have assigned. So wondering if it has to do with how the Custom Field is added.

I tried to go into custom forms and opened the Other Assets and i added the field there but it does not show up on the assets when i do that. only when i link it to the CI type.

I'm wondering if i will have to do a second loop after i create the asset and then search for where the configuration item which lists the parent_id and then update the custom field there.

Would love to be able to just add the custom field directly to the other assets form but cant figure out how to get that one to work.

jeremymayfield

try this

{
"other_asset": {
"name": "Mitel - 6930",
"model": "6930",
"manufacturer": "MITEL",
"description": "14:00:E9:08:C1:E1",
"asset_type": {
"name": "IP Phone"
},
"status": {
"name": "Unlabeled"
},
"site": {
"name": "Organization Name"
},
"user": {
"email": "user@domain.com"
},
"owner": {
"email": "user@domain.com"
},
"custom_fields_values": [
{
"name": "MAC Address",
"value": "14:00:E9:08:C1:E1"
}
]
}
}

jeremymayfield

The issue you are running into is a classic "gotcha" in SWSD because Other Assets and Configuration Items (CIs) are technically two different layers of the same object.

In your provided JSON, the custom_fields_values is structured as a single object. The SWSD API expects an array (denoted by square brackets []), even if you are only sending one field.

When the API sees an object where it expects an array, it often silently ignores that specific block while still creating the rest of the asset.

You do not need a second loop or a separate CI update if the field is correctly associated with the "Other Asset" CI Type. You just need to wrap the custom field in an array and remove the extra custom_fields_value nesting level.

jeremymayfield

If you change the JSON to the array format [...] and it still doesn't appear, it’s usually a naming mismatch.

ShadowTech

Asset Status
Department
Name
Site

Just figured i would close the loop on this one.