Forum Discussion
Post PatronIncorrect year in date hierarchy
Hi vanessafvg , you're right. It looks like the date hierarchy is just adding in those extra years in the slicer even though the data doesn't actually exist.
When I filter for the incorrect years, it doesn't return any data.
Post PatronHi Anonymous , vanessafvg
The original dataset does contain 1901, but that is the only valid "incorrect" year. The other years are 2019 and 2020.
In SQL server the field has data type date with the following format
Additionally, if I create a year column based on this date, it returns the correct years.
It is the date hierarchy which seems to return incorrect years
Community Championbo_afk i would think the date hiearchy which i believe is actually a virtual table will probably pad the gaps between the dates, if you want more control over the date, create your own date table and your own hiearchy from the date table, i think that might give you more control
vanessafvg is correct BUT if you create a date table it MUST have continous dates.
- bo_afk
Hi vanessafvg , you're right. It looks like the date hierarchy is just adding in those extra years in the slicer even though the data doesn't actually exist.
When I filter for the incorrect years, it doesn't return any data.