Understanding Manage World Map vs Worldwide Map Widget Behavior and Managing Large-Scale Node Placement in the SolarWinds Platform

• Editing options in Manage World Map may appear unavailable due to permission or configuration scope.

• The Worldwide Map widget and Manage World Map operate independently.

• Worldwide Map widgets may auto-populate locations when no filters are applied.

• Changes made at the widget level do not synchronize with global map settings.

• Managing a large number of nodes requires filtering and bulk placement methods rather than manual drag-and-drop.

Resolution

Worldwide Map Widget vs Manage World Map Behavior

• The Worldwide Map widget configured on a dashboard operates independently from the global settings under
  Settings → All Settings → Manage World Map.

• Filters or layout changes applied within a widget affect only that widget instance.

• Global map settings do not automatically synchronize with widget-level configurations.

• This behavior is expected and by design.

Filtering in Manage World Map

• The global Manage World Map view supports filtering of nodes and groups.

• Use the Group and Nodes filter fields to apply SWQL (SolarWinds Query Language) filters.

• Filters allow the map to display only specific nodes or groups without manually searching.

• This approach is recommended when managing large environments.

Using Node Lists and SQL Filters for Targeted Views

• The SolarWinds Platform Web Console supports customizable node lists for views and classic dashboards.

• Node lists can be filtered using text, IP ranges, or SQL queries, allowing precise control over which nodes are displayed.

To create and filter a node list:

1. Open the target view or classic dashboard and click the pencil (Edit) icon.

2. Click Add widgets.

3. Search for All Nodes – Table.

4. Drag and drop the widget onto the page.

5. Click Done adding widgets, then Done editing.

6. Click Edit on the widget.

Filter options:

• Use the Filter Text field:

  • Enter Home to list nodes containing Home in the node name or location.

  • Enter 192.168.1.* to list nodes in the 192.168.1.0–255 IP range.

• Select the appropriate property:

  • Node Name or Location for text-based filters.

  • IP Address for IP range filtering.

• To apply advanced filtering, enter a query in the Filter Nodes (SQL) field.

Important notes:

• Node list widgets sort nodes alphabetically by default.

• This behavior cannot be overridden using SQL.

• Including ORDER BY clauses in SQL filters will result in Custom SQL filter formatting errors.

7. Click Submit to apply the configuration.

Bulk Additions and Removals

• Manual drag-and-drop is available but not efficient for large numbers of nodes.

• Bulk placement can be achieved by:

  • Using Place nodes on the map manually

  • Leveraging grouping and search tools to select multiple nodes

  • Placing them into a new or existing map location

• Bulk removal can be performed by:

  • Removing all nodes associated with a specific location

  • Deleting the location entirely from the map

Automatic Placement Using Custom Properties

• Nodes can be automatically placed on the Worldwide Map using the Latitude (World Map) and Longitude (World Map) custom properties.

• Nodes with valid coordinate values are placed on the map automatically.

Efficient bulk workflow:

• Export node custom properties to CSV.

• Populate or correct latitude and longitude values.

• Import the CSV back into the Latitude (World Map) and Longitude (World Map) properties.

• The map updates automatically.
  
  For more information, you can refer to these documents:  Place objects into the Worldwide Map using custom properties in the SolarWinds Platform  and Display the Worldwide Map in the SolarWinds Platform and Widget configuration examples in the SolarWinds Platform 
  
  Please note: By default, node list resources are designed to sort nodes alphabetically by node caption. This configuration cannot be overwritten using a SQL filter, so ORDER BY clauses included in SQL filters are redundant and will result in Custom SQL filter formatting errors.