When running a query, why is it not picking up the elements that it should?

  Applies To 
  Product(s): WaterGEMS, WaterCAD, SewerCAD, SewerGEMS, StormCAD, CivilStorm, HAMMER
  Version(s): CONNECT Edition, V8i
  Area:  Other
  Subarea:  N\A


Defect Description

In my model, when running a query on the FCVs it is not picking up the FCVs that it should.

The query is ValveSetting = 0 AND IdahoValveResults_ValveDischarge < InitialSettings_FlowSetting.  There are three valves that should be selected from this query.

In the program, the queries expect that all compatible fields (for purposes of comparison) are set up with the same storage units (cfs, gpm, L/s, etc.).  What is displayed as the unit of measure may not be how it is stored.  An example could be a diameter is displayed in millimeters, but it may be stored in inches.

This is a known issue that has been reported to our developers.  They are working on a way to correct this in a future build of the Water and Storm/Sewer products.

Steps to Reproduce

  1. An example:  User creates a query for flow control valves.  It is set up as
    ValveSetting = 0 AND IdahoValveResults_ValveDischarge < InitialSetting_FlowSetting

  2. When the user runs the query, it is not selecting any valves, but there are three valves that match the criteria.


The problem with this query is that the ValveDischarge and InitialSetting_FlowSetting do not have the same storage units.  Since they are not the same storage units, the user would need to create a user-defined formula field for one of the fields in the query.  In the example used, a UDX-formula field would be created for IdahoValveResults_ValveDischarge.

Create a UDX-formula field like "[IdahoValveResults_ValveDischarge_CFS]"… with Dimension: flow, Storage-Unit: cfs, Numeric Formatter: flow.

Edit the query to look like this:

If, when creating the user-defined formula field, you are not sure what storage unit to use, please contact Bentley Tech Support.


  • Created by
  • When:
  • Last revision by Bentley Colleague
  • When:
  • Revisions: 6
  • Comments: 0