Forum Discussion
Date table connection cause wrong average calculation
ohjjang So does you Date table contain just dates or dates and timestamps? The issue with just Dates in your case is that these will not match up with dates other than timestamps of 00:00:00 (midnight).
ohjjang My guess, and this is only a guess, is that setting the slicer sets the end time to be the date and 0 time (midnight) and thus excludes an entire day's worth of data?
Greg_Deckler Thank you Greg,
I did slicer setting 'between' and, only could choice date as correct... do not know how to choice even time for selecting midnight. I just add some more screen captures for your consideration. Thanks again for your help.
ohjjang Oh, I think I see the problem now (maybe). So what if you use Column1 in your slicer instead of your Date column from your Date table? And that's really strange if you have a Date table with a 1:1 relationship with a column that contains date/time values.
Greg_Deckler Hi again, Thanks a lot for your advice.
Yes your approach is work when i use column1 on slicer.
But for me, i have dozens of dataset exactly same format with Date / Time column (Time stamp) and values.
Hope to generate useful report comibining / calculation with datasets in same format, that is why i put date table for slicing...
Yes you mentioned, and i looked online most of relationship with date table is one to many, single direction. But it seems i should use different philosophy....do you have any idea?
