Notifications
Announcements
No record found.
The out of the box PowerBI dashboard embedded in Omnichannel for Customer Service uses UTC as the date time/zone filter. The Omnichannel Historical Analytics dash however contains the ability to filter by GMT which accurately reflects conversations and the day/date they were created. The Omnichannel for Customer Service dashboard does not align with our time zone and so conversations and date created is 10 hours behind. This skews the view for our supervisors who require a simple, quick view without applying filters for time zone.
Omnichannel Historical Analytics is unable to be customised in PowerBI conversely which creates some difficulties and tension in ensuring data accuracy and reporting alignment.
My question is how do we align the two dashboards without customising the pbix in PowerBI?
Hello David,
Supervisors can start setting the time zone filter to their own timezone in Omnichannel Intraday Insights too. We are releasing a feature that should be rolled out to all our customers by end of Feb/Mar - 2022 that allows supervisors to do this. Please look out for the feature at https://docs.microsoft.com/en-us/dynamics365/customer-service/intraday-insights-dashboard
Regards,
Vamsee
Sr. Product Manager - Omnichannel for Customer Service
Thanks Vamsee,
Just to confirm the new feature will be available on Omnichannel Insights for Dynamics 365 dashboard too?
The feature would be available even when Omnichannel Intraday insights is embedded within Omnichannel too, if that's what you meant.
To be clear, Time zone is already supported within Omnichannel Insights (or Historical insights). Please let me know if you are referring to something else.
Hi Vamsee,
I've attached screengrabs to describe the 3 different reports.
1. Omnichannel Insights for Dynamics 365 - PowerBI Dashboard embedded in Omnichannel for CS application:
2. Omnichannel historical analytics dashboard:
3. Omnichannel Intraday Insights - PowerBI embedded in Omnichannel for CS app:
As you can can see from the above the only accurate view our supervisors can access is Historical analytics which uses the correct GMT+10 filter (local time zone). Both the Intraday and Omnichannel Insights dashboards use UTC which is 10 hours behind local time zone.
Making available a GMT filter in all insights reports would solve the problem.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Tom_Gioielli 55 Super User 2025 Season 2
Daniyal Khaleel 27 Most Valuable Professional
Scott Jackson UK 22