New Edit Content: two relationship fields share the same value

[adrianjm-dotCMS]

Problem Statement

When a content type has two relationship fields and the new Edit Content is enabled, both fields incorrectly share the same value. Filling the first relationship field automatically populates the second one with the same value. This only occurs in the new Edit Content; the legacy (old) edit content works correctly.

Impact: Users cannot store different related content in each relationship field when using the new editor. This affects any content type with multiple relationship fields and blocks adoption of the new Edit Content for those use cases.

Steps to Reproduce

Video screencast:

Screen.Recording.2026-02-27.at.10.38.26.AM.mov

Steps to Reproduce

1. Go to Content Types in the admin.
2. Create a new content type or edit an existing one.
3. Add two relationship fields to the content type.
4. Enable the new Edit Content for the content type.
5. Create a new content item using the new editor.
6. Fill the first relationship field with a value.
7. Observe that the second relationship field automatically takes the same value.

Acceptance Criteria

• Each relationship field in the new Edit Content maintains its own value independently.
• Filling one relationship field does not change the value of other relationship fields.
• Behavior matches the legacy Edit Content (one value per field).
• Existing content with multiple relationship fields displays and edits correctly in the new editor.

dotCMS Version

Latest

Severity

Medium - Some functionality impacted

Links

NA

[erickgonzalez]

Another scenario to test: When 2 relationships have different types of related Content, it doesn't display any value.
Steps:
1- Full Starter dotcms.
2- Check any Blog Content using the old mode, you can see an author and comments related.
3- Enable the new edit mode for Blog Content Type.
4- Check again, it shows empty values regardless the REST API returns data.

[github-actions]

PRs linked to this issue

• fix(edit-content): scope RelationshipFieldStore to component level #34795 by @oidacra