Submit a ticketCall us

Quickly Address Software Vulnerabilities
Patch Manager is an intuitive patch management software which extends the capabilities of WSUS and SCCM to not only patch Windows® servers and workstations, and Microsoft® applications, but also other 3rd-party applications which are commonly exploited by hackers. Learn more about our patch management solution.


Home > Success Center > Network Performance Monitor (NPM) > Columns matching when importing custom properties

Columns matching when importing custom properties

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 32 Votes: 0 Revisions: 8


When importing custom property values from an external spreadsheet, the Custom Property Editor will attempt to logically match column labesl in the spredasheet to corresponding database columns. On the Match Columns view, columns that are read from the spreadsheet to be imported are listed on the right. For each spreadsheet column, select whether the object data should Match with the corresponding object data in the Orion database or Import to the Orion database as corresponding object data.


All NPM versions


For example, a spreadsheet that is a simple list of named nodes with corresponding IP addresses and physical locations would look similar to the following:

Name IP Address City State
Node_1 Austin Texas
Node_2 Austin Texas
Node_3 Austin Texas

On import, the Custom Property Editor would list the following as Spreadsheet Columns:

  • Name
  • IP Address
  • City
  • State

Typically, you will want to match your imported nodes by name and IP address have the rest of the data imported into your SolarWinds database. In this case:

Spreadsheet Column Relationship Orion Database Column
Name matches Caption
IP Address matches IP_Address
City imports to City
State imports to State

Click Import, and the location data (City and State) for each corresponding node, identified by name and IP address, are imported from the spreadsheet into the Orion database.

Last modified
21:54, 22 Jun 2016