Forum Discussion
Capacity Metrics Dashboard - Notebook Pipeline Run reported incorrectly (time off by an hour?)
Hi v-prasare
Its funny, but I see that there are dozens and dozens of other posts about the timezone problem in the capacity metrics app.
I didn't see those at first.
No customer would expect that we should be updating a timezone offset two times a year, in a configuration parameter. Nor would we expect that there is only one timezone that is relevant to the entire capacity. This had the feeling of a bug, but I don't think Microsoft considers it a bug. It appears in the microsoft documentation.
I'm probably going to close the case now. Whenever I install this app in the future, I will just use UTC. Less confusing.
Hi v-prasare
Its funny, but I see that there are dozens and dozens of other posts about the timezone problem in the capacity metrics app.
I didn't see those at first.
No customer would expect that we should be updating a timezone offset two times a year, in a configuration parameter. Nor would we expect that there is only one timezone that is relevant to the entire capacity. This had the feeling of a bug, but I don't think Microsoft considers it a bug. It appears in the microsoft documentation.
I'm probably going to close the case now. Whenever I install this app in the future, I will just use UTC. Less confusing.
Exactly right and don't get me started on this issue in Power BI Desktop. It's outrageous and a total disaster how badly the ball has been dropped with timezone management. So much for time intelligence, huh? 😂