Skip to main content

Preparing for product changes in Microsoft Dynamics 365/CRM: A primer

by Aaron Back
Dynamics 365 Customer Engagement Practice Lead, ACE Microtechnology, ACE Microtechnology

Over the last couple of years, Microsoft has restructured the underlying architecture and the consumption approach for Dynamics 365 Customer Engagement (CRM). This shift still has many people scratching their heads on how to understand it. The goal of this article to help you understand this model, which in turn could help you prepare for the upcoming changes.

Laying the foundation

Any good building starts with a solid foundation. In our modern era, these foundations are also allowing for many systems feeding into the building. Not only does the foundation need to be structurally sound, it needs to provide access for water, electric, communications, and many other functions.

The foundation for Dynamics 365 has changed to meet shifting requirements. In order to meet the demand for new types of connections and applications, Microsoft has implemented the Common Data Service.

Source: Microsoft

This platform is the foundation for a modular approach to implementing Dynamics 365. As you can see from the above image, the Common Data Service sits within Azure, which allows for easier use of services like Azure AI to enhance solutions.

The new model also simplifies connections to other online or on-premises services. As an example, Microsoft Flow allows you to connect to over 150+ online services and build workflows to create, read, update, and delete (CRUD) from Dynamics 365.  For on-premises data sources, you can build custom connectors to Dynamics 365 and the Common Data Service.

In between the Common Data Service and Dynamics 365 is PowerApps. PowerApps is the foundation of Dynamics 365 Customer Experience first party apps, and you can use it to build business apps to meet your specific needs. These apps come in the form of either Canvas Apps or Model-Driven apps, the same approach used by Dynamics 365 apps.

Model-driven apps

Now that you have a basic understanding of the foundation, it's time to build on the foundation. This is where the model-driven apps come in to play.

Model-driven apps come with a standardized set of components to leverage in building your apps. The components are Entities, Fields, Relationships, Forms, Views, and Site Maps.

app_designer_my_first_app_page.png

Source: Microsoft

With model-driven apps, you can build once for multiple devices. The new user interface, called the Unified Interface, brings responsive web design for any device.

Preparing for changes

FREE Membership Required to View Full Content:

Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here

About Aaron Back

Aaron Back is Microsoft Certified Solutions Expert (MCSE) with many years' experience with Microsoft Dynamics 365 (CRM). He is actively involved with the Microsoft Dynamics 365 UG (D365UG) (User Group) Community. His involvement includes: Serving as Chapter Leader for his local D365UG Chapter, serving on the D365UG Board of Advisors, and speaking at the annual D365UG Summit conference.

Company:

ACE Microtechnology, Inc. is a professional services firm committed to delivering Dynamics 365 (CRM) business solutions to small and medium sized organizations. Our focus is on delivering products and services that improve our clients’ business operations. ACE has developed specialties in serving the lite manufacturing, distribution and the hospitality industry.

Rather than just building technology or implementing software, we deliver real business value through industry knowledge and understanding each client’s business. We make it our business to know your business.

For more information or assistance with Dynamics 365 (CRM) contact ACE!

More about Aaron Back