Hello, I am running into strange filtering behavior in GoodData. When I select,

Last 7 Days

,

Last 30 Days

,

This Year to Date

, or any other date range my insight returns data. However, if I choose

Last 90 Days

I get a message that no data exists for my filter. I tested this out and found that relative filters of Last 89 Days and Last 91 Days both return data as well. What could be causing

Last 90 Days

only to fail to return data while every other filter surfaces data.

There is no mention in the docs or community threads of a known bug or special rule that would make only “Last 90 days” fail while “Last 89” and “Last 91” work, so I cannot point to a single documented root cause. However, based on similar date‑filter issues, here are the most likely areas to check: 1. Custom dateFilterConfig / presets If your organization or workspace uses a custom

dateFilterConfig

, the “Last 90 days” preset might be misconfigured (for example, wrong `from`/`to` values, wrong granularity, or set to

visible: false

/ not matching your date dataset). The relative presets are defined explicitly, e.g.:{ "from": -89, "to": 0, "granularity": "GDC.time.date", "localIdentifier": "relative_last_90_days", "name": "Last 90 days", "visible": true }If this entry is missing or incorrectly defined, the UI label “Last 90 days” could be mapped to a broken preset while others are fine. You can inspect and fix this via the

dateFilterConfig

organization/workspace setting.[Date filter config] 2. Date granularity availability in the LDM If the date dataset or some granularities were toggled off in the Logical Data Model, certain relative presets can behave unexpectedly or appear to have “no data.” Check that the date dataset used by the primary date filter has the

date

granularity enabled in the LDM.[Missing granularity] 3. Underlying date field used in the insight In some cases, the insight is configured to use a specific date field (e.g.,

CloseOn

vs. a more general

DateTime

). If the “Last 90 days” preset happens to align with a period where that specific field has no rows (while other presets hit periods with data), you’ll see “No data for your filter selection.” A similar situation was seen when an insight used a date field that simply had no data for the filtered year.[Date field choice] 4. LDM joins / many‑to‑many relationships If your insight’s metrics and attributes span multiple datasets with many‑to‑many relationships, GoodData may generate inner joins that can cause some filter ranges to return no rows even though base tables have data. This has been observed with attribute filters when an intermediate M2M table was empty; filling that table or adjusting the model resolved it.[M2M join issue] Because your other ranges work, the most concrete, checkable item is the

dateFilterConfig

preset for “Last 90 days”: • Verify in your org/workspace settings that: ◦ There is a

relativePresets

entry for “Last 90 days”. ◦ It uses

granularity: "GDC.time.date"

and

from: -89, to: 0

(or whatever range you intend). ◦ It is not accidentally pointing to a different granularity or mis‑typed value.[Date filter config] If that looks correct and the LDM/date field checks out, you’ll likely need Support to inspect the exact query and trace IDs for “Last 90 days” vs “Last 89/91 days,” since the knowledge sources do not describe a more specific, known defect for this exact case. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.

Hey Nick, Can you also share a direct link to the affected visualization, so that we can take a closer look and share our findings?

Hi Yvonne, I DM'd you the links.

Hi Nick, Thanks for sharing the links, I will have a look and get back to you.

The behavior is happening for that insight on the dashboard. Let me make a copy of that insight will all the dashboard filters and I'll DM you the link

Hey Nick, I am able to reproduce the issue in the recent visualization you shared. We are still analyzing this and will get back to you as soon as possible.

Hi Yvonne, sorry it is no longer available. We had changed our datasource earlier today and I had to revert so the YAML files were re-pushed to GoodData. I think we can close the issue for now as it likely was a cache-ing issue on our end. We are going to make some changes and then revert to the new data source later this week. If we continue to run into the

Last 90 Days

issue then I will reach out again

Thanks for the Information, I will go ahead and close this out.