ContactNameOrder.LastNameFirstName issue

Heiko 1,211

In Windows 11 21H2 Build 22000.1641 it's not possible to set

ContactManager.SystemDisplayNameOrder = ContactNameOrder.LastNameFirstName;

ContactManagerForUser.SystemDisplayNameOrder = ContactNameOrder.LastNameFirstName;

anymore. Afterwards it is always ContactNameOrder.FirstNameLastName.

Why? What should I do?

It is not good, because, if I read the contacts, each contacts DisplayName was automatically built by the Windows runtime with HonorificNameSuffix, LastName, HonorificNamePrefix and FirstName in the right order with or without commas. So if I want to continue to support ContactNameOrder.LastNameFirstName in my app which is in the store for 7 years, do I need to build the DisplayName by myself now?

Roy Li - MSFT 31,681 Reputation points Microsoft Vendor

2023-03-13T02:48:32.56+00:00

I've made a simple test using the ContactPicker sample on a Win11 21H2 device. But this property is working correctly.

Here is the test result for LastNameFirstName

Here is the test result for FirstNameLastName

As you could see the result from the image, the display order has been changed correctly.

Could you please share more details about how you use this property and how did you get the unexpected behavior? It will be better to share the code snippet in your question that could be used to reproduce this behavior.
Heiko 1,211 Reputation points

2023-03-13T12:52:24.7033333+00:00
Thank you Roy for your response. I took the same sample as you. But on my side I do not get the right order. I have a test machine with Windows 11 which is not activated. Perhaps this is a reason that I cannot change the SystemDisplayNameOrder setting? But a user tells me he is using my app for a long time under Windows 10 but now if he change this setting it is applied until he closes the app and by restart this setting is lost. I didn't update my app in store since 15 months. I tested it on Windows 10 and all works fine. I tried it under Windows 11 and get the described behaviour.

This is my code. The setters are called by clicking RadioButtons.

public bool NameOrder_FirstLast { get { return ContactManager.SystemDisplayNameOrder == ContactNameOrder.FirstNameLastName; } set { if (value) ContactManager.SystemDisplayNameOrder = ContactNameOrder.FirstNameLastName; } } public bool NameOrder_LastFirst { get { return ContactManager.SystemDisplayNameOrder == ContactNameOrder.LastNameFirstName; } set { if (value) ContactManager.SystemDisplayNameOrder = ContactNameOrder.LastNameFirstName; } }
Heiko 1,211 Reputation points

2023-03-13T13:11:34.99+00:00

The People app has the same problem on my Windows 11 machine.
Roy Li - MSFT 31,681 Reputation points Microsoft Vendor

2023-03-14T03:13:12.9166667+00:00

That's an interesting behavior. I've also tested this in a Win11 22H2 VM and it also works correctly. Could you get the OS version from that user who reports the same behavior? I'll also talk to the team to see if we could find more information.
Heiko 1,211 Reputation points

2023-03-15T18:46:03.13+00:00

The user has Windows 10 22H2 Pro 22H2, build 19045.2673. If he tries to change the name order to 'LastName, FirstName' this setting won't be applied. But he also cannot change the display of the middle name of a contact within Contact.DisplayName, if he activates it.

ContactManager.IncludeMiddleNameInSystemDisplayAndSort = true;

In my Windows 10 Pro 22H2 all works well. In my Windows 11 Pro 21H2, build 22000.1641 I can reproduce this behavior. 'LastName, FirstName' won't be applied and I cannot display the middle name within Contact.DisplayName. My Windows 11 is not activated because the CPU is too old. Here I cannot change any setting unter Personalization. So I think this could be the reason that I cannot change the contact name settings programatically(?).
Roy Li - MSFT 31,681 Reputation points Microsoft Vendor

2023-03-16T07:42:47.83+00:00

Yes, it seems that his behavior happens to some specific devices. One of my test devices - the Win11 VM is not activated as well. The ContactNameOrder.LastNameFirstName also works on that device. I'll talk with the team to dig it further.

Accepted answer

Roy Li - MSFT 31,681 Reputation points Microsoft Vendor

2023-03-22T03:12:50.8633333+00:00

Hello,

Welcome to Microsoft Q&A!

I've talked with the team about this behavior. None of us could reproduce this behavior with same OS version and different OS version. This behavior should be related to the OS itself. It's highly possible that there are some system configuration or other things like group policy which causes this issue. We'd suggest you report this issue in the Feedback Hub.

Thank you.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

ContactNameOrder.LastNameFirstName issue

0 additional answers