Reports Date based on User's Timezone
closed
Sandana Thevar
marked this post as
closed
Thanks for raising this. Supporting report timestamps based on each individual end user’s local timezone isn’t possible due to a Power BI limitation. Because of this, we won’t be able to enable timezone-specific reporting.
We will continue using a consistent timezone standard—either UTC or a single timezone that the customer chooses.
H
Harsh Seksaria
For example, the team is working in the UK time zone, and their shift ends at 12.30 AM IST i.e. 7 PM UK time.
If they are closing any tickets between 12.00 to 12.30 AM IST then it is coming under the next day in Enate data feed but the team is actually closing it on the same day because their shift ends at 12.30 AM IST and in their reports, it also showing Same day not next day. However, in data feed, it is showing the next day and creating a count mismatch issue.
This is specific to data shared to customers via Azure tenant or OData.