Relationship fields fail to save when editing Blog content in new edit content mode

[oidacra]

Problem Statement

In the new edit content mode, when a Content Type has multiple relationship fields pointing to different content types, the relationship values are not displayed — even though the REST API returns the correct data.

Update: The issue where multiple relationship fields shared the same values (empty or duplicated) was resolved in PR #35017 (linked to #34795), which scoped the RelationshipFieldStore to the component level.

Remaining issue: When editing a Blog content item in the new edit content mode, relationship fields (Author, Comments) fail to persist changes on save. The relationship editor opens correctly and values are displayed, but saving does not persist the changes — the data is silently lost.

This is reproducible with the Blog Content Type in a Full Starter instance, which has two relationship fields: Author (pointing to Author content type) and Comments (pointing to Comments content type).

Steps to Reproduce

1. Start a Full Starter dotCMS instance.
2. Open any Blog content in the new edit mode.
3. Verify that Author and Comments relationship fields now display their related content correctly (fixed by PR fix(edit-content): scope RelationshipFieldStore to component level #34795 #35017).
4. Attempt to edit either relationship (Author or Comments) — the editor opens.
5. Make a selection and trigger save.
6. Observe: The save action completes but changes are not persisted — the field remains unchanged.

Acceptance Criteria

• Editing a relationship field (Author or Comments) in Blog via the new edit mode and triggering save persists the changes correctly
• Old edit mode continues to display and save relationship values as expected (no regression)
• Verify behavior with a Content Type that has a single relationship field in the new edit mode

dotCMS Version

Latest from main branch (Full Starter)

Severity

Medium - Some functionality impacted

Links

• Fixed (shared store): PR fix(edit-content): scope RelationshipFieldStore to component level #34795 #35017 / New Edit Content: two relationship fields share the same value #34795
• Related: New Edit Content: two relationship fields share the same value #34795 (sibling scenario — relationship fields in new edit content)