Hi Team, @Petr Dolejsi @Peter Plochan @Dan Homola When creating a new relative date filter using the

dateDataSet

,

to

,

from

, and

granularity

parameters with the

newRelativeDateFilter

helper function, it requires the

granularity

to be specified as a

DateAttributeGranularity

type. This type typically takes values like

GDC.time.date

. However, it's worth noting that when GoodData initiates the execution call from their end, they pass the

granularity

as "DAY". This creates a discrepancy between the granularity values utilized in the

IFilter

object and those used in the execution API call. This discrepancy prompts a couple of questions: 1. Is there a specific reason behind the inconsistency between the granularity values employed in the

IFilter

object and those employed in the execution API call? 2. Does the GoodData library offer a Mapping object that facilitates the translation of granularity values between those used in

DateAttributeGranularity

and the ones utilized in execution calls? It would be helpful to address these questions in order to ensure clarity and consistency in the usage of granularity values within the GoodData library.

Hi, there is only internal utility that does not seems to be exported: https://github.com/gooddata/gooddata-ui-sdk/blob/master/libs/sdk-backend-tiger/src/convertors/fromBackend/dateGranularityConversions.ts#L60

Thanks team.