Make a Lead for a key employee who leaves Account

(0) Share

Report

Posted on by Community Member Microsoft Employee

I'm making a Workflow where when a key employee leaves an Account a Lead is created for that Contact. However, all the workflows I've tried can't make a Lead from the old employee, only the new one that fills the role. How have you made this work? Thanks!

eg: Ana is the Director of Account X. Ana leaves Account X. Make new Lead for Ana.

*This post is locked for comments

All responses (15)

Answers (0)

Aric Levin 30,188 on at

Like (0)

Report

RE: Make a Lead for a key employee who leaves Account

Try to make the name field not required, to see if it works. If it does, we can figure out a different way.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Make a Lead for a key employee who leaves Account

Name field is generated from the old Medical Director, which is a Contact Lookup field. So the Name is that of a Contact, the previous MedDir. It's pulled during the step, Make Lead, which happens after the new MedDir is put in place. (But the workflow acts before the change is made-- that's how it pulls the old MedDir Contact...as per your helpful suggestion). Does that answer your Q?
Aric Levin 30,188 on at

Like (0)

Report

RE: Make a Lead for a key employee who leaves Account

Yes, but that still doesn't solve the name issue.

How is the Name field generated, and at what point in time.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Make a Lead for a key employee who leaves Account

I should have included this part, further down:
Aric Levin 30,188 on at

Like (0)

Report

RE: Make a Lead for a key employee who leaves Account

That is most likely because it is read-only on the actual form.

There must be some logic that it gets generated, but the question is when.

The solution that you can do, is open the Form, change it to Non Read-Only and Publish the changes.

Go back to your workflow and it should not be read-only anymore

Put a value in it and Save your workflow.

Test it.

You can set it to read-only again on the form after the Workflow has been published/working.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Make a Lead for a key employee who leaves Account

The name field is configured like this-- when I edit the workflow, it does not allow me to input values for the Name field.
Aric Levin 30,188 on at

Like (0)

Report

RE: Make a Lead for a key employee who leaves Account

Hi Talia,

There is one thing that I saw that might be a cause, but am not sure.

It looks like you name field is required, but (read-only/not entered).

How is that field generated?
Community Member Microsoft Employee on at

Like (0)

Report

RE: Make a Lead for a key employee who leaves Account

Hey Aric and Francesco-- I wonder if either of you have a lead on what's wrong now:

This workflow creates a lead when the key roles change, but this also happens when I create a new Account. Do you have thoughts how to exclude the situation of first creation? These dud leads have no Contact or Account linked, just a Topic, because the fields were previously blank, of course (pre-Account record creation).

Because of this issue, upon upload of Accounts, I currently have 2000 dud leads!

Thanks a ton.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Make a Lead for a key employee who leaves Account

I agree it's strange... The workflow has worked for the new* APRN Contact but my issue is getting it for the old one... There are no child workflows. This is the only custom workflow created for this entity.

Here is the main workflow

and the triggering field:

And create Lead instructions:

Thanks so much for your responses so far!
Aric Levin 30,188 on at

Like (0)

Report

RE: Make a Lead for a key employee who leaves Account

Are you running multiple workflows and calling child workflows, or is everything in a single workflow?

Can you possibly post an image of your workflow steps? I am not sure where your problem is.

There is no reason for Workflow to Work asynchronously and not work in real-time unless it is data related, where the data is not there when you run it in real-time, such as in the case of Pre-Event execution.