Forum Discussion
Today Filter in Reports
Hi karthik have you heard of any updates / fixes around this? Still causing me lots of issues being in New Zealand and +13 hours.
ED
The workaround is to use NOW()+13/24 and convert this to date datatype to get to the NZ timezone in the service. This is not ideal as this would change depending on day light saving settings per region which is quite soon in NZ (I am based in NZ as well :) )
The workaround to make it dynamic is to create a daylight savings tables with the start and end date and use with the time difference related to the date range.
Do you use SQL Server (or any relational database) as a data source in your app? If so you can create a view on your date dimension and create a field named "Is Current Date" set to 1 for current date. You can then use this attribute "Is Current Date" in your calculations.
- elliotdixon10 years ago
Responsive Resident
Cheers karthik
I saw another post on the forums - TimeZone Fix and managed to apply that after messing around for quite a while.ashishrj recommended
New_Calculated_Date = Old_Calculated_Date + (13/24) {changed for NZ}Your idea about a daylight savings table is a good one otherwise I am going to have heaps of datasets to fix up in April. Guess it just means a bigger calcuation for the dates as well.
Quite annoying that there is so much work required to get the data to match our timezone!
I do use a RelativeDate column to give days previous and infront of today. Very useful indeed.
RelativeDate = [Date]-TODAY()
On another note.
As a fellow Kiwi have you managed to work out how to get the dates converted to non US setup once uploaded to PowerBI.com.on my desktop app the dates look like
but when uploaded they automatically change to
Would be great to fix this.
Rgds - ED