Manual Editing of Node Details

We already make substantial use of custom properties, however editing configs on production hardware to get location data is silly. Especially when dealing with active in use hardware. 

Given that neither the node details nor custom properties minimize within a page or hide blank fields you're asking everyone to add a large widget rather than edit. 

On top of that not every device supports all of the fields listed so the argument of "fix it on the device" isn't a realistic answer. Couple that with some networks having thousands of endpoints to edit the config and then verify in Orion would take days to tackle, or given that it's 2020 and monitoring is supposed to be a tool to aid in our work it's better to let us manually edit whatever fields we'd like. If you don't want it, don't use it.

I agree with using custom properties.. I use the heck out of them.. Here a Sample of some of them..

Then you can easily create views on Region or Country, etc..

Custom properties are your friend in solarwinds.. 

Ken

cnorborg has the same answer I would have offered.  You might be thinking in reverse of what's most efficient to leverage SW's capabilities.

I actually disagree with this.   "Node Details" is giving you details about what it downloaded from the node, such as the SNMP location, SNMP contact, the IOS version, # of CPU's, etc.   If you want to change something about it, go to the node and change it and SW will download this information again.   If you edited the # of CPU's in "Node Details", it wouldn't actually change the # of CPU's on the box, would it?

The other thing about this is, if you utilize this information, you are distributing the ability to update the information to those that manage the boxes.   Those folks might not be need the ability to manage things in Orion otherwise, so why give them permissions they otherwise don't need?

Plus this is exactly why Custom Properties was made, if you want this information updated manually in your Orion database, make it a custom property and update it there.   Things like Auto Geolocation will use custom properties as well as SNMP location, so you're not really gaining much by making it a custom property, and if you wanted, you can auto-set the custom property based on what is in the SNMP location field also quite easily...