Skip to main content

To Code or Not to Code in Dynamics CRM

Microsoft Dynamics CRM offers a wide range of features combined with the ability to customize the data model and workflows without any coding.  The question is, will these features fulfill all your business requirements or do you need to write some custom code? 

This is an important question, because once you start writing code you need to put in place a commensurate framework, methodology and platform to support it.  For instance, you may need multiple environments for development, testing, staging and production.  You may need version control for code as well as documentation. 

If you choose to go the No Code route, you may need to compromise the complexity of your business rules and change the way you work to suit the product better.  You will also have to settle for a bit less automation of some functions that could be streamlined through code. For instance, if you are determined to assign Account IDs that are a combination of the abbreviated customer name, state and date that they became a customer you will need to write some code.  Integration with other systems such as inventory or timesheets nearly always requires writing code.  Complex field derivations and validations require coding. 

If you are a do-it-yourselfer and not a programmer, and you want to implement Dynamics CRM on your own, try not to take on more than you can handle in terms of custom code.

Third party plug-ins can extend the capabilities of Dynamics CRM without forcing you to write and support custom code of your own. You can purchase plug-ins for reports and calculations or for functions such as sales tax calculation. 

Be sure to consider where you stand on custom coding in your implementation of Dynamics CRM. 

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

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

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