Thread Details
  • State Not Answered
  • +1 person also asked this people also asked this
  • Replies 16 replies
  • Subscribers 365 subscribers
  • Views 5065 views
  • Users 0 members are here
Forum Actions

$bean->emailAddress->addAddress is not working, and $sea->addAddress REMOVES all other addresses

Francesca Shiekh

I am writing an API to change an email address on a contact.
I don't want to remove the old address, just add the new one as primary on the Contact bean.

I used the documented addAddress ( support.sugarcrm.com/.../ )

Fullscreen
1
2
$contactBean->emailAddress->addAddress($new_email_address, true);
$contactBean->save();
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

But this won't even add the new address to Contact at all. There are no errors in the logs, I verified that the contactBean is a valid Bean, and that the $new_email_address is a valid address. I checked the parameters for the addAddress function and I verified that the function is being called.

What's worse

Fullscreen
1
2
3
4
5
$sea = new SugarEmailAddress();
$sea->addAddress($email_address,true);
//do some checks...
//add the email address to the Contact $bean
$sea->save($bean->id, 'Contacts');
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Adds the new address but DELETES all the others!

Has something changed in v11.0.1 (on site Professional) that I'm not aware of?

Thank you,
Francesca

Parents
  • 0

    I found another issue... in some scripts I was using:

    Fullscreen
    1
    2
    3
    4
    5
    $sea = new SugarEmailAddress();
    $sea->addAddress($email_address,true);
    //do some checks...
    //add the email address to the Lead $bean
    $sea->save($bean->id, 'Leads');
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    While this works, it is now deleting ALL other addresses.

  • 0 in reply to Francesca Shiekh

    That is odd. Maybe you already checked it yourself in the core files but it is due to the way how the SugarEmailAddress class works. By default it does initialize the internal address array empty. When you directly add addresses to that using the addAddress function you actually adding them directly to that empty array. When you execute the save method it will then not validate what the other addresses are because it does not know yet which bean it is related to. See the following lines i the save method of that class:

    Fullscreen
    1
    2
    3
    if (empty($this->addresses) || $in_workflow) {
    $this->populateAddresses($id, $module, $new_addrs, $primary);
    }
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    If you call the populateAddressess before you add a new address to it you should be fine, I think. 

    btw the code for this class hasn't been changed much between 10.0.3 and 11.0.1 atleast not for this functionality.

  • 0 in reply to Jeroen Somhorst

    We jumped from 9.x to 11.x and I didn't see anything in the Release Notes for any of the versions in between (I checked them all) about such a major change in functionality. Did I miss something?

    What puzzles me is that the documentation says nothing about this:

    It talks about ADDING addresses not, REPLACING addresses:

    https://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_11.0/Architecture/Email_Addresses/#Updating_Email_Addresses_Using_the_SugarBean

    I am very confused... it was not behaving this way before, but it doesn't look like this particular file changed between v9 and v11.

    FrancescaS

  • 0 Sugar Employee Badge in reply to Francesca Shiekh

    Hi Francesca,

    I'll take this to our engineering and PMs and will circle back to you on this.

    Keep you posted.

    rafa

    SugarCRM | Principal Developer Advocate

Reply Children
No Data