Microsoft CRM Dynamics

  The main goal of any sales Company is to identify prospects and turn them into revenue. For example, how do you take someone you met at an event and turn them into a customer? This process is referred to as a sales lifecycle. A typical sales lifecycle might resemble the following image: To assist sales lifecycle management, many organizations use processes that guide sellers throughout the entire sales lifecycle. A sales process ensures that everyone is following the appropriate procedures. The image below is an example of what a sales lifecycle might look like from beginning to end: Dynamics 365 Sales assists organizations with managing their sales lifecycle. In most organizations, this lifecycle begins with leads. Let’s examine how Dynamics 365 Sales helps sellers create, manage, and qualify sales leads.

"Secondary Entity use when you have to trigger plugin or retrieve record from  Intersect Entity(contactleads)  having records of  Entities(Contact and Lead)  having N:N Relationship" While using the  Plugin Registration tool  in Dynamics CRM, we might have rarely or even never used the  ‘Secondary Entity’  field and almost always assigned it as  ‘none’,  but there are some scenarios where this field comes into play. When is ‘Secondary Entity’ required The following 2 messages require the ‘Secondary Entity’ to be specified while registering a step in Plugin registration: SetRelated RemoveRelated These two methods were extensively used in Dynamics CRM 4.0, but they were deprecated from Dynamics CRM 2011 onwards; although you can still use them in 2011 and 2013.  

As a developer who is interested in extending or customizing Microsoft Dynamics CRM, you can choose from several methods to perform your tasks. In addition to adding client-side JavaScript code to a form or adding custom ASP.NET pages, you can write a plug-in or create a custom workflow by using the web interface that calls a custom workflow activity. How do you decide when to use a plug-in and when to use a workflow? The technology that you use depends on the task that you have to perform and who will author the customization. For example, you must use a synchronous plug-in real-time workflow if you want to execute custom code immediately before or after the core platform operation executes and before the result of the operation is returned from the platform. You cannot use an asynchronous workflow or asynchronous plug-in in this situation because they are queued to execute after the core operation finishes executing. Therefore, you cannot predict when they will run. If you wan

REST is a software architecture style consisting of guidelines and best practices for creating a scalable web services. REST is a coordinated set of constraints applied to the design of components in a distributed hypermedia system that can lead to a more performant and maintainable architecture. REST has gained widespread acceptance across the Web as a simpler alternative to SOAP and WSDL-based Web services. RESTful systems typically, but not always, communicate over the Hypertext Transfer Protocol with the same HTTP verbs (GET, POST, PUT, DELETE, etc.) used by web browsers to retrieve web pages and send data to remote servers.”  SOAP “SOAP, originally an acronym for Simple Object Access Protocol, is a protocol specification for exchanging structured information in the implementation of web services in computer networks. It uses XML Information Set for its message format, and relies on other application layer protocols, most notably Hypertext Transfer Protocol (HTTP) or Simple Mail T

User Group All Microsoft CRM. This group is updated automatically as users are added and removed from Microsoft CRM. ReportingGroupA group contains all users within Microsoft CRM. This group is updated as users are added to Microsoft CRM. Users in this group have read-only access to the filtered views in the Microsoft CRM database. PrivUserGroupPrivileged Microsoft CRM user group for special administrative functions.  SQLAccessGroupA group that contains Microsoft CRM ASP.NET account and other service accounts. Members in this group have full access to the Microsoft CRM database and this group is used by the Microsoft CRM platform layer. End users should never be added to this group.

Requirement Plug-in Workflow Needs a synchronous action to happen before or after an event occurs. The same piece of logic will be executed for different events and possibly on different entities. The logic needs to be executed while offline. Needs elevation of privileges (impersonation) Needs to execute on events other than assign, create, update, and set state The process/logic may take a long time to complete or will be a persistent process (multiple long-running steps). Need an asynchronous action. End users will need to modify the process logic Child subprocesses will be triggered.