Posts: 68
Threads: 29
Joined: Feb 2017
Reputation:
22
Suppose to create one contact with a wrong mail like pippo@gmail.es
to add an opportunity to this contact.
Later when you will correct the email field in contact changin pippo@gmail.es to pippo@gmail.com in opportunity ther will be the wrong eamil address.
The opportunity.mail field is not editable, the only way to change it, is to reapply the "related to" field.
Perhaps is a better idea to leave editable ( pressing edit button) the potential email field
have a nice day
Lorenzo
Posts: 68
Threads: 29
Joined: Feb 2017
Reputation:
22
OK. It works.
The problem was i usually edit the single field in the opportunity, so i don't press edit and save globally.
thaks
Lorenzo
Posts: 3,564
Threads: 36
Joined: Apr 2014
Reputation:
49
Yes, we still can't dynamically change the other fields on individual edit. It does change the email value but you can't see the change until you reload the record.
I have that on our to-do list
Joe
TSolucio
Posts: 3,564
Threads: 36
Joined: Apr 2014
Reputation:
49
The email on the opportunity is the main email of the account or contact DIRECTLY related to the record.
Joe
TSolucio
Posts: 1,665
Threads: 644
Joined: Aug 2016
Reputation:
164
ok, but my understand when you talk about directly related, is when I associate new contact a opportunity, for me, this is or main relation.
See not is a "right" or "wrong" here, but the form of understanding.
Look my scenario
At first moment, when I create a opportunity I have one person for talking in company.
But in sales developement, I identify a real decisor for my opportunity.
In my mind, at this moment, I should click contact, and add new contact at opportunity, and this new contact is "the guy".
However, system still look for a email account, or data in account ( because my process in b2b ).
I don't understand very well, why there a relation for contact in opportunity, if not to set a new "master contact"
Ranieri
eCRM Web
Posts: 3,564
Threads: 36
Joined: Apr 2014
Reputation:
49
The way it is designed is that the person you are talking to is the one related in the "related to" field on the record. All the other contacts in the related list are stakeholders.
If you want to implement another logic you will have to program it. You can use the corebos.entity.link.after event to set the field value according to your particular business logic and eliminate the hard-coded logic (which we will do in the near future now that we can do that with workflows).
Joe
TSolucio