Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 13

NPM 10.4.1 Custom Properties Possible Bug or Just Weirdness

Hi Fellow Thwack-ziens!

I am working with a customer who is on the latest NPM 10.4.1.  We are seeing some strangeness in the custom property editor and I wanted to see if others are experiencing the same thing.  We have a need to populate 22 different custom properties for the nodes we will be monitoring.  We are trying to keep these custom properties in order to that when the provisioning folks add devices to Orion, it makes their process more logical and simpler.

In order to ensure the custom properties are in the order we want, I have prepended a number in front of the custom property name.  It looks like this:




Once I hit submit when creating the property, the custom property name gets changed to:



I checked the Nodes table in the DB and it sure does have the leading underscore.  This is not a huge deal, but does detract from the overall cleanliness/origanization of ther environment.  I am assuming it is this way due to some MS SQL limitation not allowing table column names to start with a number.

So, the questions I have are:

1. Is this a bug?  I see the CustomPropertiesMetadata table where I can change the name and it does reflect that in the web console.  Any changes here does break a number of things though so this is not something which I can do in a customer environment.

2. Is there any other method to force the order of the custom properties with something other than the default of aplhabetical ascending?


Sohail Bhamani

Loop1 Systems

Labels (1)
0 Kudos
5 Replies
Level 14


This may or may not be related, but I just opened a post on some strange-ness after an upgrade.


0 Kudos

Wow you had to jump through some hoops for that one.  Turns out for me, it is just a MS limitation.  No big deal.  Thanks for the info though.

Sohail Bhamani

Loop1 Systems

0 Kudos
Level 11

At least for 10.3 , this occurs if you use a number at the start of a custom property name. Just make it CP01_aaa CP02_aaa, and so forth.

If you only care about the order you see them in a page view, you can also create a custom HTML resource (Misc->custom HTML) that populates them in whatever order by linking them directly.

Just write ${VariableName} to display the variable, <br> for a line break, + other html code to create your own custom textbox.

This is definitely a limitation in MS SQL server's column naming and not anything to do with SW.  What zzz has mentioned is a great work around.  Thanks!

Sohail Bhamani

Loop1 Systems

0 Kudos
Level 14

Good post Sohail.  I would like to know this too.

0 Kudos