Business support

Understanding Condition Builder concepts

When you use Condition Builder to create filters in Bill Analyst and Usage Analyst, you'll have greater success narrowing the scope of your reports and zeroing in on important data trends by understanding the important concepts.

Even the simplest filters require at least one condition. Conditions are built using three components: reporting fields, comparison operators, and values.
 

  • Reporting field—a piece of data (e.g., account number, duration, originating city)

  • Comparison operator—how the relationship between the reporting field and value will be tested (e.g., contains, is equal to)

  • Value—what the reporting field is being compared to

With these three components, you can build a condition. Examples include: "Call area does not contain 303" or "Day of month is equal to October."

From the first list, you can select And or Or to improve the quality of the results that are returned to you.

Basic rules to keep in mind:
 

  • Condition rows must precede any nested groups in the same group.
  • Rows with the same indentation roll up to the nearest operator that is above and indented one level less.
  • The row following a group row must be indented one more level than the group row.
  • Rows may be added and removed between one another to change the row order.
  • The last row cannot be a group row because it would not contain any conditions.

Additional tips:
 

  • The first row of the filter (group row) cannot be deleted.
  • All rows—except for the first row—may be indented or outdented.
  • Rows below groups are outdented.
  • You cannot move rows up and down.
  • The last row cannot be a group.
  • Each group needs a condition.
  • Click the minus sign (-) to delete a row.
  • Each row is moved individually.
  • Up to five levels of indentation are possible.
  • Filters can have up to 50 rows.
Not quite right?

Check out these other, popular search topics: