Unexpected behavior with the field of type ‘upload’ and the ‘relationTo’ collection after editing it in the popup

[ivan-kardash]

Describe the Bug

Any changes inside edit popup for the field with type ‘upload’ and the ‘relationTo’ collection do nothing in context of field, it has affect only to collection.

Link to the code that reproduces this issue

Fork payload v2: https://github.com/ivan-kardash/payload/tree/edit-media-popup-issue
Repository payload v3: https://github.com/ivan-kardash/payload-edit-media-issue
Video of reproducing payload v2: https://github.com/user-attachments/assets/7eb9f2c6-92f9-43b6-b16f-8d06ebe62512
Video of reproducing payload v3: https://github.com/user-attachments/assets/d54fbe35-c0b2-4e5b-a1df-539c6e08a842

Reproduction Steps

1. Press the edit icon on the field with a schema like this: { ..., type: 'upload', relationTo: 'media' }
2. Press the button with three dots in the popup.
3. Press ‘Create New’ or ‘Delete’.

Current behavior:

• The media collection is updated.
• The field is not updated.

Expected behavior:

• The field is updated.
• The media collection is updated.

Which area(s) are affected? (Select all that apply)

plugin: cloud-storage, area: ui

Environment Info

payload: "3.0.0-beta.117"
@payloadcms/db-postgres: "3.0.0-beta.117"
@payloadcms/next: "3.0.0-beta.117"
@payloadcms/richtext-lexical: "3.0.0-beta.117"
@payloadcms/storage-s3: "3.0.0-beta.117"
@payloadcms/translations: "3.0.0-beta.117"
@payloadcms/ui: "3.0.0-beta.117"
react: "19.0.0-rc-65a56d0e-20241020"
next: "15.0.0"
node: "v22.4.1"

[github-actions]

🚀 This is included in version v3.0.0-beta.125

[github-actions]

This issue has been automatically locked.
Please open a new issue if this issue persists with any additional detail.