I’m running into a pretty weird bug, and I think it is because I have changed the start of the week in my analysis to begin on Monday rather than Sunday.
I have created a calculated field “Week commencing” that tells me what week the data I have is for and formatted in a specific way:
formatDate(truncDate('WK', {date}), 'd-MMM-yyyy')
This field then gives me values of ‘22-Jun-2024’ for last week and ‘29-Jun-2024’ for the current week. However, when I apply a filter on this field and add it to the top of the dashboard, the values displayed in the filter control dropdown are ‘21-Jun-2024’ and ‘28-Jun-2024’. So when I select one of these values, no data is displayed in my table as the values in the filter aren’t the same as in my data.
That doesn’t solve my issue, as the week commencing filter still displays ‘21-Jun-2024’ and ‘28-Jun-2024’ as the options in the filter control dropdown at the top of my analysis.
I have done that, this screenshot clearly shows that the filter has been added on the calculated field and the control has been added to the top of the page:
Then this screenshot is of the control itself, clearly the values being displayed in the control don’t align with the actual data for some reason:
This seems to be a bug with the filter control value generation. I have created a ticket for this issue - Internal link. If you want to keep track of updates, please submit a support ticket and reference the above link in there.
Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf.
I wouldn’t recommend any workaround with addDateTime function as that will start to fail at a later stage when this bug is fixed.