Use localized catalog in Commerce catalog UI

Vote:
 

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).

#210624
Dec 01, 2019 18:01
Vote:
 

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

#210639
Dec 02, 2019 11:13
Vote:
 

Yes please!

#210717
Dec 04, 2019 9:43
Vote:
 

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)

#210739
Dec 04, 2019 12:10
Vote:
 

That's some good news Quan! Our editors will be very happy with this!

#210751
Dec 04, 2019 15:05
Quan Mai - Dec 04, 2019 15:32
Accept the answer then ;))
Vote:
 

And yes, it is heading toward Commerce 13.13, which will be out in one week or so

#210777
Dec 05, 2019 13:06
Vote:
 

Me thinking why did I not ask for this before :-O

#210780
Dec 05, 2019 15:41
Quan Mai - Dec 05, 2019 15:43
Well you asked in a good day when I was in good mood and had some time to spare :)
Vote:
 

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:

#214650
Edited, Jan 10, 2020 8:04
Vote:
 

Johan had more votes so he won

Kidding aside, we will look into this

#214656
Jan 10, 2020 10:07
Vote:
 

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?

#218422
Mar 12, 2020 14:11
Vote:
 

What do you mean by configurable? Choices between name and display name? I am not actively working on this but still keeping an eye

#218424
Mar 12, 2020 15:04
Vote:
 

yes, ok sounds like far in the future. We better change how we used DisplayName.

#218426
Mar 12, 2020 15:11
Vote:
 

'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...

#218427
Edited, Mar 12, 2020 15:50
Vote:
 

@marcel, do a follow up and ask them where the're at?

#218435
Mar 12, 2020 19:39
Vote:
 

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/ 

#218462
Mar 13, 2020 9:48
Vote:
 

Thank you Quan, great!! =)

#218463
Mar 13, 2020 9:54
Vote:
 

I can confirm that that fixes our problem, thank you

#218469
Mar 13, 2020 10:40
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.