Skip to main content

Planning for Dynamics 365 (formerly Dynamics CRM) Solutions

NOTE: Updated to include Dynamics 365

Microsoft Dynamics 365 (formerly Dynamics CRM) allows a developer to package  a number of customizations as a solution so they may be installed and managed as a unit rather than individually.  For instance, you could put all your custom entities and attributes as well as reports in a solution.  The solution may be installed into an instance of Dynamics 365 -- online or on premises.

Managed solutions are a type of solution which prevents unintentional changes to the customizations. You must start by creating an unmanaged solution and then deploy it as a managed solution in another instance of Dynamics 365.

There are many approaches to defining solutions.  One extreme is to put all customizations in a single solution.  The other extreme is to use dozens of solutions.

For Microsoft Grants Manager, we would use one solution for the standard Grants Manager Plus customizations, and another which contains customizations unique to a particular agency. A third solution is used for the customizations that relate to the PortVue portal.

Be careful about dependencies among solutions, because this can complicate deployment. If you end up with proliferation of too many solutions, you may want to re-examine them and determine whether some should be merged into fewer solutions.

Solutions are not designed as a tool for managing a multi-developer project.  There are better ways of coordinating coding than to have a solution for each developer.

You need to consider maintenance implications of Dynamics 365 solutions.  For instance, today we were updating a client's CRM to a new version, only to find that a managed solution was installed that no one recognized.

Solutions are not backwards compatible to earlier versions of Dynamics CRM, as shown in the following figure:

Source: Microsoft https://msdn.microsoft.com/en-us/library/gg328109.aspx




Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan

Power Apps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as Power Apps Portal and shifted to the Power Apps side of the Microsoft product family. Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users. The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription." Pricing starts at $200/mo