When you go for plug-in and workflow?

  1. Plug-in
    1. Plug-in supports range of SDK messages or can be triggered but workflows are limited to be triggered on record creation, status change, and assignment, attribute change and deletion.
    2. Plug-in can execute synchronously on Pre Validation and Database Transactions.
    3. Needs a synchronous action to happen before or after an event occur.
    4. Needs elevation of privileges (impersonation)
    5. The process/logic may take a long time to complete or will be a persistent process (multiple long running steps).
    6. Better small operations like data lookups, common data operations.
    7. Data validations.
  1. Workflow
    1. Child sub processes will be triggered.
    2. Can run processes manually using run workflow.
    3. Plug-in is not intend to fire or execute logic while timeout or subscription with recursive.

Product Catalog : Product Kit

  • Products can also be bundled together to form a kit.
  • A kit helps to simplify the sales and ordering process.
    • For example, if an organization sells digital cameras and batteries, these two products can be bundled together to form a kit.
  • To form a kit, first convert the product to a kit product, and then add each product to the kit.

Creating Workflows - Microsoft Dynamics CRM 2011

This CRM 2011 video goes through how to create 2 workflows:

  1. Notification when an opportunity hits the proposal stage in the sales cycle AND it is above $250K
  2. Updating the Account to Relationship Type = Client when an Opportunity is WON.

Creating Role Based Forms - Microsoft Dynamcis CRM 2011

This video provides an overview of how to create a unique and tailored user experience for each type of user that is logging into CRM by creating a separate form for each Record Type in CRM (like Accounts, Contacts, Opportunities etc.)

Opportunity :User Provided Pricing

When User Provided is selected, opportunity products and write-in products can still be added, but their pricing is not be used when determining the value of the opportunity.

Microsoft Dynamics CRM 2011: Implementing Claims and IFD: Part 6

This session will cover some common troubleshooting questions related to Claims-Based Authentication and IFD in Microsoft Dynamics CRM.


Creating a User Adoption Dashboard - Microsoft Dynamics CRM 2011

This video goes through the process of creating a User Adoption Dashboard in Dynamics CRM 2011. The video explains the approach to building a dashboard in CRM 2011 and how the related charts and views make the dashboard present the data that you want.

What meant by plugin?

A plug-in is custom business logic that can integrate with Microsoft Dynamics CRM 2011 to modify or augment the standard behaviour of the platform.

CRM 2013 Quick Tip: Add new information quickly through shortcuts in Microsoft Dynamics CRM

Error Handling in Plug-ins

  1. For synchronous plug-ins, the Microsoft Dynamics CRM platform handles exceptions passed back to the platform by displaying an error message in a dialog of the web application user interface.
  2. For asynchronous plug-ins, the exception message is written to a System Job (AsyncOperation) record.
  3. For plug-ins not registered in the sandbox, the exception message (System.Exception.Message) is also written to the Application event log on the server that runs the plug-in.
  4. Sandboxed plug-ins should use tracing.
    1. Tracing is to provide isolated (sandboxed) plug-ins and custom workflow activities with a way to output runtime information when an exception is thrown because isolated plug-ins and custom workflow activities cannot write information to the system event log or the file system.
    2. The tracing service was implemented to provide sandboxed plug-ins and custom workflow activities with a means to output run-time information when an exception is thrown. In addition, tracing is also supported in plug-ins that is not sandboxed.