Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
If you are building a tabular model for global audience in multiple time zones and your data involves time information, then this post may provide some approaches on dealing with different time zones.
The AS Engine has a simple type system which does not support datetime with time zones. So it is up to the modeler to do the necessary time zone reconciliation.
For example, let us say you have one call center in the east coast ( utc-5) and another one in west coast ( utc-8) and you use PowerPivot/Power View based global BI solution to do call volume analysis. The data is pulled from both places and aggregated at an hourly basis and the datetime is stored in UTC.
The Data Analyst could be in any place and when they are doing call volume analysis and they are interested in looking at the call volume in the local time zone.
Let us start with a simple table which has the location, the start and end times in UTC and the number of calls in PowerPivot
If the user tries to visualize this info in Power View, they will get
Since the date is in UTC format, it will display the UTC time which is not meaningful to the user in Seattle. It will make sense to seethe data in PST.
The modeler anticipating the potential usage in different time zones, could add calculated columns for each time zone that would be used witha very simple formula
Now using the calculated column, the end user could easily visualize the data in the timezone that he/she is interested in
Of course, if you have multiple tables, it’s better to create a separate Date table and have the timezone conversion done at one place and rest of the tables reference this Date table.
Business Applications communities