Timeline for Saving Opportunity and related Contact from single Visualforce page
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 24, 2015 at 0:40 | comment | added | David Leckenby | Thanks @raffters Opportunity is related to Contact through the Account object. From the Opportunity there is a many to one relationship with Account and from Account to Contact there is a one to many relationship. Also Contact records can be queried as they have the exact same name as the Account record. Regards | |
| Apr 23, 2015 at 14:15 | comment | added | raffters | @DavidLeckenby - The question I intended raise (though didn't do well reading it while more awake), was: How are the Opportunity and Contact related? | |
| Apr 23, 2015 at 14:12 | comment | added | raffters | Thanks @LaceySnr I didn't mean to mislead anyone. I personally find that way to be of rather limited use, but opinions will vary. | |
| Apr 23, 2015 at 14:05 | history | edited | raffters | CC BY-SA 3.0 |
added 120 characters in body
|
| Apr 23, 2015 at 3:54 | comment | added | Matt Lacey♦ | Hey raffters, setting an id like this is actually a legit way to do updates. Very useful in situations where you're close to the SOQL query limit for instance and is more performant overall. | |
| Apr 23, 2015 at 3:24 | comment | added | David Leckenby | Thank you for your response! What I am attempting to do is to instantiate a contact object, populate it with the correct values that are related to the opportunity (through Id relationship) , and then update it with any changes from the user Visualforce page. Basically I want the save operation to save both the standard primary object (Opportunity) AND the related object (Contact) at the same time. Hope that makes sense. Regards | |
| Apr 23, 2015 at 3:07 | history | answered | raffters | CC BY-SA 3.0 |