Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

ADSI - multivalued proxyaddresses

bchrist
New Contributor
New Contributor
Hi,
We are tryig to update proxyaddresses with latest email address as primary and leaving old value as secondary. 
expected result :
1. replace existing primary "SMTP" with "smtp"
2. Appending a new value to current list with new email as "SMTP"
The following example described the actual behavior:
value of customproperty39 (value in saviynt account which store the proxyaddresse value) 
[STMP: 'email@example.com', stmp: 'alias@example.com', SIP:  'sip@example.com' ]
update the email with a new email value
[STMP: 'newemail@example.com', ,stmp: 'email@example.com', STMP: 'email@example.com', stmp: 'alias@example.com', SIP:  'sip@example.com']
During my tests, I noticed that when the new email value existed in the proxyaddress value, no update was made (no new value was added to proxyaddress).
After several updates, this behavior caused problems during reconciliation, as the proxyaddress value became too long to be mapped with a customproperty39. We therefore removed proxyaddress from the account attribute mapping.
 
Can anyone help me ?
Thanks .
3 REPLIES 3

rushikeshvartak
All-Star
All-Star

Multivalued attributes supported in AD are:

  • proxyaddresses

  • businesscategory

  • othermailbox

  • othermobile

  • otherpager

The value of the multivalued attribute in EIC is always be equal to the value of the corresponding multivalued attribute in AD. To add a new value to a multivalued attribute, append the new value in a comma separated list of values. You can replace existing value with the new value in the corresponding customproperty parameter.

For example, if a multivalued attribute named as proxyAddresses has values as SIP:adsiuser01@hostname.com and SIP:adsiuser02@hostname.com, then in the UPDATEACCOUNTJSON parameter, use the following format: "proxyAddresses": ["SIP:adsiuser01@hostname.com","SIP:adsiuser02@hostname.com", SIP:adsiuser03@hostname.com]. When the attribute values are referring to binding variables, use the following format: "proxyAddresses": ["${account?.customproperty1.toString().replace(',','","')}"]


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

bchrist
New Contributor
New Contributor

Hello  rushikeshvartak

We've done it before, but it didn't work.

You will attached the updateAccountJSON config

Can you share logs


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.