---
canonical: https://amplience.com/developers/docs/release-notes/2026/repo-driven-locales/
title: Repository based locale ordering
description: Dynamic Content locale lists for field level localization can be ordered by hub or repository assigned locales can be placed at the top of list.
audience: Business User
date_published: 2026-08-04
date_modified: 2026-08-04
---

# Field level localization enhancements

**Release date: 4th August 2026**

Two new Dynamic Content features make it easier to find the locales you need for field level localized content. Both bring the most relevant locales to the top of the picker, which helps when your hub has a large number of locales configured.

## Repository based locale ordering

Speed up locale selection for **field level** localized content by setting the picker to display locales relevant to the repository first. This helps most when your hub has a large number of locales configured but you only work with a small subset of them.

Each content team member chooses this for themselves. The setting applies only to their own view, so everyone can order the list to suit the way they work.

### Choosing your locale order

To set the order of locale lists for **field level** localization, go to **Settings > Properties** and configure the **Locale ordering** property:

![Dynamic Content properties window with the locale ordering option](https://cdn.media.amplience.net/i/ampproduct/rn-dc-properties-window 'Dynamic Content properties window with the locale ordering option')

- **Hub locales** - Shows every locale in the order they are set up in the hub. This is the default.
- **Repository locales** - Shows locales assigned to the repository above all other locales.

See [Dynamic Content hub settings](https://amplience.com/developers/docs/user-guides/basics/dynamic-content/settings/#properties).

### How the locale list appears in the editing form

With the **Repository locales** setting selected, the locales assigned to the current repository are displayed at the top of the locales list in the content editing form.

![Dynamic Content editing form locales list with repository assigned locales pinned to the top](https://cdn.media.amplience.net/i/ampproduct/rn-repo-driven-locale-ordering 'Dynamic Content editing form locales list with repository assigned locales pinned to the top')

If the repository has no assigned locales and **Repository locales** is set, all hub locales are listed in their set up order instead.

For more information about filtering field level localized content, and ordering the locale list, see [Filtering content using locales](https://amplience.com/developers/docs/user-guides/produce-content/localize/#filtering-content-using-locales).

## Enhanced localized value set

We've updated the localized value set component so that you can now choose to initially show only the locales assigned to a repository, rather than a developer needing to define the default (or pinned) locales in a content type schema. This new feature makes it easier for content producers, particularly those working in multiple repositories, to focus on adding content for only the locales that they're working with.

An additional parameter allows developers to specify that the locales shown by default should be those assigned to the content item's repository. See the [Localized value set reference](https://amplience.com/developers/docs/schema-reference/input-field-components/arrays-and-objects/#localized-value-set) for more information. Note that this feature also requires [Repository locales](#choosing-your-locale-order) to be set.

![Dynamic Content editing form locales list with fields pinned to repository defined locales](https://cdn.media.amplience.net/i/ampproduct/localized-value-set-repo-locales-2 'Dynamic Content editing form locales list with fields pinned to repository defined locales')

## Related pages

[Ordering the content locale list](https://amplience.com/developers/docs/user-guides/produce-content/localize/#ordering-the-locale-list)

[Field level localization](https://amplience.com/developers/docs/user-guides/produce-content/localize/#field-level-localization)