---
title: "DSL Query Based Prefilling and Filtering"
slug: "dsl-query-based-prefilling-and-filtering"
updated: 2026-02-02T08:09:32Z
published: 2026-02-02T08:09:32Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.encodify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# DSL Query Based Prefilling and Filtering

## Example Business Case

---

**Scenario 1**

**Applicable when fields: Start Date and End date is within months 03 to 08 (both included) and the Year is the same for both fields.**

1. E.g. Start Date 1/3/2019 and End Date 28/5/2019.
2. System should automatically calculate the year and season as 2019, ‘Spring/Summer’.

**Scenario 2**

**Applicable when fields: Start Date and End date is within months 09 to 02 (both included) year 2019-2020**

1. E.g. Start Date 20/10/2019 and End Date 15/01/2020.
2. System should automatically calculate the year and the season as 2019, ‘Autumn/Winter’.

**Scenario 3**

**Applicable when fields: Start Date and End Date falls between scenario 1 and scenario 2.**

1. E.g. Start Date 1/12/2019 and End Date 1/03/2020.
2. User should be able to set the season and the year themselves - no season prefilling should take place.

**Scenario 4**

For specific company (e.g. Company = "Company_1"), their year goes from January to December, as opposite to March-February in scenarios 1, 2 or 3.

### Data Model

---

![EBMS_20952_data_model.png](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/ebms_20952_data_model.png)

### Query Examples

---

**QUERY for Season field default values in module Campaigns:**

```plaintext
Select * from MODULE_NAME_Seasons FD
inner join MODULE_NAME_SeasonCombinations sc on sc.FD_Name_Season = FD.id
WHERE sc.FD_4168 <= :currentItem_FD_1984
AND sc.FD_4169 >= :currentItem_FD_1984
AND sc.FD_4169 >= :currentItem_FD_1985
```

Where:

- sc.FD_4168 is a Start Date field in module Season Combinations
- sc.FD_4168 is an End Date field in module Season Combinations
- :currentItem_FD_1984 is a Start Date field in module Campaigns
- :currentItem_FD_1985 is a Start Date field in module Campaigns

**QUERY for Season Field filtering in module Campaigns:**

This configuration is required to filter the season by the company

```plaintext
Select * from MODULE_NAME_Seasons FD
inner join MODULE_NAME_SeasonCombinations sc on sc.FD_Name_Season = FD.id
WHERE sc.FD_4172 = :currentItem_FD_2439
```

Where:

- sc.FD_4172 is Company module link field in Season Combinations module
- :currentItem_FD_2439 is Company module link field in Campaigns module

**QUERY for Season Field filtering in module Campaigns not allowing to select other season values excpet those that matches prefilling rule:**

This configuration is required to filter the season by the company

```plaintext
Select * from MODULE_NAME_Seasons FD
inner join MODULE_NAME_SeasonCombinations sc on sc.FD_Name_Season = FD.id
WHERE sc.FD_4172 = :currentItem_FD_2439
AND
( ( sc.FD_4168 <= :currentItem_FD_1984 AND sc.FD_4169 >= :currentItem_FD_1984)
OR ( sc.FD_4168 <= :currentItem_FD_1985 AND sc.FD_4169 >= :currentItem_FD_1985)
OR ( sc.FD_4168 >= :currentItem_FD_1984 AND sc.FD_4169 <= :currentItem_FD_1985)
)
```

Where:

- sc.FD_4172 is Company module link field in Season Combinations module
- :currentItem_FD_2439 is Company module link field in Campaigns module
- sc.FD_4168 is a Start Date field in module Season Combinations
- sc.FD_4168 is an End Date field in module Season Combinations
- :currentItem_FD_1984 is a Start Date field in module Campaigns
- :currentItem_FD_1985 is a Start Date field in module Campaigns

**QUERY for Year field default values in module Campaigns:**

This configuration is required to extract the year from the Start and End date field values

```plaintext
Select * FROM MODULE_NAME_Year FD WHERE FD.FD_1864 = getYearFromDate(:currentItem_FD_1984)
```

Where:

- FD.FD_1864 is a Year field in the module Year
- getYearFromDate(:currentItem_FD_1984) extraction of the year value from the Start Date field in the Campaigns module.

### Example

---

**Season Combinations module**

![seasonCombinations.png](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/seasoncombinations.png)

**Campaigns module**

**![Screenshot_2020-05-15_at_13.51.35.png](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/screenshot_2020-05-15_at_13.png)**

### **Configuration recommendations and limitations**

---

- Feature is for**NEW UI only**
- For the start/end date the following field types are supported: Date, Date-Time, Month-Year, Week-Year, date calculation fields.
- For the Year field in the Module Year fields of the type Text or Integer are supported.
- Prefilling (also using DSL query) is not supported in item copy and API calls.
- Prefilling will not take place in case value is restricted to a user (e.g by Group or Status settings).
- Following existing prefilling behvaior of the system, in case more than 1 option matches the DSL Query, last option (by ID) will be prefilled.
- Both module/field name and ID can be used in DSL Query. However, IDs are recommended for use to avoid problems with broken queries in case module/field is renamed or contains special characters or spaces.

**Example:**

*Using module name*

```plaintext
Select * from MODULE_NAME_Season FD
```

*Using module ID*

```plaintext
Select * from MODULE_123 FD
```

*Using field name*

```plaintext
WHERE sc.FD_Name_Company
```

*Using field ID*

```plaintext
WHERE sc.FD_123
```