Hi,
I'm updating the First name, last name and Display name. Everything works great, and no errors! But the the "Preferred Handle" field under "CM Endpoint Profile' sets to "(None)" when this update happens. I'm only sending a simple xml (below) with the names.
How can I prevent this from setting to "(None)"?


userXmlData is : <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<delta:deltaUserList xsi:schemaLocation="http://xml.avaya.com/schema/deltaImport userdeltaimport.xsd" xmlns:tns="http://xml.avaya.com/schema/import" xmlns:delta="http://xml.avaya.com/schema/deltaImport" xmlns:asm="http://xml.avaya.com/schema/import_sessionmanager" xmlns:ipt="http://xml.avaya.com/schema/import_csm_cm" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<delta:userDelta>
<displayNameAscii>Doe, John</displayNameAscii>
<givenName>John</givenName>
<loginName>John.Doe@avaya.avayagovos.com</loginName>
<employeeNo></employeeNo>
<middleName>Merged middle name</middleName>
<source>local.xml</source>
<sourceUserKey>none</sourceUserKey>
<surname>Doe</surname>
<userName>Johne.Doe</userName>
</delta:userDelta>
</delta:deltaUserList>

What release of AES & CM are you working with?

As a work around, read the record, and copy the "Preferred Handle" from your read request into your change/update request. From your description it sounds like the AES/CM code is accidentally copying an unspecified "null" from your update request into the station record even though when a field is absent, there should be no update to that field.

The "Preferred Handle" lives under CM profile, and I'm trying to avoid sending the entire CM profile since this is just name change. Keep it simple!
I've poke around with the xml. Found out that the issue occurs anytime I send the Display name along with First Name and Last name. But Display name is important for displaying on the phone, therefore, I need to include it in the xml.

What API are you working with? Application Enablement Services' System Management Web Service, or System Manager's User Web Service?

I'm using "User_Management_Webservice_Client".

Instead of using the find, I modify what I get from the lookup. The lookup is very simple and it has all the names I need.

final String result = webServiceClient.lookup(
properties.getProperty("entity.type"), queryUrl);
final List<String> loginNameList = UserMgmtClientUtil
.getLoginNames(result);
final String updateMode = properties.getProperty("user.update.mode");
for (String loginName : loginNameList)
{
System.out.println("Applying logic to user update data...");
final String userResult = webServiceClient.find(
properties.getProperty("entity.type"), loginName);
System.out.println("userResult " + userResult);
//Users users = UserMgmtClientUtil.getUsers(userResult);
Users users = UserMgmtClientUtil.getUsers(result);
.
.
.

This issue would seem to exceed the level of free support we provide through the forums. The System Manager User Management Web service is available to higher level (i.e. above registered level) members in the DevConnect program. If your membership is above the registered level, please open a technical support request to engage us further on this issue.