Microsoft CRM Dynamics

Required Software and Assemblies To develop Windows Workflow Foundation 4 custom activities, you must develop them on Microsoft .NET Framework 4. If you plan to register your custom workflow activities with Microsoft Dynamics CRM Online, you must build them using the Microsoft .NET Framework 4  PU3  (platform update 3) or a later version, such as .NET 4.5. The following assemblies must be added as references in your project. They can be found in the  SDK\Bin  folder in Microsoft Dynamics CRM SDK. Microsoft.Xrm.Sdk.dll Microsoft.Xrm.Sdk.Workflow.dll Use the CodeActivity Workflow Base Class To create a custom workflow activity, create a class that inherits from the  CodeActivity  workflow base class. This class is available in the  System.Activities namespace. Activities that inherit from the  CodeActivity  class can override the  Execute  method to produce custom functionality. To create a custom activity...

CRM 2011 will now allow to decide permissions not just at the record level but also “Field Level”. This means that you can decide if a user has the permission to that attribute at the time of Create or Update or simply view the data for that attribute. Currently, this feature is only available for the custom attributes that you add. They are not available for the system attributes. When you create a new attribute you can enable “Field Level Security” for that attribute. Once the attribute has been defined for Field Security, it becomes available for defining the security levels for different roles. Similar to the Security roles, you can now create Field Security Profiles The profile lists out all the attributes setup for Field Security and you can edit the permission to Read, Update and Create. Note any security that you apply here is not just available/applicable on the CRM forms, but also programmatically. So if you try to edit a custom attribute of an entity for which...

Synchronous In general, synchronous (pronounced SIHN-kro-nuhs, from Greek syn-, meaning "with," and chronos, meaning "time") is an adjective describing objects or events that are coordinated in time. In information technology, the term has several different usages. In other words a process occurring at the same time or at the same rate or with a regular or predictable time relationship or sequence. Asynchronous  In general, asynchronous (pronounced ay-SIHN-kro-nuhs, from Greek asyn-, meaning "not with," and chronos, meaning "time") is an adjective describing objects or events that are not coordinated in time. In information technology, the term has several different usages. In other words a process whose execution can proceed independently, "in the background". Other processes may be started before the asynchronous process has finished. In computer programs, asynchronous operation means that a process operates independently of oth...

Whenever you install MSCRM what all databases get created? Answer: MSCRM_Config and  MSCRM _orgname.

Dynamics CRM is frequently integrated with the data and services of systems such as:  ERP and accounting systems like Dynamics GP, NAV, and AX, as well as third-party systems like SAP, QuickBooks, and many others CTI/Telephone systems like Cisco and Avaya Line-of-business applications, such as manufacturing process management systems and shipping systems. Internal and external-facing Web sites, from simple contact or help request forms through full portal and e-commerce integration l File and data repositories and directories l External data sources used for lead generation and market research, such as Dun & Bradstreet, Hoover’s, or Dodge Reports.   Recognizing the need for these kinds of integrations, Microsoft has designed Dynamics CRM to be an incredibly flexible and extensible system with many points for integration. Microsoft Dynamics CRM 2011 is itself an integrated system, each tier of the system having multiple integration ...

Append and Append To are two privileges that most user are not very clear about regarding their functionality. In this article we try to explain the difference between “Append” and “Append To” Privileges and how it affects the user access. Append and Append To basically deal with the entities that are parties to a 1:N relationship or N:1 relationship. Append:  When an entity has the lookup of another entity on its form. It is important that the user have the “Append” privilege on this entity so that it can set the values for the lookups on this entity. For eg: Contact has the lookup of Account on its form so here the user needs to have the “Append” privilege to be able to set the parent account. Append To:  When an entity is available as a lookup on another entity form. It is important that the user have the “Append to” privilege on the entity that is referred to in the lookup so that it can set the values for the lookups of this entity on any other form. For eg: Account ha...

I get asked about many-to-many (a.k.a. N:N) relationships more than just about any other single topic, so here’s a summary of how they work in Dynamics CRM 2011. I’ll review both “native” and “manual” N:N’s, using a simple Association to Contact relationship to illustrate. This is a classic many-to-many: each association should be able to have multiple contacts associated with it, and each contact should in turn be able to be associated with many associations. Native N:N Relationships With native N:N relationships, you open up an entity for customization, click the N:N relationships link, and click the  New Many to Many Relationship  button and select the entity to create the relationship to. For the Association to Contact N:N relationship, I’ll start from the Association entity: In the previous figure, notice that Do no Display is selected in the Display Option for each side. I only show that to illustrate a point: what this will do is prevent the relationship from be...