Did you get the entire team to vote up for you? I agree this can be better. I will file a bug for Commerce team to look into
A bug has been created and a fix is under review. It might be included in 13.14 (or 13.13 if I push hard enough)
And yes, it is heading toward Commerce 13.13, which will be out in one week or so
Tested OK! https://world.episerver.com/documentation/Release-Notes/ReleaseNote/?releaseNoteId=COM-10522. Good job Quan!
Is there an option to switch this back to the way it was ?
Now we see these commerce nodes :
The (English) Name field is always unique.
The (localized) display name isn't always unique...
The content editors are free to choose whatever text they want as the <h1> title text...
Each of above commerce nodes are specific for one country site, e.g. this one is for Austria :
Another example where the (localized) product DisplayName is not unique:
Johan had more votes so he won
Kidding aside, we will look into this
Hi Quan, My custoemer have the same problem now, would like to have column configurable, like the old manager ;) haha, nevertheless, are you looking in to this?
What do you mean by configurable? Choices between name and display name? I am not actively working on this but still keeping an eye
yes, ok sounds like far in the future. We better change how we used DisplayName.
'I am not actively working on this but still keeping an eye'
Sorry, what does this mean?
2 months ago, I opened this problem via the official support page and they told me that it would be taken care of?
We've been waiting very patiently ever since for a fix...
@marcel, do a follow up and ask them where the're at?
Providing the APIs to let partners - you - switch between name and display name can be complicated, but you can do it yourself, and with more flexibilty https://vimvq1987.com/name-or-display-name-in-catalog-ui-you-can-choose/
Thank you Quan, great!! =)
I can confirm that that fixes our problem, thank you
This is something that has been bothering me for years. Why does Episerver render the Catalog UI using the Name property rather than the DisplayName property? The Name property isn't translatable, while the DisplayName property is.
We have customers with editors all over the world who have painfully been forced to learn the Swedish names of products and categories, just because the catalog was created in Swedish. And similary, if the catalog was created in English, it's not given that everybody knows all the English translations by heart.
Why not use the translations instead to render the tree? Just like CMS does?
The only reasoning I can see for this is 1) legacy... 2) legacy and 3) there might not be a Displayname in the current languge, but then a fallback to Name could be made and indicating that it is "untranslated" (just like CMS does with grey italics).