Parameters - End date should always be greater than Start Date

Question & Answer
, ,
1

I have created the custom sql, and created and added the parameter in dataset level itself.
Custom SQL:
SELECT
date,
count
FROM xxx.yyyyyy
WHERE date >= COALESCE(CAST(<<$StartDate>> AS TIMESTAMP) AT TIME ZONE ‘UTC’, ‘1900-01-01’::timestamp)
AND date <= COALESCE(CAST(<<$EndDate>> AS TIMESTAMP) AT TIME ZONE ‘UTC’, ‘2200-01-01’::timestamp)
AND count > 0

Now I have added the controls through parameters after mapped. Now all I need is, if I try to select April 01 2025 then end date should always be greater than or equals to april 01 2025, end data should not show before dates. How can I acheive this?

2

Hi Priyanka,
If you are trying to select April 1 2025 as value in the end date control then that should give you the expected result. If that’s not the case. Can you provide additional information about with which control are we trying to attend this output and also parameter type info could also be helpful.

Thanks
Yamini

3

Thank you for your support @Yamini_Baskar_24

I’m working with two date filters in QuickSight: Start Date and End Date. By default, both filters display the full range of available dates (months, years, days), which is expected.

However, I’m trying to implement the following logic:

When a Start Date is selected (for example, April 4, 2023), the End Date filter should only show dates on or after the selected Start Date.

Additionally, if the user selects an End Date that is earlier than the Start Date, I want to prevent the KPIs or visuals from showing any data. They should only reflect results when the End Date is greater than or equal to the Start Date.

Is there a way to enforce this kind of dynamic filtering or validation in QuickSight (either through parameter configuration, calculated fields, or controls)?