Comparison of large and small fields

Summary

In Dos, in Criteria Aggregations such as [Calculate Field Average Values for Destination Table Rows that Meet Criteria] (../../actions/aggregate/calc_subtable_averageif_v2/), and Criteria for Comparing Field Values such as [If Field Values are Specific] (../../conditions/condition_field/field_value_condition/), you may want to make small or large comparisons between field values and values specified in parameters.

Here are the rules for comparing large and small in Customine. See Here: for information on determining equal or not equal.

The “large-small comparison” parameters are as follows:

  • Large (>)
  • Greater than or equal to (>=)
  • Small (<)
  • Less than or equal to (<=)

Field Types Supporting Large and Small Comparisons

  • Text
  • Number
  • Calculated
  • Date
  • Time
  • Date and time
  • Created datetime
  • Updated datetime
  • Record number

If you try to compare large or small on any other field type, you will receive an error when performing the customization.

Text Field

If both the field value and the comparison value entered as a parameter are numbers, they are compared as numbers; otherwise, they are compared in lexicographic order as strings.

Number Field

Compare both the field value and the comparison value entered as a parameter as a number.

Calculated Field

Calculated fields can include not only numerical values but also dates and times.

If the Calculated field value is a number, the comparison value entered as a parameter will be treated as a number if both are numbers. Otherwise, it will be compared as a string in lexicographic order.

If the Calculated field value is date or time, compare it as a string, in lexicographic order. The caveats in that case are the same as for Date fields, etc.

Date field

Time field

Date and time field

Created datetime field

Updated datetime field

Compare in lexicographic order as a string.

Note the format of the comparison value you enter as a parameter as it compares to a string. For example, specifying a Date as “4/1/2019” separated by a slash will not produce the intended result.

Datetimes should be extra careful and specified in Coordinated Universal Time, not Japan Standard Time.

Field type Input Format Example
Date YYYY-MM-DD 2019-04-01
Time HH:MM 06:30
Date and time YYYY-MM-DD’T’HH:MM:SS’Z' (Coordinated Universal Time) 2019-03-31T21:30:00Z

Record number

Compare Record numbers as numbers.

Even if the Record number has an App code, the App code part is ignored and only the Number part is compared.