87 Wednesday, December 21, 2016 |
Suresh Maurya
Dynamics CRM Consultant at IBM

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.

Dynamics CRM 2011 : Goal Metrics and Goals

Retrieve Records In Dynamics CRM Using QueryExpression

Following example demonstrates how to retrive records in dynamics crm using QueryExpression.

Connection string

<connectionStrings>
<add name="connection" connectionString="Url=https://org.crm.dynamics.com; Username=user@org.onmicrosoft.com; Password=password;"/>
</connectionStrings>

 C#

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

namespace CrmSampleCodes
{
class Program
{
static void Main(string[] args)
{
IOrganizationService _service = new OrganizationService("connection");

// Create query using QueryExpression.
QueryExpression queryExpression = new QueryExpression("account");
queryExpression.ColumnSet = new ColumnSet("name", "address1_city", "emailaddress1");

queryExpression.Criteria.AddCondition("address1_city", ConditionOperator.Equal, "Redmond");

// Query passed to service proxy.
EntityCollection retrieved = _service.RetrieveMultiple(queryExpression);

System.Console.WriteLine("Query Using QueryExpression");
System.Console.WriteLine("===============================");

// Iterate through returned collection.
foreach (var c in retrieved.Entities)
{
System.Console.WriteLine("Name: " + c.Attributes["name"]);

if (c.Attributes.Contains("address1_city"))
System.Console.WriteLine("Address: " + c.Attributes["address1_city"]);

if (c.Attributes.Contains("emailaddress1"))
System.Console.WriteLine("E-mail: " + c.Attributes["emailaddress1"]);
}
System.Console.WriteLine("===============================");
}
}
}

Order Management : Fields on the Order Form contd.

  • Shipping Information
    • Shipping Method: Shipping method for deliveries sent to this address.
    • Payment Terms: Payment terms to indicate when the customer needs to pay the total amount.
    • Freight Terms: Freight terms to make sure shipping charges are processed correctly.
  • Addresses
    • Bill to Address: Complete Bill To address.
    • Ship To: Whether the products included in the order should be shipped to the specified address or held until the customer calls with further pick-up or delivery instructions.
    • Ship To Address: Complete Ship To address.
  • Sales Information
    • Opportunity: Related opportunity linking the data for the order and opportunity for reporting and analytics.
    • Quote: Related quote linking order data and quote data for reporting and analytics.
    • Potential Customer: Customer account or contact providing a quick link to additional customer details, such as account information, activities, and opportunities.

Dynamics CRM 2011: Sales Force Automation

[Job] - L&T : Microsoft Dynamics CRM Sr. Developer, United States

Company: L & T Infotech

Location: Farmington, CT, United States

Job Code: 14400
Title: Microsoft Dynamics CRM Sr. Developer
Location: Farmington, CT, United States


Description:

Language Required

  • Spanish & English or
  • Portuguese & English Or
  • Spanish, Portuguese & English

Skills

1.Education – B.E., B. Tech, MCA, Around 5 to 8 yrs or more years of relevant experience.
2.Certified professional (Configurations, customizations and Extensions) and having experience in
Installation (considering accessing via Microsoft Outlook and Mobile), customizations in On-Premise, Online model (considering best practices within Microsoft Dynamics CRM), and customization of reports in On-Premise and Online model. {Experience in Online model a must}


1.Experience in Integration with third party applications.
2.Working knowledge of Microsoft SQL Database, Windows Server Operating System, Active Directory and Active Directory Federation Services.
3.Experience in SSIS (SQL Server Integration Services) and aware of sizing of hardware and software would be an added advantage
4.Project Lead experience
5.Understanding of standard available sales, marketing and service module functional flows
6.Experience in developing reports in SSRS (SQL Server Reporting Services), xml based reports a must
7.Awareness and working experience of various technologies like HTML, CSS, SOAP, REST, Silverlight, Angular JS

Required Experience (Same as Relevant Experience)

1.5 to 8 yrs or more years of MS CRM Sr. Developer / Technical experience

Job Responsibilities

1.Technical consultant with MS CRM background, having worked on the MS CRM product extensively and done 4 - 6 end to end implementations.
2.Worked on CRM 2013 version onwards until latest version.
3.Also having done projects on premise and cloud, support, upgrade and migrations.
4.Aware of mobility in MS CRM CRM and access of MS CRM via Outlook - Online and Offline.
5.Knows the MS Sure Step methodology well; able to articulate and understand the pain points of customer.
6.Design the solution, configure and customize to address the pain points and deliver it is one of the key responsibilities.
7.Design, develop solutions, identify bugs and resolve the issues/bugs.
8.Preparation of technical related documentations.
9.Should be customer facing with excellent analytical and communication skills.
10.Lead a team of resources, allocation and estimation of tasks.
11.Troubleshooting any issues.

Key Skills: Microsoft Dynamics CRM Sr. Developer
Education Qualification: Associate Degree

Microsoft Dynamics CRM 2013 for Tablets - Offline

SampleDataImportSteps

Microsoft Dynamics CRM: User Experience is Critical

Microsoft Dynamics CRM 2011: Installing and Configuring the Outlook Client

What is meant by sandbox? How it is differentiate between standard environments?

  1. Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online support the execution of plug-ins in an isolated environment. In this isolated environment, also known as a
  2. Use of the full power of the Microsoft Dynamics CRM SDK to access the web services. Access to the file system, system event log, network, and more is prevented in the sandbox.
  3. It is more secure, supports run-time monitoring and statistics reporting, and is supported on all Microsoft Dynamics CRM deployments.
  4. In registration Sandbox, known as partial trust:
  5. Outside sandbox is full trust: Full trust is supported for on-premise and Internet-Facing Microsoft Dynamics CRM deployments.
  6. Microsoft Dynamics CRM Online deployment, plug-ins must be registered in the sandbox (partial trust) because no full trust run-time environment is supported. Partial trusts are also supported for on-premise deployments.
  7. Sandboxed plug-ins can access the network through the HTTP and HTTPS protocols.
  8. Access to localhost (loopback) is not permitted.
  9. IP addresses cannot be used. Plug-ins must use a named web address that requires DNS name resolution.
  10. Anonymous authentication is supported and recommended.
  11. Full trust is supported for on-premises and internet facing Microsoft Dynamics CRM deployments. For a Microsoft Dynamics CRM Online deployment, plug-ins must be registered in the sandbox (partial trust) where they are isolated as previously described.

Color Grid for Dynamics 365

Color Form for Dynamics 365