Importing CSV to update phones doesn't update KEY0 2

[NewUser25]

Hey I'm fairly new to working with CS1000 Element Manager 7.5 and I was messing around with the import function to update phone records more easily. What I am having a problem with is updating KEY0 when PRIMEDN is the first field in the csv file. If the first field is TN like so

[ TN,PHONE,DES,ZONE,KEY0
232 0 13 22,1120,4137,14,SCR 31803 0 MARP CPND_FIRST_NAME(TEST) CPND_LAST_NAME(USER) ]

KEY0 will update just fine. If the first field is PRIMEDN like so

[ PRIMEDN,PHONE,DES,ZONE,KEY0
31803,1120,4137,14,SCR 31803 0 MARP CPND_FIRST_NAME(TEST) CPND_LAST_NAME(USER) ]

KEY0 will not change at all. If I try to update KEY1 when the PRIMEDN is the first entry, KEY1 will update, but still not KEY0. Any help is appreciated, thanks.

 

[NewUser25]

Anyone have any experience with this?

 

[NewUser25]

If there is any more information I can give that might help, let me know.

 

[StanleySteamer]

I think because PRIMEDN is usually derived from the DN on KEY0. So maybe Element Manager will not update it because it thinks you are trying to change the information on the same database item that you are querying.
That's just a guess but I doubt you will get a solution from Avaya. I know you are only trying to change the name but you might have to find a way to workaround by using the TN.
If you have frequent name changes then you might consider a LD 95 command line script. Pretty sure FirebirdScrambler has posted something that works with Procomm.

 

[Wanebo]

While I have never used the import function in Element Manager I would suspect the reason you are running into the issue is that you are explicitly establishing PRIMEDN before key programming. Even in manual programming of a set you cannot use a number that is a primary DN on one set and use it on key 0 when creating a new set. You can change an existing sets key 0 to a DN that is primary on a different set, but you are not allowed to create the set using it there.

 

[NewUser25]

Thanks for the information guys, looks like the only work around is to use the TN first which in my situation isn't ideal. Oh well!