Basic queries

This table shows basic queries and their corresponding regular expressions:

Query Code
<Filed Name>=value
(\r)?+Segment\|([^\|]*\|){Index-1}+[^\|]*value
Not <Segment>.<Index>=value. This indicates the carriage return displays once or not at all before a segment.
 indicates the carriage return could(\r)?+Segment\|([^\|]*\|){Index-1}+(?!value)
<Segment>.<Index>=value
(\r)?+Segment\|([^\|]*\|){Index-1}+[^\|]*value
<Field Alias>=value
(\r)?+Segment\|([^\|]*\|){Index-1}+[^\|]*value
<Subfield Alias>=value
(\r)?+Segment\|([^\|]*\|){Index-1}+([^\\^]*\\^){SubIndex-1}+value

In these queries:

  • (\r)?+Segment\| matches the specified segments in a message.
  • (\r)?+
  • ([^\|]*\|){Index-1}+ specifies how many fields should be passed through before reaching the specified field.
  • Index indicates the field index.
  • [^\|]*value attempts to match a field value. A field consists of several subfields. To support wildcard matching, [^\|]* is added before the value..
  • (?!value) introduces a zero-width negative lookahead to represent the logic NOT.
  • ([^\\^]*\\^){SubIndex-1}+value matches the specified subfield.
  • ([^\\^]*\\^){SubIndex-1}+ specifies how many subfields should be gone through before reaching that subfield.
  • The | and ^ characters are the default delimiters of fields and subfields. They are replaced with the real delimiters in runtime if the messages are using the other delimiters.