Four Languages, One CRM: Making SSCV2 Truly Multilingual

Switzerland has four national languages, and a Swiss CRM rollout that only speaks German is half a rollout. We have now taken SAP Sales and Service Cloud V2 through full German, French, Italian and English adaptation on client projects. The platform can do it. The knowledge of how is scattered, and most of what went wrong for us went wrong conceptually, not technically. So here are the concepts.

The logon language rules everything

The display language of an SSCV2 session is the language chosen at login, fixed until logout. Not the browser language, not a preference field on the user record. Once you accept this single fact, half the mysterious behaviour disappears.

It also has a sneaky testing consequence: colleagues switch the language, reload the page, see the old language and file a bug. Nein, so nicht: log out, log in, then judge. We have watched perfectly correct translations get rejected in testing purely because of a reload.

Translation is two jobs, not one

Field labels and the values inside selection lists are maintained separately, through different mechanisms. Translate only the labels and your French users see a perfect label above a list of raw technical codes. The two are independent, and both belong to the definition of done.

Two smaller lessons ride along. First, read before you write: real tenants are rarely clean, and we have found the same label empty in two languages, with a typo in the third and a test string in the fourth. Second, a proper translation outranks a hardcoded label, so a wrongly named field rarely needs an irreversible UI change. It needs four good translations.

Embedded pages do not know the language unless you tell them

Mashups, the pages you embed in the CRM, are where multilingual efforts usually die. The iframe cannot see which language the surrounding session runs in; the platform has to pass it along, and that wiring is configured per mashup and easy to miss. Configure it, and the page receives the language cleanly. Skip it, and your beautifully translated page guesses, wrongly.

The tempting workaround is to build your own lookup that reads the language from the user record. Warum in die Ferne schweifen? We have seen that fail in both directions: an empty field that yields nothing, and a stale field that overrides the correct session language. Take the language the platform hands you, keep the texts with the page, done.

Languages are the definition of done, not aftercare

The biggest lesson is organisational. Deliveries came back from customer testing not because translation was missing, but because it was treated as a final polish step. Our rule now: all four languages present, and at least one non-default language checked by a person after a fresh login, before anything goes to the customer.

Two one-minute checks, and each exists because its absence once cost us a retest round. A stitch in time saves nine, umso mehr in four languages.