Hi, When I try to convert a Lead to a Company or Company and opportunity I get the following workflow error. This is when I give a existing company name in the company name section.
But when I give a new company name under company category (as in the below image) it allows to convert that lead to a Company and opportunity.
How to fix this issue? Could anyone help me on this.
Hi @jmatias here the issue comes when we try to create do the conversion with a existing company, if we try to do the conversion with a new company as in the below image there wo nât be any workflow error.
Thatâs ok - that workflow should only be used when the Account/Contact does not exist yet - so, letâs say, the company already exists, that workflow canât be triggered because the Lead is already converted.
We are talking about the workflow âLead to Account and Opportunityâ, right?
Hi @jmatias what do you mean by that. Are you saying the process of creating and converting a lead should be for a new company should be there right. If an existing company is given then that means the lead is already converted. Is that what you mean?
If Iâm correct, that workflow should only be triggered on the lead page. Because it relates the data in the workflow with the data on the lead itself;
Where do you have that automation block?
And yes, if the lead is already converted - The workflow will trigger an error - But a different one, it usually says something like âThis lead is already convertedâ.
To resume things: you didnât change the module âLeadsâ âOpportunityâ & âAccountâ, right? The fields are the same as when we install Corteza?
Strange - I just created a blank Corteza instance and the workflow has gone through without alerts or problems. Have you already saved the Lead when you try to convert it? Or you havenât clicked on âSaveâ yet when trying to execute the workflow?
Hi @jmatias I execute the workflow after I save the Lead and this issue comes when we give existing company in the company details section, when a new company is given there is no issue in workflow. (As shown in the above with screen shots).
Did you add any custom changes to the modules? Any validators or such things?
Since the error indicates you changed something in the module/workflow configuration that is now causing this.
If you didnât change anything then its quite strange and an edge case. So we need server logs and as much actual info as possible.