Network Management

Custom filters in widgets stop working

See the most common issues related to widgets migrated from SQL to SWQL and learn how to correct filter syntax in the widgets.

First published date

10/19/2021 7:10 AM

Last published date

5/15/2025 3:28 PM

Overview


When you encounter the "Custom SWIS filter incorrectly formatted" message in your widgets, review the resolution.

The message might be displayed in the following widgets:
  • Top XX Wireless APs by Clients Count
  • Top XX Wireless Clients by Traffic
  • Top XX Errors & Discards This Hour
  • Top XX Errors & Discards Today
  • Top XX Interfaces by Percent Utilization
  • Top XX Interfaces by Relative Multicast Packet Rate
  • Top XX Interfaces by Traffic
  • High Errors & Discards Today
  • Percent Utilization of All Interfaces
  • Current Traffic on All Interfaces
  • Interfaces with High Percent Usage (no paging)
  • Down Interfaces
  • Total Interfaces By Type
  • Total Nodes By OS

Product section

Orion Platform

Cause

Widgets were migrated to SWQL.

Resolution


All migrated widgets

If custom filters used in the migrated widgets contain an SQL function that does not have an SWQL counterpart, you need to rewrite the filters not to use the function. 
See Use SolarWinds Query Language (SWQL) in the Orion Platform for details.


Interfaces widgets

If the filter uses custom properties that are common to both Nodes and Interfaces, the properties have to be distinguished by a prefix. The prefix changed as follows:
 
 New PrefixOriginal Prefix
NodesNodesCustomProperties.Nodes.
InterfacesInterfacesCustomProperties.Interfaces.


Example

In this example, assume both nodes and interfaces have custom property A.
Original filter: Nodes.A = 5 OR Interfaces.A = 5
New filter: NodesCustomProperties.A = 5 OR InterfacesCustomProperties.A = 5


Top XX Wireless Clients By Traffic widgets

If the filter contains properties of Wireless Clients, these might not work anymore. To find which properties can be used, see the SWIS entity Orion.Wireless.Clients. If a property is the same for both nodes and wireless clients, prefix the property name with Clients.


Example

Original filter: Client_TotalBytesRx > 100 AND Client_Name LIKE '%client%'
New filter: InTotalBytes > 100 AND Clients.Name LIKE '%client%'


Top XX Wireless APs by Clients Count

If the filter contains properties of Wireless APs, these might not work anymore. To find which properties can be used, see SWIS entity Orion.Packages.Wireless.AccessPoints. 
If a property is the same for both nodes and wireless access points, prefix the property name with APs.

Example

Original filter: AP_TotalBytesTxPerSec > 20 OR AP_Name LIKE '%GF%'
New filter: OutBps > 20 OR APs.DisplayName LIKE '%GF%'