Forum Discussion
Totals
Hi karunrathi
Good to see you again 😃
This is just a hunch, but it looks like in #2, TRANDATE may be a datetime column, formatted as a date. So each row of the visual corresponds to a different datetime value.
Could you check if the column is defined as type date in Power Query? Switching the type to Date after loading to the model can make the column appear as a date but the time part is still present.That's what I can suggest off the top of my head, but if you can share a PBIX I could look further.
regards
Owen
Super UserHi karunrathi
Good to see you again 😃
This is just a hunch, but it looks like in #2, TRANDATE may be a datetime column, formatted as a date. So each row of the visual corresponds to a different datetime value.
Could you check if the column is defined as type date in Power Query? Switching the type to Date after loading to the model can make the column appear as a date but the time part is still present.
That's what I can suggest off the top of my head, but if you can share a PBIX I could look further.
regards
Owen
It worked,, Thank you!
Your hunch was 'Good as gold' 😄🙌 Is that how they say it down under??
I did flip that back and forth between Date and Date/Time today to try to fix it, but I kept doing it in the data view within the model. I changed the data type to DATE in Power Query for Test Report 1 yesterday while setting up the dataflow, I wanted to get the desired stack bar chart to work from these values - and it did work.
But forgot to do it today when I loaded the larger dataset for Report 2. And those hidden time stamps were driving me crazy, as I said, it felt like deja vu... similar thing happened 2 years ago, and I felt the solution was staring straight at me and you were the saviour back then as well.
Thanks again! Hope you're well.