Limit the number of available languages in the web client

[kasperdj]

BC Idea Link

https://experience.dynamics.com/ideas/idea/?ideaid=6d5f0cc9-2375-ef11-a4e5-000d3a7ad6db

Description

Use case already discussed with S??ren Alexandersen from Microsoft on LinkedIn.

Enable the possibility to define (read limit) the number of support languages. It is extremely confusing for the customers that they have an option to choose between 10+ English languages and 30+ languages they will never use. So essence is: please keep it simple - most customers only need the local language and English (US).

Note: The NST already supports this setting and has done so for many years - however we can only set this for OnPrem installations.

I will provide the implementation for this BC Idea

• I will provide the implementation for this BC Idea
  Internal work item: AB#549461

[JesperSchulz]

Approving, given this was discussed with @sorenfriisalexandersen.

[kasperdj]

So what is the next step here? Søren mentioned that you want to build a new app for controlling this.

I have part of the source code already that limits the language selection to Danish and English (US) that I can offer as a contribution if it helps. The changes that then is needed on top are:

• Creating new app
• Create a new setup table in which the super user can define which languages that is "being used" in the given environment
• Update my code which is hard-coded to Danish and English (US) to use the languages defined as being used in the new table

[JesperSchulz]

Ideally you would create a pull request with your code in a shape, which allows us to pull it into the product. I don't have all the details, but from how I understand the feature, this doesn't sound like an app? Sounds more like a contribution to existing code. I will need to talk to @sorenfriisalexandersen how he envisions this feature to surface. We will get back to you!

[sorenfriisalexandersen]

@kasperdj , @JesperSchulz We are looking for flexible solution that would allow administrators to add the "allowed" languages within that environment, so that users can only choose from those languages. If no allowed languages have been set up, the list works as today, unfiltered.

Any other ideas?