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?

[Alex Coope - SN]

So, I can't talk for any customisations that might be on that instance, however I can say that if the OOtB Spanish Language pack is being leveraged you would have "es" records in there,

Expanding on that per language would look this for the state field on the incident table via sys_choice:



Many thanks,
Kind regards

[jlaps]

STUPID USER ALERT! STUPID USER ALERT!

I provided the above from PROD, which does not have the language pack installed... oops.

So here is what I see for choices on this field. I created one ES option as shown-

When I go to the portal, using SPANISH, I get this for choice list-

Which is providing both the English and Spanish version of VALUE=1. Is this a problem on the widget in question perhaps?

[Alex Coope - SN]

Ha, no need to say that, it happens to the best of us,

So, that looks like a widget in the portal? I have a hunch it's because you haven't enabled "unique values only" on the definition,
- If I'm wrong and it's a variable, that would be on the "Type Specification" form section of the variable item's definition and it's a tickbox,

Many thanks,
Kind regards

[jlaps]

This is from the web portal, and this field is a FIELD and not a variable. It should work exactly like incident_state does, which properly shows NUEVA instead of NEW when in Spanish, and not show both. I don't think I want the enforce unique value, as the incident_state has the same values for the en/es translations of NEW/NUEVA for example.

Stumped.

[Alex Coope - SN]

Ok, so it's a field I have a few ideas:

• Because you don't have the same amount of choices available that could be a factor, so create choices in Spanish for the other 8 entries (in the background the array lengths will be different, when it's expecting them to be the same per language)
• Try the "unique value" because that will limit how many are being shown based on the language and how many are seen in the pool based on the "value", e.g. if it sees 2 entries for "1" (one in English and one in Spanish) it will limit to only one of them which would be the language your session is in,

Let me know how you get on as I'd be curious how the above goes,

Many thanks,
Kind regards