Observability

Custom Properties Containing ID Do Not Appear in Maps Content Picker in the SolarWinds Platform

This article provides information about an issue where node custom properties whose names contain ID do not appear in Maps > select node > TEXT > Content (+) in SolarWinds Platform / SolarWinds Observability Self-Hosted, even when the custom property is assigned and has a value on the node.

First published date

5/12/2026 4:19 PM

Last published date

5/12/2026 4:19 PM

Overview

In affected environments, users may try to display a node custom property in an Intelligent Map label by selecting the node and navigating to TEXT > Content (+). The expected custom property is not returned in the content picker, which prevents the property from being inserted into the map text.

 

This issue is not limited to a single custom property name. Any custom property whose name contains ID may be affected, including different case variations such as:

  • ID
  • Id
  • iD
  • id

 

Example affected custom property names may include:

  • Device_ID
  • DeviceId
  • ManagementID

 

The behavior can vary slightly. In some environments, only the custom property containing ID is missing. In other cases, because of how the list is filtered and ordered, it may appear that additional custom properties created after the affected one are also missing from the Maps content list.

 

Example reproduction scenario

  1. Create and assign a node custom property that does not contain ID, such as Test.
  2. Add the node to a map.
  3. Open TEXT > Content (+) and confirm that the custom property appears.
  4. Create and assign a custom property whose name contains ID, such as Device_ID.
  5. Return to Maps and check TEXT > Content (+) again.
  6. Observe that the custom property containing ID is missing from the list.

Product section

Hybrid Cloud Observability

Cause

This issue is caused by a product defect affecting the Maps content picker logic in SolarWinds Platform.

Based on internal investigation, custom property names containing ID are being filtered out by the backend query used to populate the Maps > TEXT > Content list. As a result, affected custom properties are not displayed even though they exist, are assigned correctly, and contain values.

Resolution

Use custom property names that do not contain ID as a temporary workaround until a permanent fix is available.

 

Workaround steps

  1. Identify any custom property used in Maps whose name contains ID.
  2. Create a replacement custom property with a name that does not contain ID.
  3. Populate the new custom property with the same values as the affected property.
  4. Open Maps > select node > TEXT > Content (+).
  5. Verify that the replacement custom property now appears in the content picker.
  6. If confirmed, update operational use of the old property as needed.

 

Additional workaround actions

If the issue still occurs after recreating the custom property without ID in the name:

  1. Restart the Orion Module Engine service.
  2. Restart the SolarWinds Information Service V3.

 

Important notes

  • The current recommendation is only to avoid using ID in the custom property name until the fix is released.
  • Before making broad production changes to custom properties, take a full backup of the SolarWinds database as a best-practice precaution.
  • If the affected custom property is referenced by alerts, reports, groups, or other workflows, validate dependencies before removing or retiring it.