Developer forum

Forum » Ecommerce - Standard features » Cannot change system field in default language

Cannot change system field in default language

Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

Hi,

 

We noticed a small bug in 9.15.9. Currently we can change the label/name of all product fields, in all languages, but if you're working on the default language, that's not allowed.

 

Go go Settings > Ecommerce > Proudct fields > pick a system field > make sure you have the default language and try to change the label/name

https://app.screencast.com/UGTvhs088kKoa

 

Best Regards,

Nuno Aguiar


Replies

 
Kristian Kirkholt Dynamicweb Employee
Kristian Kirkholt
Reply

Hi Nuno

Please don´t use version 9.15.9. There is a problem with ProductCategoryFields in that version.

You can´t change the Label/Name on the standard fields

Create a Custom field then you have full control and are able to change Label/Name after the creation

Kind Regards
Care Support
Kristian Kirkholt

 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

Hi Kristian,

 

Sure, we can upgrade, this is just a demo site, but using a custom field is not an option, because we're not asking customers (nor integration) to use a different field because of a label.

 

But is this not a Bug? If I create another ecom language and make that the default, I can update the name/label in English and then I can update the default language back to English.

 

The problem started when a customer wanted to use Field Display Groups in Swift and wanted to change "Number" to "Num." or "Num #", but then we realized we couldn't. When we first reported it, it was Rejected because it could not be reproduced (was tested with another language that was not the default) and now I managed to confirm it's tied to the default language.

 

Does this explanation make it clearer?

Nuno Aguiar

 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

Hi Kristian,

 

Did you get my reply above? I did upgrade to 9.15.13 and the result is basically the same. We cannot change the label of a standard field in the default language, but we can in other languages.

https://www.screencast.com/t/Dvg0jMIAn

 

Nuno

 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Reply
This post has been marked as an answer

Send to QA for verification

Votes for this answer: 1
 
Oleg Rodionov Dynamicweb Employee
Oleg Rodionov
Reply

Hi,

the behavior was defined by TFS task #80451 (#82323) and implemented on DW9.9.5 and up (probably to follow the "system field" meaning), so it's feature but not a bug. Actually, bug could be abbility to edit "Name" in translations like for not system field (currently it's under discussion).

BR, Oleg QA   

 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

Hi Oleg,

 

So the bug is the ability to allow users in other languages (i.e. "French") to change "Number" to "Nombre"?

 

If so, I guess the problem we have is the User Experience, so we have to tell customers that:

  • If you want to change the label of a custom field in any language, --» go to Settings / Product Catalog / Product fields
  • (currently) If you want to change the label of a standard field in a language other than the default one, --» go to Settings / Product Catalog / Product fields
  • If you want to change the label of a standard field
    • --» go to Translation
    • --» customize the Specifications component to render a Translation tag instead of the field name
    • --» you will start to also see custom fields in Translations, so now you should start to change the name here OR in Settings (and we know how confusing it can start to get

 

Hope this helps expose the current situation we're experiencing.

 

What I'm looking for is a for a better user experience that does not get us into issue described above, where the Translations start to get populated with unnecessary keys and add confusion.

 

Best Regards,

Nuno Aguiar

 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Reply

Hi Nuno

I'll let this go to PM for PIM. But it will probably not be a bug fix. We might change it, we might not.

 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

Understood. thank you Nicolai

 
Oleg Rodionov Dynamicweb Employee
Oleg Rodionov
Reply
This post has been marked as an answer

Hi,

new task #16043 has been submitted agains the bug per PM's final resolution.

BR, Oleg QA

Votes for this answer: 1
 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

Thanks Oleg. That's encouraging :)

 
Kristian Kirkholt Dynamicweb Employee
Kristian Kirkholt
Reply

Hi Nuno

The new PIM task #16043 now added to release 9.16.2
Get this from the download section https://doc.dynamicweb.dk/downloads/dynamicweb-9

Kind Regards
Dynamicweb Care Support
Kristian Kirkholt

 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

Thank you Kristian

 

You must be logged in to post in the forum