Start where you are. Use what you have. Do what you can. Arthur Ashe
Your life will not get better if you don’t move from where you are #HoskWisdom
With the imminent release of Microsoft Dynamics 365 (Dynamics 365 is coming and why you need to be ready) Microsoft is making significant step forward. I looked at my draft blog posts and found this blog and it seemed an interesting time to publish it.
Dynamics 365 gives Dynamics professionals a time to reflect and ponder the future and the past of Microsoft Dynamics CRM. Microsoft is removing the faithful CRM from the product, it’s a distinctive move.
Dynamics CRM moves to the cloud, will Microsoft redesign the architecture of Dynamics 365 to a cloud solution and utilize Azure and scalability. Is the one database design creating a bottle neck in performance?
If evolution really works, how come mothers only have two hands? Milton Berle Microsoft Dynamics CRM has evolved at a frantic …
That’s a great summary. Have been on the CRM journey since being early adopter of 1.2 in the UK. I do wonder if Microsoft need to take a step back and consider the whole product as its rapidly becoming an unmanageable scattergun collection of products..
Fixing some of the really annoying, and in most cases very well established issues in the product that make users stare at you in that ‘are you serious’ way would help.
Bolting several varieties of UI together, new, old an positively ancient makes for a confusing collection of experiences. Lookups that require many mouse clicks to get to the entry you want, the fact you still can’t return a count of how many records you have due to how database, security and localisation conspire against you to kill performance – and sure everyone has some other feature they wish would get sorted.
Don’t get me wrong, overall it’s a great product but stapling on newly aquired functionality at a rate of knots isn’t sustainable.
CRM needs to evolve into a new platform – probably not called CRM as even its name is a distraction.
Take the good stuff, turn it into a cloud based platform then add a modern, mobile first, cross platform adaptive UI and allow us to add or remove stuff so you get the system you actually need minus clutter and bloat. If I am never going to use marketing, or finance entities, allow that.
CRM should then be just one of a number of Dynamics products that sits on the platform. If I need accounts let me add modules from a proper accounting solution, or elements of ERP, or an Event Management solution – all modular, extensible and integrated.
The other core feature that’s needed is inbuilt integration and Master Data capabilities. I should be able to define one instance of contact, address, and account and share across multiple applications. Single version of the truth.
It will be interesting to see how things evolve as it moves to an inevitable cloud only model – looking forwards to the journey..
Thanks for a great blog…
The CRM SDK architecture page is a great resource to understand the architecture of Dynamics CRM
this picture explains the architecture, showing the moving parts along with the order and flow of Microsoft Dynamics CRM.
How did the original CRM Artchitecture come about?
Microsoft Dynamics CRM is one product made of multiple Microsoft products knitted together. The programmer in me thinks this is good design, splitting up the solution into logical parts.
- CRM is made up of many separate parts
- Active Directory
- Microsoft SharePoint
- Reporting Services
- Microsoft SQL Server
- Internet Information Services
- Active Directory Federation Services – ADFS – for expose CRM to the web
- Microsoft Exchange
The reason for using these separate parts is they are Microsoft products and it made sense to use existing products and delegate responsibility to products and service which specialize in.
When CRM was released cloud solutions were not popular, common or achievable (no Microsoft Data centres). It made sense for Microsoft to use it‘s own products because it could then persuade people to buy more Microsoft products or integrate CRM with existing Microsoft products a customer already owned (Exchange, Active directory, etc)
In the article The RISE OF CRM, Microsoft has upgraded the CRM front end making it look better.
The new forms is so they compatible with Microsoft mobile friendly functionality such as Business rules and Business Process flows.
Microsoft Dynamics CRM 2016 has new forms mixed in with old forms. I learnt this when investigating why I couldn’t add a business rule to the article entity – Why can’t I add a business rule to the article entity and in this article – CRM 2016 – How to rename the default business rule
Since its day one, Salesforce was designed as a cloud based application with design features optimized for a browser experience not a desktop program experience.
Where are we
Microsoft Dynamics CRM has a front end with a mixture of modernized forms and old CRM 2011 form style (5 years old).