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

Define default custom property value for drop-down list

In NPM 11.5 with recent addition of Mandatory Custom Properties when you have mandatory drop-down list - the value of this property for new nodes will default to the first one on the list - which is not good. It is in alphabetic order, but by no means the first one is the one I want to have default to all my new nodes.

It would be great to specify which one should be set to default value. If default value is not specified - it should default to "none" for both Mandatory and non-mandatory proeprties, although when clicking on submit - the error should pop-up for mandatory properties.

Thank you,

Alex

Find more posts tagged with

Status: None

Comments

AlexSoul

ok, after a bit of testing unfortunately this limitation has stopped me from using mandatory custom properties for drop down list - I better deal with nodes which have null values separately with the help of reporting, rather then have them all incorreclty tagged with first option in drop down list. Hope this will be noticed soon by product team

clubjuggle

DanielleH‌, can this be moved to NPM Feature Requests? Thanks!

AlexSoul

clubjuggle‌, sorry, I obviously posted in wrong area, Please feel free to move. Thank you

clubjuggle

No worries! I just want to make sure it gets the visibility it needs.

wluther

alexslv I have just been adding "A" as an option, and then I build my reports and alerts to fire off when "A" is detected as the value. It really would be nice to be able to either manually arrange the choices, or at least set the default value to "Choose One", and then not let the person add the node until an actual value is selected.

I would really like to have nested/cascading drop downs too. I think it would really make things much more clean, only seeing specific properties, and not having to see all of them.

i_like_eggs

I ran in to this exact problem today, Where one CP updates another But the default value keeps change my other CP lol. would be nice to just be able to disable this default behaviour in the website settings

wluther

I had much better luck with this by adding the "-" character to the list. It places it at the top, and seems to force the mandatory property to function as intended, by forcing the user to change the value.