Content - Item with relational field not reflecting correct locale when switch to other language version

[gtllien]

Problem

When a user creates a new item (with multiple locales configured) and sets a value for a relational field (a field linking to another item), that relational value is not correctly fetching the appropriate localized data when the user switches to a different locale/language version.

See below test video

chrome_96P7U4mAN0.mp4

Steps to reproduce

Steps to reproduce the behavior:

1. Ensure you have at least two locales configured (eg. en-US, en-PH)
2. Create a new item with a relational field (eg. One-to-One field), and set the relational field value then save.
3. Examine the language/locale of the relational field when switch to the other locale (eg. en-PH)
4. Observe that the One-to-One field (eg. switch to Ph version) is incorrectly set to the original item's locale value (en-US).

Expected behavior

When an item with relational field is created having multiple locales, and when switch to other language version the relational field's value should pick up the correct localized value

[geodem127]

Hi @gtllien, Isn’t that the expected behavior since the relational field’s language was explicitly defined when the item was created?

What would be the expected behavior if the user intentionally sets the relational field’s language while creating the item, then later switches to another language version? Should the relational field’s language also update automatically?

For example, the user creates a new item in en-PH, sets the one_to_one field to es-ES, and then switches the item’s language version to en-US — should the one_to_one field’s language also change to en-US?

As per the docs, when you generate a new language version, the system creates a separate item for that language that begins as a direct duplicate of the original source content.
https://docs.zesty.io/docs/locales-multi-lang-content#what-happens-when-a-new-language-is-added
https://docs.zesty.io/docs/how-to-set-up-internationalization-i18n#creating-content-in-other-languages

[bobakzahedi]

I agree the expected behavior is to have relational filed automatically point to the corresponding localized version. Especially if the feature previously worked this way. Any change would be unexpected, and introduce new issues in our user's flow.

From this slack conversation:
https://zesty-io.slack.com/archives/C050120G5/p1760542269903149?thread_ts=1759513172.180209&cid=C050120G5

[geodem127]

Requires backend changes - reference Slack discussion

Slack: https://zesty-io.slack.com/archives/C050120G5/p1761763597691779?thread_ts=1759513172.180209&cid=C050120G5

https://github.com/zesty-io/instances-api/issues/695