81 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

Dynamics CRM 2011 Goals - Sales Goals

This will show you how to create a sales goal suitable for an individual sales rep, and then how to create a team goal. The team goal demo illustrates the important and initially confusing concept of a "Rollup Query".
 

 

Opportunity : Opportunity Status

Opportunity records can be closed in one of two ways:

  • Close as Won indicates a successful sale, and changes the status value to Won.
  • Close as Lost indicates a decision not to buy, and changes the status value to Lost.

 

Opportunity records with status values of either Won or Lost are read only. If closed opportunities require changes, they can be reopened.

How to Put a Product Mix on a Dynamics CRM 2011 Dashboard

Learn how to create a product mix graph and place it in your dashboard in Microsoft Dynamics CRM and Dynamics CRM Online.

Microsoft CRM 2011 -- Creating Charts

[Job] - TCS: MS Dynamic CRM Functional Consultant, India

Company: Tata Consultancy Services

Location: Kolkata, India

 

  

 

BACHELOR OF COMPUTER APPLICATION, BACHELOR OF COMPUTER SCIENCE, BACHELOR OF ENGINEERING
Enterprise Solutions and Frameworks - Microsoft Dynamics CRM
Candidate should be a MS Dynamics CRM Functional Consultant, with good knowledge on Dynamics CRM entities , workflows , configurations , customization development , integrations development; Sound in core NET technology and SSRS; Proficient on CRM Functional areas in Sales Force Automation , Marketing automation and Service management functionality

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 access the default ribbons?

  1. SDK\Resources\ExportedRibbonXml or
  2. RetrieveApplicationRibbonRequest
    1. This message retrieves the core application ribbons including the entity template.
  3. RetrieveEntityRibbonRequest
    1. This message retrieves the ribbon definition used for a specific entity.

Microsoft Dynamics CRM Spring '14 Queue Enhancements

What meant by Queue in CRM

  1. Queue is a central location to monitor the progress, prioritise user work and change status of activities. Or collection of queue items.
  2. It is used to processing sales orders, responding to service calls, pre validation of consumer services, tracking of emails and product information to prospect clients.
  3. The following information pertains to queues:
    1. All customizable entities, business or custom, can be enabled for queues.
    2. A default queue is automatically created for each new user or team.
    3. You can assign and share queues with other users and teams to improve collaboration efforts.
    4. Queues can be enabled for workflows and audit. This helps improve productivity and track the entity and attribute data changes for future analysis and reporting.
    5. A queue contains information about the user who is working on a particular queue item. This helps you manage your resources more efficiently and helps to prevent duplication of work.
    6. A queue can contain multiple entity types, such as tasks, emails, or cases.
    7. A queue is user-owned or team-owned. This provides a high level of security by allowing data access to specified users and teams instead of to the whole organization.

On Demand Workflows and Security Roles: CRM4

Color Grid for Dynamics 365

Color Form for Dynamics 365