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

I need to add 200+ entries into a custom property pull down...

I need to add 200+ entries into a custom property pull down, is there a was to do this en mass and not individually? Thanks!!!

Find more posts tagged with

Accepted answers

All comments

yaquaholic

Have you seen the Custom Property Import tool?

Settings --> Manage Custom Properties --> import Values. This will allow you to import CPs from CSV, XLS or TXT files (with some examples files to get you going).

yaquaholic

I did have a crack at updating the CustomProperyValues table (in test and dev), but the updated rows did not show up in Orion.

dgsmith80

Hi cwjohnson3rd

You could do this by directly inserting the data into the Database in SQL.

INSERT INTO [dbo].[CustomPropertyValues] ([TargetTable],[Name],[Value]) VALUES ('NodesCustomProperties','Your_CP_Name_Here','Your_Entry_Here')

I have assumed it is a NodesCustomPropery, if that isn't the case then change that part of the command to Interfaces etc.

However, the OrionSDK has an API which lets you create Custom Properties with Values Managing Custom Properties · solarwinds/OrionSDK Wiki · GitHub

yaquaholic

I tried this, but the values did show up in Orion.

Is there a second step required?

dgsmith80

It works fine in my lab, the Custom Property did already exist though. Maybe that's the missing step for you? I was just adding value's to an existing CustomProperty.

yaquaholic

Odd me too, I added a further 4 rows to my Customer CP, but when I went back into Orion (Node edit) the newly added options where nowehere to be seen.

Let me test it further...

cwjohnson3rd

Thanks, I will try this and see what happens

mesverrum

These are all pretty complicated.... you could just remove the limitation, import properties to nodes that need them, then turn the limitation back on and it will automatically include everything that exists on any nodes. I literally just went through this while merging two environments this morning.

dgsmith80

This is the obvious choice, it maybe I misread the original brief I thought OP just wanted to create the options there wasn’t the added criteria to assign them to a set list of nodes but maybe that is the case?

dgsmith80

Sounds like you had a good plan of approach, sometimes automation takes longer than just doing the task manually I guess it depends on how many times you will ever need to perform such a task

Good luck.