66 Wednesday, January 4, 2017 |
Suresh Maurya
Dynamics CRM Consultant at IBM

Lead Management: Lead To Opportunity Process Ribbon

With the process ribbon, users can follow a step-by-step process to make sure the correct information is gathered for different record types.

Stages and Steps in Lead to Opportunity Process

  • Qualify
    • Existing Account
    • Existing Contact
    • Purchase Timeframe
    • Estimated Budget
    • Purchase Process
    • Identify Decision Maker
    • Capture Summary

Microsoft Dynamics CRM 2013 Customization New Features - Phone Number Format

Associate Records In Microsoft Dynamics CRM Using Early Bound

Associate Method

To associte records in Microsoft Dynamics CRM use IOrganizationService.Associate(entityName, Guid, Relationship, EntityReferenceCollection) method.

Parameters

Name Type Comment
entityname String Entity logical name
guid Guid The ID of the record to which the related records are associated.
relationship Guid The name of the relationship to be used to create the link.
relatedEntities Guid A collection of entity references (references to records) to be associated..

Output

Void

This method is implemented by OrganizationService class and OrganizationServiceContext generated in previous chapter.

Using Early Bound 

Following example demonstarates how to associate a contact with three accounts in Microsoft Dynamics CRM using early bound

C#

// Associate the accounts to the contact record.

// Create a collection of the entities that will be 
// associated to the contact.
EntityReferenceCollection relatedEntities = new EntityReferenceCollection();
relatedEntities.Add(new EntityReference(Account.EntityLogicalName, _account1Id));
relatedEntities.Add(new EntityReference(Account.EntityLogicalName, _account2Id));
relatedEntities.Add(new EntityReference(Account.EntityLogicalName, _account3Id));

// Create an object that defines the relationship between the contact and account.
Relationship relationship = new Relationship("account_primary_contact");


//Associate the contact with the 3 accounts.
_service.Associate(Contact.EntityLogicalName, _contactId, relationship,
    relatedEntities);

Console.WriteLine("The entities have been associated.");

//Disassociate the records.
_service.Disassociate(Contact.EntityLogicalName, _contactId, relationship,
    relatedEntities);

Multiple Ways To Connect To Microsoft Dynamics CRM Using Organization Service, Proxy and Context

Microsoft Dynamics CRM can be connected programmatically using following:

  • Organiation Service
  • Organization Service Proxy
  • Organization Service Context 

Using Organization Service

Simplest way of connecting to Microsoft Dynamics CRM is using OrganizationService.

OrganizationService constructor can take connection string or CrmConnection object as parameter.

public OrganizationService(string connectionStringName);
public OrganizationService(CrmConnection connection);

Method 1

Pass the connection string name to constructor.

IOrganizationService service = new OrganizationService("connection");

Entity entity = new Entity("account");
entity.Attributes["name"] = "This is my sample account";

service.Create(entity); 

Method 2

In CrmConnection constructor pass the connection string name, which further should be passed in OrganizationService constructor.

CrmConnection connection = new CrmConnection("connection");
IOrganizationService service = new OrganizationService(connection); //System.configuration

Entity entity = new Entity("account");
entity.Attributes["name"] = "This is my sample account";

service.Create(entity); 

CrmConnection requires following additional assembly to be referenced.

System.configuration 

Method 3

Use CrmConnection.Parse method to create CrmConnection object and pass that to OrganizationService constructor.

string connString="Url=http://crm.contoso.com/xrmContoso; Domain=CONTOSO; Username=jsmith; Password=passcode;";

CrmConnection connection = CrmConnection.Parse(connString);
IOrganizationService service = new OrganizationService(connection); //System.configuration

Entity entity = new Entity("account");
entity.Attributes["name"] = "This is my sample account";

service.Create(entity);

Using Organization Service Proxy

OrganizationServiceProxy class provides a proxy to connect to Microsoft Dynamics CRM.

Use following constructor to create the proxy.

public OrganizationServiceProxy(
Uri uri,
Uri homeRealmUri,
ClientCredentials clientCredentials,
ClientCredentials deviceCredentials
)
Parameter Description
uri The URI of the organization service.
homeRealmUri

This parameter is set to a non-null value when a second ADFS instance is configured as an identity provider to the ADFS instance that Microsoft Dynamics CRM 2011 has been configured with for claims authentication. The parameter value is the URI of the WS-Trust metadata endpoint of the second ADFS instance.

Pass null in this case

clientCredentials The logon credentials of the client.
deviceCredentials

The Windows Live ID device credentials.

Pass null in this case

Following sample code connects to Microsoft Dynamics CRM using OrganizationServiceProxy

Uri oUri = new Uri("https://yourorg.api.crm5.dynamics.com/XRMServices/2011/Organization.svc");
//** Your client credentials
ClientCredentials clientCredentials = new ClientCredentials();
clientCredentials.UserName.UserName = "YourAccount.onmicrosoft.com";
clientCredentials.UserName.Password = "YourPassword";

//Create your Organization Service Proxy
OrganizationServiceProxy _serviceProxy = new OrganizationServiceProxy( oUri, null, clientCredentials, null);

//** Now simple use Entity and create a sample account
Entity entity = new Entity("account");
entity.Attributes["name"] = "This is my sample account";

//use the service proxy to create the entity object
_serviceProxy.Create(entity);
}

Using Organiation Service Context

OrganizationServiceContext is alternative to OrganizationServiceProxy to connect to Microsoft Dynamics CRM programmatically.

To create OrganizationServiceContext object pass IOrganizationService object to constructor.

IOrganizationService service = new OrganizationService("connection");
OrganizationServiceContext context = new OrganizationServiceContext(service);

Entity entity = new Entity("account");
entity.Attributes["name"] = "This is my sample account";

