Microsoft Dynamics CRM (Archived)

Automatically creating account record when Lead is qualify

(0) Share

Report

Posted on by Florence Caysip

415

Hi,

How do I prevent creation of Account record when I qualify a Lead in the new form (Polaris)?

Note: In previous version, there's an option to choose whether you want to create an Account, Contact and Opportunity record.

Thanks!

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (1)

Verified answer

Community Member on at

Like (1)

Report

Hi Florecen Caysip, good morning

My name is Andrés Guzmán, I'm glad to help you

This option to qualify a Lead changed for this lastest versión:
The Convert Lead dialog box no longer appears during lead qualification in Microsoft Dynamics CRM Online

Have a great day,

Regards,

Was this reply helpful? Yes No
Florence Caysip 415 on at

Like (0)

Report

Thanks Andres!

Was this reply helpful? Yes No
Benjamin Rutledge 635 on at

Like (0)

Report

Andres,

Is there a reason Microsoft is forcing us to create all 3 entity records when qualifying a Lead? My company uses a process that specifies flowing from Lead to Account to Opportunity to Order. Is there going to be a way to alter the process flow for those of us who prefer the more flexible CRM?

Please advise,

Benjamin

Was this reply helpful? Yes No
Gateway Solutions 5 on at

Like (0)

Report

I also think it would be valuable to be able to create just some of the records, (for instance a new opportunity to an existing account.) This was existing functionality that users were used to having and built processes around.

Was this reply helpful? Yes No
Charlie Strack 100 on at

Like (0)

Report

The unilateral decision on the part of Microsoft to create contact, company, and opportunity is completely unacceptable. In the industry I work, where most important sales are to OEMs, lead qualification is the first step in a series of several steps towards having an opportunity, and often the opportunity comes much later in the process. Microsoft does not seem to understand that different selling environments have sales cycles that are substantially different, and the CRM needs to be flexible enough to handle these differences.

At this point, we've got very serious pressure from our management to provide IPad capability with our CRM. Polaris forms are mandatory for IPad compatibility, and thus the lead qualification process that Mircosoft is forcing may leave us with no alternative but to change our CRM software.

There needs to be a way to suppress creation of account, contact, and/or opportunity upon qualification of a lead, even if it is a default setting for our company's instance.

Charlie

Was this reply helpful? Yes No
AFT 235 on at

Like (0)

Report

I agree that forcing us to automatically create an opportunity when qualifying a lead is very inconvenient. What work arounds are there to prevent this. I usually just want an account and contact created when qualifying a lead early in the sales cycle.

Thanks in advance.

Was this reply helpful? Yes No
mynameisphong 35 on at

Like (0)

Report

Has anyone come up with a workaround for this or know of any updates?

This is what I've come up with (very manual and inconvenient).

1. Delete unwanted Opportunity after Lead Conversion.

2. Merge duplicate Account and Contact after Lead Conversion.

Thanks in advance.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

This is [another] completely ridiculous decision by the Dynamics product team. This along with making polaris forms default (however at least you can disable Polaris forms).

Considering the sales process is a core tenant of what CRM is supposed to be assisting with, it seems daft beyond comprehension that you would take a core component of it (Lead Qualification), and strip out any ability to control the process.

G

Was this reply helpful? Yes No
Suggested answer

Kathryn Warner on at

Like (0)

Report

For my company, we wanted the Opportunity Record, but not the perpetual new Contact.

Assuming the user flags the lead with the existing contact record, I created a workflow that runs when the lead is qualified.

1. The workflow checks to see if the contact look up is populated on the lead

If it is, it updates the contact on the opportinity with that contact record.

2 Then I update the parent contact record (the one automatically created) to an inactive status.

3. I debated on going back to lead and changing the parent contact id (I believe to do this, I would have to mark the lead as open in the workflow, update the parent contact id, then re-mark the lead as Qualified.

In theory, I could then have a bulk delete job automatically delete the inactive contacts that were deactivated by the workflow.

I just wrote the workflow, and it seems to work. I would like to see others opinions of the downside of doing it this way. We enter leads for existing contacts all the time, so duplicate detection, as far as I can tell, won't work for us.

Was this reply helpful? Yes No
Michael Hammons on at

Like (0)

Report

We had the same frustration. Our approach was to use Campaign Responses. Once a Campaign Response is added to a lead, contact or account, one can use the "Convert Campaign Response" button to give you the features/options of creating an associated contact, account and opportunity record..similar to how it worked prior to the recent changes.

This is the form that is displayed when using Convert Campaign Response.

Was this reply helpful? Yes No