You need to sign in to do that
Don't have an account?
goabhigo
Email to User and Manager when Manager is changed
I have a Hierarchy (a lookup to User) field in User - it is called Mentor. The requirement is simple, when I change the Mentor, an email should be sent to new Mentor and the User.
I have created email field, populated the same using workflow. Then I created an email alert, to send the email to user's email and this newly created email field.
Output is surprising - The email is directed to Mentor and mentor user's mentor is shown!!
To make is clear here is the example:
Keir is the Mentor of Abhilash. The admin changes the mentor, to Bob. Now ideally Bob and Abhilash should get an email about this change. But what happens is Bob gets email as below:
Dear Bob,
Your mentor has been changed/mentee has been assigned.
Mentor: Buzzard
Mentee: Bob
Is there any way to do this without writing apex trigger?
--
Abhilash.
I have created email field, populated the same using workflow. Then I created an email alert, to send the email to user's email and this newly created email field.
Output is surprising - The email is directed to Mentor and mentor user's mentor is shown!!
To make is clear here is the example:
Keir is the Mentor of Abhilash. The admin changes the mentor, to Bob. Now ideally Bob and Abhilash should get an email about this change. But what happens is Bob gets email as below:
Dear Bob,
Your mentor has been changed/mentee has been assigned.
Mentor: Buzzard
Mentee: Bob
Is there any way to do this without writing apex trigger?
--
Abhilash.
Please go through this article (https://help.salesforce.com/apex/HTViewHelpDoc?id=merge_fields_email_templates.htm&language=en) for your reference. Highlighting the one which solved:
So, I had used {!User.Name}, instead I had to use {!Target_User.Name}.
Trust someone who comes across this issue will get help from this.
--
Abhilash
All Answers
Please go through this article (https://help.salesforce.com/apex/HTViewHelpDoc?id=merge_fields_email_templates.htm&language=en) for your reference. Highlighting the one which solved:
So, I had used {!User.Name}, instead I had to use {!Target_User.Name}.
Trust someone who comes across this issue will get help from this.
--
Abhilash