Timeline for Automatically map Account Look up field on Lead in Salesforce
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Sep 28, 2016 at 22:08 | history | suggested | Asad Malik | CC BY-SA 3.0 | corrected myLead with newLead |
| Sep 28, 2016 at 21:39 | review | Suggested edits | |||
| S Sep 28, 2016 at 22:08 | |||||
| Sep 28, 2016 at 20:00 | comment | added | Asad Malik | Error: Compile Error: Variable does not exist: myLead.CompanyName at line 13 column 52 | |
| Aug 3, 2015 at 16:01 | comment | added | James | Glad it helped! | |
| Aug 3, 2015 at 15:50 | comment | added | San | @James : Thanks for the clarification on '=' and 'IN' when used for binding variables. | |
| Aug 3, 2015 at 13:06 | comment | added | James | This example can be greatly reduced. I intentionally did so to help illustrate the process and guide mike inuitively so he has a framework for future challenges. Also, '=' and 'IN' are equivalent when using binding variables. developer.salesforce.com/docs/atlas.en-us.apexcode.meta/… | |
| Aug 1, 2015 at 13:56 | comment | added | San | @James : If I a not wrong, we can avoid the statement List<Lead> leadsToAddAccountId = new List<Lead>(); . And one more correction while Query Account object WHERE condition should be with "IN" not "=". | |
| Aug 1, 2015 at 13:55 | history | answered | San | CC BY-SA 3.0 |