95

After applying the latest Product Update related to the December 2012 Service Update for Microsoft Dynamics CRM Online, users may notice that the lead Qualify button no longer presents the Convert Lead dialog box. A new Opportunity is being created an opened, there is no chance to get the old behavior:-(

Described in KB-Article KB 2808201 (http://support.microsoft.com/kb/2808201)

We - and much more important our customers - want this functionality back!

Category: General
STATUS DETAILS
Planned
October 2019
Ideas Administrator

Thank you for your feedback!

 

Would like to update you that this capability is planned for 2019 Release Wave 2 in October.

Please refer to 2019 Release Wave 2 documentation for Dynamics 365 for Sales for details.

 

Sincerely,

Paramita Chatterjee

PM, Microsoft.

Comments

T

Thank you all for the comments. This is an understandable suggestion which we are considering in our roadmap.

Sincerely,
Daniel Dallala
PM, Microsoft

Category: General

T

This has been requested for more than 2 years no, still we have no feedback from MS teams and I do not think this is part of the upcoming CRM2016 release ?

On my installation i had to do a custom Dialog to allow users to choose what entity they want to convert their lead to (Account and/or Contact and/or Opportunity). This is a particularly bad UI experience for them, they have to go to the sub-menu, select a dialog to get that ugly visual-basic-like frame and convert their lead.

Any proper integration within the new CRM UI would be greatly appreciated.

Category: General

T

It's really hard to fathom why this was done. If it isn't already resolved in newer versions (we're on prem, so we're behind, obviously), you ought to devote some resources to it. It makes the lead form essentially non-workable, IMO. The gymnastics we have to do to stop this behavior from happening shouldn't really be required. It diminishes the value of Dynamics CRM immensely.

Category: General

T

More duplicates to link to this thread:
https://connect.microsoft.com/dynamicssuggestions/Feedback/Details/779260

and a new one:
https://connect.microsoft.com/dynamicssuggestions/Feedback/Details/920180

Any update from the product team on this? This comes up a lot, and customers need some control. This could be a dialog box, or an organization setting, or an OOB field on the Lead entity that controls whether or not an Opportunity should be created.

A field "CreateOpportunity" on the Lead entity would be good, as a yes/no/null option set field.
So if the users should be given control, this can be exposed on a form or in a BPF, and the field can be set to an appropriate default value. Please use an option set so it can be left null by default and made business required and/or configured as a required step in a BPF - so please don't use a two options field type because this would remove the ability to control how and when the field is required. (Configuring a two options field as a required step in BPF means it must be set to a value of 1 before proceeding. The intention here is to force the user to answer the question, yes OR no, rather than leaving it null.)
This field could have a different default value set, with the field left off the form in order to enforce an organisation-wide stance of always or never creating an opportunity.

Category: General

T

Thank you for your feedback. This is a great suggestion, and we will consider this in our roadmap.

======================
Prashanth GanapathyRaj
PM, Dynamics CRM, Microsoft
======================

Category: General

T

Thank you guys for the feedback. We'll be taking this into consideration as we plan our future roadmap.

Category: General

T

There are to primary focuses of using leads -- 1) determine if the person/organization is a qualified opportunity --meaning they have a match for a specific product or service, have a budget, a timeline, etc. 2) determine if a person/organization is a good fit for your organization.

In some sales processes, if they are a good fit for your organization, but you do not yet have a relationship with them, you might bring them into your database as an Account and Contact (with Relationship Type Prospect, for example), so that you can continue to track the relationship and build out a bigger profile on the prospect as you get to know them. For example, perhaps you are in contact with multiple people at the organization and/or you have additional profile fields on the Account that you do not track on the simple lead form.

This is the business reason for needing to be able to convert a lead WITHOUT creating an Opportunity. Additionally, your only reason for converting a lead may be to merge a duplicate or add a contact for an existing company that somehow came in as a lead. That being said, the current design being released in CRM 2013 is going to be very problematic for organizations who do NOT always create an Opportunity when converting. That is why this request is CRITICAL.

Category: General

T

Also note near-duplicate feedback here:
https://connect.microsoft.com/dynamicssuggestions/feedback/details/779260/convert-lead-dialog-box-no-longer-appears-during-lead-qualification

Category: General

T

Voting up for Adam's suggestion below.

Category: General

T

Personally I don't care how the functionality is brought back - a popup dialog box may not work (eg on iPad), but an in-form set of choices is needed. Whether this is via bit fields* which can be displayed as part of the process definition, or in a similar way to the current Polaris method for Case Resolution, customers need the Lead qualification process to provide this functionality:
- If an existing Account or Contact is specified, use them (ignoring any checkbox which says to create a new one)
- If an existing Account xor Contact is specified, allow user to choose to create the other entity record if they want. Especially in B2B scenarios, a Lead often turns out to be an additional Contact for an existing Account. It should create the new Contact and link them to the chosen existing Account as Parent Customer
- If neither is specified, allow user to decide if they want a new Account and/or Contact
- Whatever is specified, allow user to choose whether an Opportunity should be created.
- Ideally, allow user to choose whether the customer for the Opportunity is the Account or Contact (pre-existing or new), again using a bit field so this may have a default set by admin. Override this value when not applicable (eg user chooses a pre-existing Contact, no Account and opts to not create a new Account either, set Contact as Opp customer regardless of this value)

*these should be actual bit fields defined in the Lead entity, enabling a system customiser to set the default to an appropriate value for the business process. Checkboxes would work well for most of these, a radio button pair may be better for the choice of Opportunity customer type. These fields will also show what choices a user made at the point of Qualification, often necessary for checking back on the origins of a record.

Category: General