Details about this thread
  • State Not Answered
  • Replies 2 replies
  • Subscribers 293 subscribers
  • Views 1154 views
  • Users 0 members are here
Related content from around SugarClub

Can you have required fields before converting a lead

MONIQUE MILLSON

How do you set up required fields when Converting a lead to an opportunity.

Our sales team will need to have a few fields required before they can convert it to an opportunity.

However, we do not want these fields to be required in the Leads module when creating a lead - only when converting a lead.

Thanks

Parents
  • 0

    Monique,

    Recommend you make those fields that are required on lead conversion, required fields in the Opportunities Module. This will ensure that on conversion, those fields must be completed before the opportunity can be created. (Opportunities will need to be set as required on conversion, which is usually the case anyway).

    For example, lets say you have a Lead Field for Build Area that is not required in the Leads Module. Create the same field in the Opportunities Module with exactly the same name, but make it required in the Opportunities Module.

    On Lead Conversion, the system will try to copy Build Area from the Lead to the Opportunity which is good if the Lead had the data filled in even if it was not required. As the field is a required field in Opportunities it will appear and require completion before the Opportunity can be created. (the system will try to copy from the Lead if the Lead has a Build Area).

    If required, a workflow could be added to copy the Opportunity Build Area field back to the Lead.

    Hope that I understood the question correctly and this helps.

    Regards

    Greg Barrass 

Reply
  • 0

    Monique,

    Recommend you make those fields that are required on lead conversion, required fields in the Opportunities Module. This will ensure that on conversion, those fields must be completed before the opportunity can be created. (Opportunities will need to be set as required on conversion, which is usually the case anyway).

    For example, lets say you have a Lead Field for Build Area that is not required in the Leads Module. Create the same field in the Opportunities Module with exactly the same name, but make it required in the Opportunities Module.

    On Lead Conversion, the system will try to copy Build Area from the Lead to the Opportunity which is good if the Lead had the data filled in even if it was not required. As the field is a required field in Opportunities it will appear and require completion before the Opportunity can be created. (the system will try to copy from the Lead if the Lead has a Build Area).

    If required, a workflow could be added to copy the Opportunity Build Area field back to the Lead.

    Hope that I understood the question correctly and this helps.

    Regards

    Greg Barrass 

Children
No Data