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

[Julia Baus]

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?

[GlideFather]

It is not recommended to create a new records manually, please follow the plugin installation and you will not need to create anything and you will avoid future problems

[GlideFather]

@Julia Baus 

One more thing, I checked the values for the Language field and there is duplicity despite there is only one record in the sys_language table, the customization overwrote the system settings:

You can check the system dictionary for the field:

Re-consider the solution from the maintenance perspective, because you should not create duplicates. It should be erased the manually created record (ekk) and then activated the Internationalization plugin, if it is already activated then click repair and it will do the trick.

Please review it from your end - user form and Language field or the Language field's system dictionary.

Also, some of the ServiceNow scripts may be associated with the "est" value and will not expect "ekk", for that it might serve you for now but it might not be compliant with OOTB behavior which is what ServiceNow wants you to use...

[Julia Baus]

I think you misunderstood what I was doing: We had an OOTB entry created from Internationalization plugin that had the value et for Estonian language. When I activated that, I got above error message. Means I can't just activate the OOTB entry as the system blocks its activation and asks me to install an Estonian Plugin which does not exist. 

What I find strange that for you the value seems to be "est" instead of "et", but I checked and it was "et" for us from the beginning and no change done before on it. 

I get your point with the references and thinking about it, it might also cause issues with the machine translation, but currently I don't have any other idea how to get the entry activated as it doesn't accept the ootb value

[GlideFather]

OK, just verify you do not have duplicates in the system dictionary because otherwise it will bring you headaches sooner or later 😛 

[Julia Baus]

Thanks for all the hints provided!