context.AddObject(entity);
context.SaveChanges();

context.AccountSet.ToList().ForEach(a => Console.WriteLine(a.Name));

OrganizationServiceContext class can be generated by the code generation tool (CrmSvcUtil.exe). 

 

Activity Feeds Overview

Quick overview of activity feeds and social network capabilities within Microsoft Dynamics CRM 2011

RIBBON COMMAND ELEMENTS

The <CommandDefinition> (RibbonDiffXml) element defines a command in the ribbon. The Id attribute specifies a unique identifier for the command that can be referenced by ribbon control elements by using the Command parameter.

A ribbon command defines three things:

  • Enable Rules: Specifies when a specific ribbon control will be enabled.

When configuring Ribbon elements you can define specific rules to control when the ribbon elements are enabled. The <EnableRule> (RibbonDiffXml) element is used as follows:

  • Use the /RuleDefinitions/EnableRules/EnableRule element to define rules controlling when the ribbon element should be enabled.
  • Use the /CommandDefinitions/CommandDefinition/EnableRules/EnableRule element to associate specific enable rules to a command definition.
  • Display Rules: Specifies when a specific ribbon element will be visible.

When configuring ribbon elements, you can define specific rules to control when the ribbon elements will display.

  • Use the /RuleDefinitions/DisplayRules/<DisplayRule> (RibbonDiffXml) element to define rules controlling when the ribbon element should be displayed.
  • Use the /CommandDefinitions/CommandDefinition/DisplayRules/<DisplayRule> (RibbonDiffXml) element to associate specific display rules to a command definition.
  • Actions: Specifies what code will execute when a ribbon control is uses.

Define the actions to be performed by a ribbon control in a <CommandDefinition> (RibbonDiffXml) element together with rules that control whether the control is enabled or visible in the ribbon.

A Ribbon control can perform two types of actions and may include multiple actions:

  • JavaScript Functions: A <JavaScriptFunction> (RibbonDiffXml) element references a function defined in a Script Web resource.
  • Open a URL: The ribbon opens a URL using the value from an Address attribute in the <Url> (RibbonDiffXml) Additional parameters can pass information about how what querystring parameters are passed and the mode in which the window opens.
    You have several options to pass parameters to a URL using the ribbon. For more information, see Pass Parameters to a URL By Using the Ribbon.

Creating Custom Entities - Microsoft Dynamics CRM 2011

This video provides an overview of how to extend Dynamics CRM 2011 to include additional functionality or business processes.

In this overview we show how you can add a custom entity to track Samples that you want to send out to customers.

Office 2010 / Microsoft Dynamics CRM Demo -- Coordinating Sales and Customer Support (Part 2 of 2)

In this demonstration, you will see how the user, such as an account manager, can easily access customer information from a central dashboard in SharePoint Server 2010, and also seamlessly access customer data stored in Microsoft Dynamics CRM.

[Job] - Microsoft : PREMIER FIELD ENGINEER - DYNAMICS CRM | United States

Company: Microsoft

Location: United States

This role will require you to accumulate, maintain, and demonstrate technical knowledge of Microsoft Dynamics CRM and related Microsoft products. You will apply this knowledge to each customer through proactive and preventative work to promote organizational health and reduce risk at their site. This role requires the ability to acknowledge opportunities and solve real world customer business problems by leveraging Microsoft Business Solutions Applications and technologies. Strong product knowledge of Microsoft Dynamics CRM is required; communication, and customer relations skills are needed to complement product and technical knowledge.

Minimum Requirements: Solid understanding of client/server, networking, and Internet technologies fundamentals. Candidate must possess strong knowledge and demonstrated technical proficiency in Windows Server and Microsoft client products, SQL Server, and Dynamics CRM. In addition, the successful candidate must possess knowledge of DNS, Exchange Server and Active Directory as it relates to successful implementations of Dynamics CRM. Five or more years of experience in systems development, network operations, and software support or I.T. consulting or five or more year’s industry experience with Microsoft products are required. Effective learning skills, ability to work well in a team environment and strong problem-solving skills are also critical to success in the role.

Goal: To provide high quality technical support reactively and proactively to a designated set of strategic Microsoft customers.

Responsibilities: Primary responsibilities include providing on-site and remote technical support solutions for customer service delivery and availability, while ensuring satisfaction with Microsoft software. The successful candidate will be capable of providing field technical support and proactive service presence for groups in the Microsoft Services organization, including but not limited to Premier and Professional Support, Microsoft Consulting Services, and escalation engineers. The Premier Field Engineer acts as the primary technical contact, providing customer visibility, advanced technical troubleshooting support and problem resolution for corporate customers, including issues escalated to the highest levels of management. The candidate will provide technical support including product technical training onsite, as well as via telephone, and electronic media. Candidate must be able to manage hot issues by setting customer expectations, devising and implementing action plans, and professionally communicating to all parties involved.

Overnight travel may be required. Travel requirements vary regionally and could be in the range of 30-75%. Candidates must possess current passport or be able to obtain passport within 90 days of hire. The candidate should already have current US work authorization and live within US and be willing to relocate if needed.

Qualifications: 4-year technical degree or equivalent work experience, 5+ year’s customer experience. Ideal candidate would have 2+ years of experience with the Microsoft Dynamics CRM product. MCSE strongly preferred, but not required at hire. Candidate must possess the ability to effectively communicate with customer managers and executives on technical and business issues. Strong organization, communication, problem solving, time management, and negotiation skills.

Scania benefiting from Microsoft CRM

Microsoft CRM from ConsultCRM gets results: See how this global enterprise achieved 100% growth in sales and fourfold increase in marketing performance.

 

Content Marketing with Microsoft Dynamics Marketing

Color Grid for Dynamics 365

Color Form for Dynamics 365