Translation of Choice Field Problem

[jlaps]

Good morning community,

I am working on translating our Service Portal and pages to Spanish. I have found documents and it has been going pretty smoothly, but I am running into a problem translating a custom choice list off the incident table.

I see the two letter language choice, and if I create a NEW choice for 'es' and put in the Spanish translation, and I leave the existing 'en' choice, I see both choices on either language in the portal. If I replace the 'en' with 'es' and the translation, I only see the Spanish of course.

I cannot seem to translate my choice fields without ruining the existing English choices, or duplicating the choices showing both English and Spanish. What am I doing wrong?

[jlaps]

Thanks Alex for sticking with me on this one. I have not yet tried your above possibles, but I did find out something that i think is a definitive bread crumb trail. This stems from my irritation about state/priority fields should be the same way and they are working correctly.

I was comparing what the advanced view, behind the scenes working of ServiceNow and those fields, to the portal view for the escalation reason choices.

Though it never happens in the wild, I edited the escalation reason field from an incident.list view, and sure enough, it only shows the proper choices by language. It is ONLY the widget on the portal that is having trouble.

So I am thinking there is something on the widget side that is not working like other widgets; this is a custom widget I made, so perhaps I am missing something in the code that is grabbing the choices, I do not know how to limit them, but I have not searched on that yet either.