From 8914ba9fece284ca150e10b217c6a8fb31a9ee5d Mon Sep 17 00:00:00 2001
From: Charles Bochet <charlesBochet@users.noreply.github.com>
Date: Wed, 8 Oct 2025 11:30:42 +0200
Subject: [PATCH] Fix RelationToOneSection assignment bug (#14975)

While refactoring SingleRecordPicker to support morph use case, we
forgot to QA RelationDetailSection for ManyToOne.
---
 .../components/RecordDetailRelationSectionDropdownToOne.tsx     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/twenty-front/src/modules/object-record/record-field-list/record-detail-section/relation/components/RecordDetailRelationSectionDropdownToOne.tsx b/packages/twenty-front/src/modules/object-record/record-field-list/record-detail-section/relation/components/RecordDetailRelationSectionDropdownToOne.tsx
index 4793222ddf..e99456949c 100644
--- a/packages/twenty-front/src/modules/object-record/record-field-list/record-detail-section/relation/components/RecordDetailRelationSectionDropdownToOne.tsx
+++ b/packages/twenty-front/src/modules/object-record/record-field-list/record-detail-section/relation/components/RecordDetailRelationSectionDropdownToOne.tsx
@@ -84,7 +84,7 @@ export const RecordDetailRelationSectionDropdownToOne = () => {
     if (!selectedMorphItem?.recordId || !relationFieldMetadataItem?.name)
       return;
 
-    onSubmit?.({ newValue: selectedMorphItem.recordId });
+    onSubmit?.({ newValue: { id: selectedMorphItem.recordId } });
   };
 
   const { createNewRecordAndOpenRightDrawer } =