Addled Address Adjustments

Matt Gonzales $organization over 11 years ago

We're getting the following error for some records when trying to save a change to one of their addresses:

"Salutation of the specified Salutation Type does not exist for the Constituent. (AddressEntity.AltSalutationType.Id)"

Upon investigation, I see that the records in question have one thing in common: no alt_signor entry (i.e. NULL). In the client, the dropdown says (none). Is it necessary for there to be a Salutation in every [active] address record? If so, I believe it's possible this happened via a bad custom stored procedure written to handle NCOA updates which can be adjusted for future runs. But in the meantime, can I just mass update the records with the Default signor (0) and be done with it?

What say you, Tessiturians?

Anna Wessely (Past Staff Member) $organization over 11 years ago

Matt,

I would hit up support in TASK on this one.

Best,

Anna
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Melanie Weir $organization over 11 years ago

I'm getting this message, too. What was the resolution?

Thanks!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Anna Wessely (Past Staff Member) $organization over 11 years ago in reply to Matt Gonzales

Matt,

This sure sounds like a defect to me. Do you mind logging this through TASK? That way we can get it in our queue.

Best,

Anna
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Matt Gonzales $organization over 11 years ago

It appears that the record was using the default salutation in the drop-down list ("default"). Unfortunately, the record did not have a salutation type "default", which seems like something the client software should prevent somehow.

Thank you,

Matt

On Feb 23, 2015, at 12:26 PM, "Melanie Weir" <bounce-melaniesnook1900@tessituranetwork.com> wrote:

I'm getting this message, too. What was the resolution?

Thanks!

From: Matt Gonzales <bounce-mattgonzales9808@tessituranetwork.com>
Sent: 1/28/2015 1:00:20 PM

We're getting the following error for some records when trying to save a change to one of their addresses:

"Salutation of the specified Salutation Type does not exist for the Constituent. (AddressEntity.AltSalutationType.Id)"

Upon investigation, I see that the records in question have one thing in common: no alt_signor entry (i.e. NULL). In the client, the dropdown says (none). Is it necessary for there to be a Salutation in every [active] address record? If so, I believe it's possible this happened via a bad custom stored procedure written to handle NCOA updates which can be adjusted for future runs. But in the meantime, can I just mass update the records with the Default signor (0) and be done with it?

What say you, Tessiturians?

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel