Has this feature request been addressed in the 10.3 update? Haven't had a chance to upgrade yet but didn't notice any mention of it in the release notes. I'd hate to have to wait another few months or longer for this essential improvement.

As far as i can tell, it has not. I have the 10.3 RC running and it is not resolved there. I think someone from SW mentioned in another thread that it hadn't been addressed in 10.3 but maybe in a near future release.

I know, to be honest we always found highest priority tasks to implement through previous versions. But, because similar thing is being discussed here: http://thwack.solarwinds.com/message/171233#171233 . We are going to reconsider this request and increase priority of this feature. Hopefully I'll have a good news for you soon. And sorry for waiting on this so long.

I second this request.Since we use custom properties to group devices using the Ajax node view, any typos, leading or lagging spaces or uppercase/lowercase differences results in new groups showing up in this view.

Also create a limitation that only allows the user to select from an existing custom property when adding or editing nodes.

Also create a limitation that only allows the user to select from an existing custom property when adding or editing nodes.

This would have to be done correctly because what if you really did have to add a "new" value to the custom property. Maybe making it so that web edits can not add "new" values, but to do so you would need to go to System Custom Property Application to add it for the first time. I think its good just need to take a few things into consideration.

Consider it for future relase? This should have been standard in the original produsct... Also I have some true/false custom properties and was amazed (in a bad way) to find that I didn't have a check box. I have to actually type "True" or "False" in there. Seriously?

Little things like this during the eval make me feel less at ease recomending this product for purchase.

Add another name to the list. When I first saw the custom property implementation for web node management, I thought this was coming soon because it was so obvious. There needs to be a checkbox for true/false values and a list/combo box for text based values.

SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community.
More than 150,000 members are here to solve problems, share technology and best practices, and directly
contribute to our product development process.
Learn more today by joining now.