One of my offices has a Xerox 7855. I work almost 100% remotely, so all configuration, including address book maintenance, is done remotely. I can add e-mail contacts but cannot figure out how to make those new contacts Favorites. I go to Address Book, then Email → Contacts, Edit an existing Contact, click the Email Favorite button. It changes from gray to colored, but when I click Save, it does not become a Favorite. And the next time I look at that Contact, it is not a Favorite.
I can make existing Favorites non-favorites, then make them favorites again. But I cannot make new contacts Favorites.
I already tried this:
But then I get a message indicating that the contact (display name) already exists. However, I cannot see it in the machine's HTML interface. Furthermore, I can add that contact manually to the machine's HTML interface with no duplicate conflict. But I still cannot make it a favorite.
Solved! Go to Solution.
Well, the rabbit hole went deeper than I thought. Upon poking around, I discovered the Remote Admin Console. Even there, although I could check the Favorites button and get it to light up, that setting was not saved. So I resorted to exporting the entire address book (change Management to Export in the upper-left corner on the Address Book screen). Then I did a Delete All. I also updated the CSV file to make the new contact a favorite (although I could have done this later).
Then I re-imported the address book, using the replace contacts instead of add contacts option. Now I can make any contacts favorites.
Problem solved, although it does leave me wondering what more there is to the internal address book than what is actually exported, since the export file looked and functioned correctly, and it seems it was only the Delete All option that cleared things to make it all usable.
Display name already exists is a long standing bug/glitch.
The fix is and always has been to just Export > Delete > Import
We don't know why it happens or what might cause it, it almost seems random. Since we cannot cause a machine to do it, we can't fix it, I'm sure the engineers have tried, but the problem is, it's so easy to resolve (less than 2 minutes) that for most of the customers who have had the issue, when they call in, they don't want to take 30 or more minutes to collect data logs and config sheets and all the other stuff that would be required by Engineering to diagnose/fix it. And there is no certainty that they could, because possibly the logs would show nothing wrong. And it could take days/weeks/months to figure out, and you couldn't verify the fix unless you left it broken for that days/weeks/months time span.