Optimizing Row Filters - EcoSys - Help - Hexagon

EcoSys Performance Tuning

Search by Category
EcoSys Version

Related Object Row Filters

Whenever it is possible to apply a row filter to an attribute field instead of a related object field, always use the attribute field. This ensures filtering is done by the database and before any objects are loaded into memory.

Equals Selection, Does not Equal Selection Row Filters

The Equals Selection and Does not Equal selection row filters are the most efficient of all row filter operators. When possible, use these instead of Equals, Not Equals, Contains, etc.

Applying Or-Logic

Using the “Or-Logic” option when applying row filters can slow performance down dramatically. Use only when necessary.

Row Filtering Precedence

Some row filters are more efficient than others. The following list shows field types in the order of most efficient to least efficient:


Row Filtering Precedent by Column Type

Therefore, if possible, try to filter on the more efficient field types. Even if a filter on a less efficient field type will yield the data you need, if you can also apply a filter on a more efficient field type, the process will run faster and with less load on the system.

Displaying Related Objects vs. Attributes

Related Object fields are always more time and resource consuming than Attribute fields. When possible, use the Attribute fields instead of related objects.

The ID and Name fields for most related objects can be found in the Attribute section, so if you only need ID or Name, use it from Attributes and not from Related Objects.