42 Saturday, May 28, 2016 |
Msxrmtools Publisher
Publisher at Msxrmtools

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.

Working offline with Dynamics CRM mobile apps

Thanks to Dynamics CRM mobile apps, you don't have to stop working just because the network does. In this video we'll show you how to set up and use CRM's offline experience. Network disruptions no longer matter. When you reconnect the app, everything you added offline will be there.

What is the difference between managed and un-managed solutions?

  1. A managed solution is a completed solution that is intended to be distributed and installed.
  2. An unmanaged solution is one that is still under development or is not intended to be distributed.
  3. Managed solutions can also be layered on top of other managed solutions.
  4. Any unmanaged customized solution component can be associated with any number of unmanaged solutions.
  5. Deleting a managed solution will uninstall all of the solutions components.
  6. Unmanaged solutions are references to customizable solution components in the organization.
  7. Think of unmanaged solutions as source code and think of managed solutions as compiled, versioned and signed assemblies.
  8. Unmanaged
    1. Add components.
    2. Remove components.
    3. Delete components that allow for deletion.
    4. Export and import the unmanaged solution.
    5. Export the solution as a managed solution.
  9.  Managed
    1. You cannot add or remove solution components in a managed solution.
    2. You cannot export a managed solution.
    3. Deleting a managed solution uninstalls all the solution components within it.
    4. After you generate a managed solution, you cannot install it in the same Microsoft Dynamics CRM organization that contains the unmanaged solution.

How to debug a Sandboxed Plug-in

  1. The Microsoft Dynamics CRM Sandbox Processing Service on the sandbox server.
  2. The sandbox host process monitors the sandbox worker process that is executing the plug-in.
  3. To disable the shutdown feature, set the following registry key to 1 (DWORD):

               HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM\SandboxDebugPlugins

Customer Service and Care: Microsoft Dynamics CRM

Classifying Accounts with Many-to-Many Relationships

Sometimes a single-valued picklist is sufficient to classify records like accounts in Dynamics CRM, but sometimes it's not. In this video I talk about why and how you might want to use many-to-many -- N:N for short -- relationships, and demonstrate how to implement them in Dynamics CRM 2011.

Microsoft Dynamics CRM 2011 Outlook Client Installation & Configuration troubleshooting

Create a Record In Microsoft Dynamics CRM Using Early Bound

Create Method

To create a record use IOrganizationService.Create(entitymethod.

Parameters

Name Type Comment
entity Microsoft.Xrm.Sdk.Entity Entity object to create

Output

System.Guid

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

Using Early Bound

Create an instance of an entity type.

Contact contact = new Contact()
{
FirstName = "Charles",
LastName = "Brown",
Address1_Line1 = "123 Main St.",
Address1_City = "Des Moines",
Address1_StateOrProvince = "IA",
Address1_PostalCode = "21254",
new_twittername = "Chuck",
Telephone1 = "123-234-5678"
};

pass it to the create method.

Guid contactId= _service.Create(contact);

 

Following example demonstrates how to create record in Microsoft Dynamics CRM using Early Bound 

C#

using Microsoft.Xrm.Client.Services;
using Microsoft.Xrm.Sdk;
using System;

namespace Msxrmtools
{
class Program
{
static void Main(string[] args)
{
//"connection" = connection string name from config file"
IOrganizationService _service = new OrganizationService("connection");

Contact contact = new Contact()
{
FirstName = "Charles",
LastName = "Brown",
Address1_Line1 = "123 Main St.",
Address1_City = "Des Moines",
Address1_StateOrProvince = "IA",
Address1_PostalCode = "21254",
Telephone1 = "123-234-5678"
};

Guid contactId = _service.Create(contact);

Console.Write(Contact.EntityLogicalName);
Console.Write(contactId);
}
}
}

Opportunity : Opportunity Form Fields

The opportunity form in Microsoft Dynamics CRM contains the following fields:

  • Topic: The opportunity’s interests. For example, if an existing customer called for details about a product, list the name of the product as the topic.
  • Contact: Lookup for a Contact record associated to the opportunity.
  • Account: Lookup for an Account record associated to the opportunity.
  • Purchase Timeframe: Timeframe for the potential sale of the sales opportunity.
  • Currency: Local currency for the record.
  • Budget Amount: Lead’s potential available budget.
  • Purchase Process: Whether an individual or committee will be involved in the purchase process.
  • Description: Text area for additional information for the opportunity.
  • Price List: The appropriate price list for organizations that use them. 

Upgrading Microsoft Dynamics CRM 2011 to Microsoft Dynamics CRM 2013

What is the purpose of plug in?

  1. Performing complex platform level data validation
  2. Performing auto-number generation
  3. Providing integration with other applications
  4. Executing complex business logic
  5. Data auditing and look up.
  6. Performing common database operations.

Color Grid for Dynamics 365

Color Form for Dynamics 365