Skip to main content

FAV Plugin for Microsoft Dynamics CRM: Formula, Aggregation and Validation


InfoStrat has developed the FAV Plugin for use with Microsoft Dynamics CRM to support data validation, aggregate operations, and formula support without programming.  Many business applications for Dynamics CRM require complex business operations that are not supported in Dynamics CRM out of the box but can be implemented through plug-in configuration.

Typically, in a complex Dynamics CRM deployment, business rules, complex calculations and additional security measures are scattered across multiple layers.  Often all of the above are implemented in JavaScript code on various Dynamics CRM forms, in Plugins, and in other extensions such as external portals and data integration components. This proliferation of implementation decisions makes a solution extremely hard to maintain and modify, breaking the development agility inherent to Dynamics CRM. The FAV Plugin allows an implementer to concentrate these functions in a single location and implement all requirements declaratively.

Background

Microsoft Dynamics CRM includes a flexible SDK framework that allows developers to modify the standard behavior of the CRM platform.  One of the approaches to customization in Dynamics CRM is custom compiled code—a Plugin—that runs against events triggered by actions in Dynamics CRM. These Plugins can be run on the Dynamics CRM server either synchronously or asynchronously.

The Dynamics CRM framework is designed for extension: the metadata for core entities is exposed in the API for creation of custom entities. Due to this high degree of extensibility, Dynamics CRM development can address the business functions for a wide variety of organizations.

InfoStrat has developed the FAV Plugin for use with any Dynamics CRM instance, whether based in the 2011, 2013 or 2015 version, hosted on premise or online. The context for the FAV Plugin operation is driven entirely by configuration objects located in the FAV Plugin registration properties, enabling developers to use this FAV Plugin against many CRM instances with increasing economies of scale for each implementation. As a result, the FAV Plugin can be used to implement declaratively complex business rules and additional security measures.

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

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

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