> For the complete documentation index, see [llms.txt](https://docs.silverband.com.au/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silverband.com.au/home/paradigm-knowledge-base/generating-reports/workflows/introduction-to-report-builder/basic-comparison-operators.md).

# Basic Comparison Operators

## **Overview** <a href="#equals" id="equals"></a>

Generating a report using Report Builder can overwhelm you with lots of data if the results are not filtered out as you intend them to. Building reports in Report Builder allows you to use comparison operators to help you with sifting the right data or information that you need to meet your report requirements.&#x20;

An example would be using a [Course Enrolment Base Report](/home/paradigm-knowledge-base/generating-reports/workflows/introduction-to-report-builder/base-reports.md#student-course-enrolment-details) limiting the results to a specific start date, only students who are enrolled on a specific Course, and only output records that are "Enrolled", etc. Generating a report with these filters will make a significant difference in the number of results found in your output file. The speed of generating it is also noticeably faster.

<img src="/files/ATTwPbcnyGoSRHBl3Ydz" alt="Difference between generating a report WITH or WITHOUT Filters" class="gitbook-drawing">

How to do it in Paradigm using the Report Builder menu?

After you have selected your Base Report, to further narrow down your output information - specific to what you only need to see on your report, you can add filter clauses using some of the basic comparison operators below. The following can be added under the **Set Filter Clauses** tab \[FILTER CLAUSES section] in building your report, *see* [Step 4 - Add Filter Clauses](/home/paradigm-knowledge-base/generating-reports/workflows/build-a-report/step-4-add-filter-clauses.md) for more details on the workflow.

<figure><img src="/files/mU8h6kbO0giq4IzursVd" alt=""><figcaption><p>Example Basic Comparison Operators in the <strong>Inclusive</strong> category used in Report Builder</p></figcaption></figure>

The Comparison Operators are used to determine if the two values (in the above screenshot - in Report Builder, the **Column Name** \[second column]column and the **Value** column \[fourth column])that you used are the same or not.&#x20;

The **Column Name** section is where you can choose the field name that you are going to compare. The fields that you can see in the dropdown are the fields that are made available based on the Base or Saved report that you have loaded, *see* [Step 1 - Select a Base Report](/home/paradigm-knowledge-base/generating-reports/workflows/build-a-report/step-1-select-a-base-report.md).

The **Operator** column \[first and third columns] is where you need to choose your intended operator - depending on how you are going to compare the field you have selected in the second column. The operators are categorised into three:&#x20;

* **Inclusive** - operators to use that will include results within a range of values
* **Exclusive** - operators to use that will include results outside a range of values
* **Advanced** - operators to compare two fields, *see* [Complex Comparison Operators](/home/paradigm-knowledge-base/generating-reports/workflows/advanced-report-builder/complex-comparison-operators.md) page

Refer to the description and examples below for each basic comparison operator under the **Inclusive** and **Exclusive** categories that you can use.&#x20;

The **Value** column (fourth column) is where you enter the value that you would want to compare against the field that you have selected in the second column (**Column Name** section).

To understand better how the filter clause interacts with each other, check each basic comparison operator below and the examples of when and how you can use them in your report:

## **Inclusive Comparison Operators**

### **Equals to the value (=)** <a href="#equals" id="equals"></a>

For this operator, the data within the column name has to be an exact match.

**Example 1**

> “Postal Code” = 3153 (only records with the exact match (3153) will be returned in the data set)

<figure><img src="/files/wzY33D9FWVRRhN5nGLK7" alt=""><figcaption></figcaption></figure>

**Example 2**

> “Course Accredited” = YES (only records with the exact match (YES) will be returned in the data set)

<figure><img src="/files/cJNFJvNpYLsuKQqrR5Ie" alt=""><figcaption></figcaption></figure>

### **Greater than the value (>)** <a href="#greater-than-greater-than" id="greater-than-greater-than"></a>

Normally used for numeric values like date and credit points. Return values greater than what has been set.

**Example 1**

> “Start Date” Greater Than (>) 2020-01-01 (values returned will start after 2020-01-01)

<figure><img src="/files/fWwp2Y5JtbJePq2a9WuS" alt=""><figcaption></figcaption></figure>

### **Greater than or equal to the value (>=)** <a href="#greater-than-equal-to-greater-than" id="greater-than-equal-to-greater-than"></a>

Normally used for numeric values like date and credit points. Return values greater than and equal to what has been set.

**Example 1**

> “Start Date” Greater Than Equal To (>=) 2020-01-01 (values returned will start from 2020-01-01)

<figure><img src="/files/IXKvbb27RVuS6Q4jwci2" alt=""><figcaption></figcaption></figure>

### **Less than the value (<)** <a href="#less-than-less-than" id="less-than-less-than"></a>

Normally used for numeric values like date and credit points. Return values less than what has been set.

**Example 1**

> “Start Date” Less Than (<) 2020-01-01 (values returned before 2020-01-01)

<figure><img src="/files/cBadUsBKJXWDoWLLgjdY" alt=""><figcaption></figcaption></figure>

### **Less than or equal to the value (<=)** <a href="#less-than-equal-to-less-than" id="less-than-equal-to-less-than"></a>

Normally used for numeric values like date and credit points. Return values less than and equal to what has been set.

**Example 1**

> “Start Date” Less Than Equal To (<=) 2020-01-01 (values returned on or before 2020-01-01)

<figure><img src="/files/gEpdb548nMEcD5IYJUB1" alt=""><figcaption></figcaption></figure>

### **Contains the value (ilike)** <a href="#less-than-equal-to-less-than" id="less-than-equal-to-less-than"></a>

Like is a wildcard value. This will return values that contain a pattern match (partial keyword matching) with the same character combination regardless of the case as set in the value.

**Example 1**

> “First Name” Like **Br** (will return **Br**ianna, **Br**ian, **Br**idget) and also (**br**ian, **br**ianna, **br**idget)

<figure><img src="/files/N1DHzocVIiA5cVEe2vKU" alt=""><figcaption></figcaption></figure>

**Example 2**

> “UnitCode” Like **ACC** (will return all unit codes with “**ACC**” keyword, like **ACC**OUNTING 101, **Acc**101, etc.)

<figure><img src="/files/V5Kims3PxnCNtjDZKp4w" alt=""><figcaption></figcaption></figure>

### **Contains the case sensitive value (like)** <a href="#less-than-equal-to-less-than" id="less-than-equal-to-less-than"></a>

If you want a LIKE Operator which would mind the case on how the data are coded and that it contains/matches the exact case typed in the value set, then use this operator. This will return values that contain a pattern match (partial keyword matching) depending on the letter case.

**Example 1**

> “First Name” Like **Br** (will return **Br**ianna, **Br**ian, **Br**idget) but not (**br**ian, **br**ianna, **br**idget)

<figure><img src="/files/5ri802gFem5eafWedKbk" alt=""><figcaption></figcaption></figure>

**Example 2**

> “UnitCode” Like **ACC** (will return all unit codes with “**ACC**” keyword, like **ACC**OUNTING101, etc. but not "**Acc**ounting101" - as long as the value is not in the same letter case)

<figure><img src="/files/iHMDeas8lUr1SvxKAqvp" alt=""><figcaption></figcaption></figure>

### **Contains any of the following options (in)** <a href="#in" id="in"></a>

IN is normally used when selecting predefined options from the drop-down box. You can also multi-select the values which you would want to be included in your clause.

**NOTE**: In Paradigm, fields that are designed to have the select values will appear automatically when you use this operator, e.g. Course Id.

**Example 1**

> “Course Id” In "Bachelor of Accounting" (all records with a Course Id of “Bachelor of Accounting” will be returned)

<figure><img src="/files/Y58pTCJMmhORj9Pp1EmW" alt=""><figcaption></figcaption></figure>

**Example 2**

> “Course Enrolment Status Id” In "Enrolled" , "Withdrawn", "Credited/RPL" (all records with an “Enrolled”, "Withdrawn", "Credited/RPL" Course Enrolment Status Id will be returned)

<figure><img src="/files/UkzKUEpU3l1xNdIcZTVy" alt=""><figcaption></figcaption></figure>

### **Is not empty (not null)** <a href="#not-in" id="not-in"></a>

Checks the field or value if it is not blank - returns true if the field has not been left bank during record creation. Fields with zero value or that contain spaces are considered "NOT NULL"

**Example 1**

> “Email” Is NOT NULL (returns a value if the field "Email" has been entered a value during record creation)

<figure><img src="/files/M9LUkwd4vPG7o6PK8H1d" alt=""><figcaption></figcaption></figure>

**Example 2**

> “Invoice Id” IS NOT NULL (will return true if the field is NOT NULL, else false)

<figure><img src="/files/6N3NrdH4xfzLO3k67cpZ" alt=""><figcaption></figcaption></figure>

## Exclusive Comparison Operators

### **Not equal to (!=)** <a href="#not-equal" id="not-equal"></a>

For this operator, the data within the column name can not be an exact match.&#x20;

**Example 1**

> “Postal Code” Not Equal ! = 3153 (records with every postcode OTHER than 3153 will be returned)

<figure><img src="/files/QU1GMrqzUxoDaVinDRIn" alt=""><figcaption></figcaption></figure>

### **Does not contain (not ilike)** <a href="#not-in" id="not-in"></a>

Like is a wildcard value. Using the NOT ILIKE operator will return values that do not contain a pattern match (partial keyword matching) with the same character combination regardless of the case as set in the value.

**Example 1**

> “First Name” Not ILike **Br** (will not return **Br**ianna, **Br**ian, **Br**idget) and (**br**ian, **br**ianna, **br**idget) or anything that has the "**Br**" character combination

<figure><img src="/files/QptL9agDNiBkGYgUoBuC" alt=""><figcaption></figcaption></figure>

**Example 2**

> “UnitCode” Not ILike **ACC** (will not return unit codes with “**ACC**” keyword, like **ACC**OUNTING 101, **Acc**ounting101, etc.)

<figure><img src="/files/UPvBpLQAYFEm9GcG9Fbb" alt=""><figcaption></figcaption></figure>

### **Does not contain the case sensitive value (not like)** <a href="#not-in" id="not-in"></a>

If you want a NOT LIKE Operator which would mind the case on how the data are coded and that it contains/matches the exact case typed in the value set, then use this operator. This will return values that contain a pattern match (partial keyword matching) depending on the letter case.

**Example 1**

> “First Name” Not Like **Br** (will not return **Br**ianna, **Br**ian, **Br**idget) but will still return (**br**ian, **br**ianna, **br**idget)

<figure><img src="/files/dUjl80Suckh6Wob7sZCU" alt=""><figcaption></figcaption></figure>

**Example 2**

> “UnitCode” Like **ACC** (will not return all unit codes with “**ACC**” keyword, like **ACC**OUNTING101, etc. but will still return "**Acc**ounting101" - as long as the value is not in the same letter case)

<figure><img src="/files/S087loMbe8xnQwrYPVpe" alt=""><figcaption></figcaption></figure>

### **Does not contain any of the following options (not in)** <a href="#not-in" id="not-in"></a>

NOT IN is normally used when selecting predefined options from the drop-down box, and it will choose which of the predefined options should be specifically excluded from the results. You can also multi-select the values which you would want to be included in your clause.

**NOTE**: In Paradigm, fields that are designed to have the select values will appear automatically when you use this operator, e.g. Course Id.

**Example 1**

> “Course Id” Not In "Bachelor of Accounting" (all records with a Course Id “Bachelor of Accounting” will not be returned)

<figure><img src="/files/yDLskJCpB6w1PEk1Y95p" alt=""><figcaption></figcaption></figure>

**Example 2**

> “Enrolment Status Id” Not In "Applied", "Deferred", "Audit" (all records with enrolment status of  "Applied", "Deferred", "Audit" will not be returned)

<figure><img src="/files/meZSA6diXWR8ax3v5v7x" alt=""><figcaption></figcaption></figure>

### Is empty (null)

Checks the field or value if it is blank - returns true if the field has been left bank during record creation. Fields with zero value or that contain spaces are not considered "NULL"

**Example 1**

> “Email” Is NULL (returns a value if the field "Email" has been left blank during record creation)

<figure><img src="/files/MhdVFWJQWlU4Sqo2a0Ae" alt=""><figcaption></figcaption></figure>

**Example 2**

> “Grade Description ” IS NULL (will return true if the field is NULL, else false)

<figure><img src="/files/h98Lc5fqRr9dVldxL2H0" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.silverband.com.au/home/paradigm-knowledge-base/generating-reports/workflows/introduction-to-report-builder/basic-comparison-operators.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
