---
title: "Lusid.Calendar.Date"
slug: "lusidcalendardate"
tags: ["luminesce ", "provider", "calendars", "copp clark"]
updated: 2024-08-21T10:35:13Z
published: 2024-08-21T10:35:13Z
canonical: "support.lusid.com/lusidcalendardate"
---

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

# Lusid.Calendar.Date

| **Type** | **Read/write** | **Author** | **Availability** |
| --- | --- | --- | --- |
| [Data provider](/v1/docs/what-are-a-data-provider-and-a-direct-provider) | Read | Finbourne | Provided with LUSID |

The `Lusid.Calendar.Date` provider enables you to write a [Luminesce SQL query](/v1/docs/understanding-the-luminesce-sql-query-syntax) that retrieves information about dates in your [calendars](/v1/docs/using-calendars-in-lusid).

> **Note:** The LUSID user running the query must have sufficient [access control permissions](/v1/docs/creating-policies-to-control-access-to-providers-for-different-luminesce-end-users) to both use the provider *and* read calendar data stored in LUSID. This should automatically be the case if you are the domain owner.

**See also**: [Lusid.Calendar.Date.Writer](/v1/docs/lusidcalendardatewriter)

## Basic usage

```sql
select * from Lusid.Calendar.Date where <filter-expression>
```

## Query parameters

`Lusid.Calendar.Date` has parameters that enable you to filter or refine a query.

To list available parameters, their data types, default values, and an explanation for each, run the following query using a [suitable tool](/v1/docs/what-tools-are-available-to-write-luminesce-queries):

```sql
select FieldName, DataType, ParamDefaultValue, Description from Sys.Field where TableName = 'Lusid.Calendar.Date' and FieldType = 'Parameter';
```

## Data fields

By default, `Lusid.Calendar.Date` returns a table of data populated with particular fields (columns). You can return a subset of these fields.

To list fields available to return, their data types, whether fields are considered 'main', and an explanation for each, run the following query using a [suitable tool](/v1/docs/what-tools-are-available-to-write-luminesce-queries):

```sql
select FieldName, DataType, IsMain, IsPrimaryKey, SampleValues, Description from Sys.Field where TableName = 'Lusid.Calendar.Date' and FieldType = 'Column';
```

> **Note:** Fields marked 'main' are returned by queries that start `select ^ from Lusid.Calendar.Date`.

## Examples

> **Note:** For more example Luminesce SQL queries, visit our [Github repo](https://github.com/finbourne/luminesce-examples/tree/master/examples).

### Example 1: Determine if a certain date is a holiday

```sql
select * from Lusid.Calendar.Date where LocalDate = '2023-12-25'
```

### Example 2: Retrieve calendar dates for a certain year

```sql
select * from Lusid.Calendar.Date where CalendarCode = 'GBP' and LocalDate like '%2023%'
```

### Example 3: Check for any bond payments due to mature on a holiday

You can join `Lusid.Calendar.Date` with an [instrument provider](/v1/docs/lusidinstrumenttype-reader-providers) to check if a payment date falls on a holiday and subsequently how the payment date will be adjusted.

```sql
select 
    b.DisplayName, 
    b.MaturityDate, 
    b.LusidInstrumentId,
    b.FlowConventionsRollConvention,
    b.FlowConventionsSettleDays,
    c.DateIdentifier
from Lusid.Instrument.Bond b
inner join Lusid.Calendar.Date c
    on b.MaturityDate = c.FromUtc
where b.FlowConventionsPaymentCalendars like '%GBP%'
    and c.CalendarCode like '%GBP%'
group by b.LusidInstrumentId;
```

The table of data returned by the query looks like this:

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/be85edd0-b948-4eeb-a21e-fd7275a79777.png?sv=2026-02-06&spr=https&st=2026-11-09T07%3A48%3A28Z&se=2026-11-09T08%3A48%3A28Z&sr=c&sp=r&sig=jVO5q4cSyKcXEwj3tkzGTTjaalZFJU%2FOgqjhbbWOKpA%3D)