Hey team, can someone explain why these rows (with...
# gooddata-cloude
Evangelos Malandrakis
05/05/2025, 10:49 AMHey team, can someone explain why these rows (with dates that don't match with the filter) appear on the analysis?
m
Mauricio Cabezas
05/05/2025, 12:30 PMHi Evangelos, thank you for this. May I ask if the issue is happening only in one dashboard/insight? Would you be so kind as to share with us the direct link to the insight to investigate further? Feel free to use DM.
Mauricio Cabezas
05/05/2025, 6:27 PMHi Evangelos, I wanted to update you that I've been able to reproduce the issue on my end. It appears that there might be a problem with the hour and/or minute filter. To get a definitive answer, I asked to the team responsible for this matter. I will provide an update as soon as I have more information from them. Thank you for your patience.
👌 1
p
Philip Asp
05/06/2025, 7:15 AM@Mauricio Cabezas Hi Mauricio, I work with Evangelos on the data team. We saw this behavior in another visualization 4 weeks ago. The visualization was aggregating revenue data based on filtering per month (datetime_ltz).
The revenue data is critical for us, so to fix the problem we switched the underlying table to an aggregated view.
We see this as an high priority issue for us since a lot of filtering is based on datetime. We need to be able to trust the filtering.
Appreciate if you can prioritize this issue. I assume this is impacting more clients.
Thanks!
m
Mauricio Cabezas
05/06/2025, 12:41 PMHi Philip, thank you for this update, I am sorry but still we do not have answer.
I will increase the priority.
May I ask for clarification, you are mentioning the same problem for another visualisation, but filtering by month besides Hour or Minute. Could you share internally the direct link to the visualisation, please?
p
Philip Asp
05/06/2025, 1:20 PMHi Mauricio, we don't have this visualization anymore. It was replaced using the aggregate view.
In that dashboard we are filtering on "Last month". The issue was that the filter did not take into account the local timezone (DATETIME_LTZ). So, the records with around midnight last day of the month was interpreted incorrectly by the filter (UTC vs CET).
m
Mauricio Cabezas
05/06/2025, 1:44 PMHi Philip, just to clarify and avoid any misunderstanding. We have two cases in this thread, right?
1. When filtering Date on Static Period using some specific time/hour on the day, the filter is not working as expected and is showing all the values for the day of the date, meaning the filter is not applying specific Hour and/or minutes.
2. Filter is not working as expected, for example when you filter by Last Month and on the last and first day of the month, near to midnight is an inconsistency. Regarding this, you mentioned a old case, I found it on this thread, where it seems was resolved (it was a bug), so you just mentioned as example, right?
Both are issues with Date filter, but are not related, just to be sure.
So, currently the only issue is 1)?
Mauricio Cabezas
05/06/2025, 6:58 PMHi Philip and Evangelos.
Regarding the first point, thank you for your patience while we investigated the issue you reported with the Static Period date filter when using Minute or Hour granularity.
After a thorough review and extensive testing with our engineering team, we have been able to reproduce the behavior you described.
We've confirmed that the filter on the dashboard and insight level is not correctly applying the Minute or Hour granularity, effectively filtering only by the day.
We understand the priority of this issue for you, especially when precise time-based filtering is required, and we sincerely apologize for the inconvenience this is causing.
We have reported this as a confirmed bug and have raised an internal ticket with our development team for further investigation and resolution. Unfortunately, at this time, we do not have an estimated time of arrival (ETA) for a fix, as the root cause is still being identified.
We appreciate your help in reporting and your patience as we work to resolve this. We will keep you updated on the progress of the internal ticket as we receive more information.
p
Philip Asp
05/07/2025, 6:54 AM@Mauricio Cabezas
FYI: @Evangelos Malandrakis
Thanks for the update!
In regards to 2. - sorry, I was not fully updated on this. I see that is now explained and will be resolved.
e
Evangelos Malandrakis
05/07/2025, 7:10 AMHey @Mauricio Cabezas, we have a new thread for the same problem here: https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1744177485502879
And I'm not sure if it resolved, so we would appreciate if you can check it 😊
m
Mauricio Cabezas
05/07/2025, 12:30 PMHey Evangelos, Thank you for bringing that case to my attention. I have checked internally, and it is still not resolved. I apologize for the inconvenience, and I've requested an update. Regarding the original issue on this thread, with the hour and minute filters, our engineers have identified the root cause and are currently working on a solution. I appreciate your patience. I will keep you posted.
👍 2
Mauricio Cabezas
05/08/2025, 4:09 PMHi all,
I have an update: Both cases are likely related. In short, we have a bug in the way timestamps are filtered for Snowflake.
Our engineers are working on it but still I can not provide an ETA.
Once again, we appreciate your reporting both issues, as it helped us discover the bug. I will keep you updated.
p
Philip Asp
05/09/2025, 6:20 AMGood that you are able to replicate/confirm the bug, first vital step to fix it. Thanks for the update.
j
Jakub Sterba
05/13/2025, 11:29 AMThe fix has been delivered to GD Cloud.
🙌 1
m
Mauricio Cabezas
05/13/2025, 11:41 AMHi Phillip and Evangelos,
As Jakub wrote, the bug has been fixed and delivered to GD Cloud Production. I have tested it on my own environment, and I can confirm that now the static period filtering by hour/minutes is working as expected.
Please let us know if you need further assistance and thank you for your patience.
p
Philip Asp
05/13/2025, 12:06 PMOk, thanks for the update 👍
3 Views