The Clearly Podcast
Power BI and Microsoft Dynamics
Summary
This week, we talk to Haseet Sanghrajka from City Dynamics about Microsoft Dynamics and Power BI.
Well, that was what we were meant to talk about.
It’s difficult to approach this subject without starting with the range of reporting options used by Dynamics customers. And it is a broad range from our old friend Excel, to Jet Reports and FRX, Power BI and many more in between. Haseet takes us through the choices and use cases for the multiple options out there.
We also talk about how the life of the Dynamics partner has changed over the last 20 years. Personal indulgence on my side.
We end with a discussion on how Dynamics customers are specifically adopting Power BI as their chosen reporting/BI application. Ease of purchase and price point has been a significant contributor to why many customers start Power BI projects. And once it’s started they see all of that BI goodness…
Haseet was a fascinating source of insight on this subject and if you have any interest in the intersection between Dynamics and how customers consume data – this is the one for you.
If you already use Power BI, or are considering it, we strongly recommend you join your local Power BI user group here.
Transcript
Andy:
I'm excited for a couple of reasons today. First, we have a special guest, and second, we have an upgrade in Shailan.
Tom:
Twice in one season.
Andy:
Yes, twice in one season. I've been on all podcasts, so let's move on. Our special guest today is Haseet Sangrajka of City Dynamics. We'll discuss Dynamics, reporting, and Power BI. Haseet, please tell us about yourself and City Dynamics.
Haseet:
Thanks, Andy. Hi, Tom and Andy. City Dynamics is a Microsoft Dynamics 365 partner based in London. We focus on Dynamics Business Central and Dynamics Customer Engagement, especially for financial and professional services clients. We turned 20 in January 2022, and the market has changed a lot since we started in 2002 with Microsoft's entry into business solutions.
Andy:
Yes, it's been a lot of evolution. It must be a challenge keeping up.
Haseet:
Absolutely. The changes, especially since Microsoft unified its services under the Dynamics 365 umbrella, have been significant.
Andy:
Today, we’ll discuss Dynamics and Power BI, but let's not assume all Dynamics reporting is Power BI. There are many reporting applications for Dynamics customers. Tom, you’ve worked with many Dynamics customers. Let's discuss the variety of reporting and analytics platforms they use.
Haseet:
Sure, let's look back. We started with Dynamics GP and 4X, which worked well together. Excel was often used for analysis. With the introduction of SQL Reporting Services, clients began using SSRS, although it was limited. Larger tools were too expensive, so Excel and SQL Reporting were commonly used. Today, SQL Reporting hasn't migrated easily to the cloud, so clients often use Power BI, especially when existing solutions don't meet their needs. Some clients use Click or Tableau, but Power BI's low entry cost makes it appealing.
Andy:
When you say the entry point is low, do you mean cost?
Haseet:
Yes, with Power BI Pro costing around £10.50 a month, it's affordable for clients to trial. If they don’t like it, they can easily turn it off. This flexibility is a big advantage.
Tom:
Yes, from a licensing perspective, starting with Power BI can be very cost-effective, sometimes just £50 for a trial.
Andy:
There’s also strong brand association with Microsoft, making Power BI a convenient option. The single sign-on and integration with other Microsoft products are powerful features.
Haseet:
Absolutely. The ease of enabling Power BI within a tenant is a huge advantage. Clients can quickly start trials and see the benefits. The simplicity of integration and the ability to enhance further with Azure or Office 365 make it a preferred choice.
Andy:
So, when starting a Power BI project, where do you typically begin?
Haseet:
We start by assessing how the client wants to consume data. If they need simple dashboarding, Dynamics 365 might suffice. For more complex needs, Power BI is better. It's especially useful when clients want data on mobile devices. We ensure Power BI is part of their toolkit for when they need it.
Tom:
And it’s crucial to consider how users will consume the reports, whether on their desktop or mobile.
Haseet:
Exactly. We often design reports with mobile consumption in mind. Many senior staff prefer accessing key metrics on their phones. Power BI's design tools make it easy to create mobile-friendly reports.
Andy:
What happens after the initial Power BI implementation?
Haseet:
Initially, we address immediate reporting needs. Over time, clients often move to consolidate data into an Azure database, using Power BI for comprehensive reporting. This progression supports deeper insights and more strategic decision-making.
Tom:
Yes, long-term projects often involve migrating historical data and integrating multiple systems, with Power BI providing a unified reporting platform.
Andy:
What are your top tips for success with Dynamics and Power BI?
Haseet:
System Design: Ensure the system is designed for easy data entry and accurate reporting.
User Adoption: Make the system user-friendly to ensure high adoption.
Data Quality: Maintain high data quality to support reliable reporting.
Integration: Utilize integration capabilities to consolidate data from multiple sources.
Andy:
Great insights. Thank you, Haseet. This has been a valuable discussion.
Haseet:
Thank you for having me, Andy and Tom. I enjoyed it.
Andy:
Thank you, everyone. That wraps up our podcast. Goodbye.
Tom:
Cheers.. Stay tuned!