System does not allow me to enter a custom language entry for Estonian

Julia Baus
Tera Expert

Hi,

we need to support Estonian language on our system. As there is no ServiceNow plugin for Estonian, I wanted to create a custom entry for Estonian on sys_language table (we did the same e.g. for Romanian and it worked). 

For Estonian I get the error message:

Setting active=true does not load/upgrade the Estonian Language Plugin. To activate this plugin please navigate to System Definition - Plugins.

 

Any ideas on this as there is no such plugin?

 

1 ACCEPTED SOLUTION

Hristo Ivanov
Kilo Sage

I just tried it in my PDI with id = ekk and it worked, I guess there's some conflict with the "et" ID

View solution in original post

10 REPLIES 10

Hristo Ivanov
Kilo Sage

I just tried it in my PDI with id = ekk and it worked, I guess there's some conflict with the "et" ID

GlideFather
Tera Patron

Hi @Julia Baus,

I have replicated the issue, and yes it is not possible to go and create the Estonian language in [sys_language] table, however, the plugin to be activated is called:

I18N: Internationalization

Now Platform

Plugin id: com.glide.i18n

KamilTEL_0-1749198277294.png

 


And then it creates (or activates) the Estonian language without manual intervention:

KamilTEL_1-1749198295558.png

Tested OK on my PDI.

NOTE: when installing plugins, you should always talk to the platform owner as it might be a subject to some extra expenses, most probably not in this case but you should let them know. And it is impossible to remove the plugins after installation, so maybe test it first with some instance that is not important (enough.g. personal developer instance).

Please, let me know if this helped you solve your issue 

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */


You will just need to manually activate that record... but not to create it.

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */


It is not possible to manually activate the record, that is when I get the error message. After having changed to ekk as mentioned above, then I was able to activate it. Sorry if mentioning to create above was misleading