From 69b558e03d5c76f8f7c714c913db245dfe27fd40 Mon Sep 17 00:00:00 2001
From: Charles Bochet <charlesBochet@users.noreply.github.com>
Date: Tue, 9 Jan 2024 17:49:05 +0100
Subject: [PATCH] Fix bug on relation on custom object (#3336)

---
 .../relation-metadata/relation-metadata.service.ts       | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/packages/twenty-server/src/metadata/relation-metadata/relation-metadata.service.ts b/packages/twenty-server/src/metadata/relation-metadata/relation-metadata.service.ts
index d23f9f845..e93c1a080 100644
--- a/packages/twenty-server/src/metadata/relation-metadata/relation-metadata.service.ts
+++ b/packages/twenty-server/src/metadata/relation-metadata/relation-metadata.service.ts
@@ -120,9 +120,10 @@ export class RelationMetadataService extends TypeOrmQueryService<RelationMetadat
     }
 
     const baseColumnName = `${camelCase(relationMetadataInput.toName)}Id`;
-    const isToCustom =
-      objectMetadataMap[relationMetadataInput.toObjectMetadataId].isCustom;
-    const foreignKeyColumnName = isToCustom
+
+    // TODO: this logic is called to create relation through metadata graphql endpoint (so only for custom field relations)
+    const isCustom = true;
+    const foreignKeyColumnName = isCustom
       ? createCustomColumnName(baseColumnName)
       : baseColumnName;
 
@@ -149,7 +150,7 @@ export class RelationMetadataService extends TypeOrmQueryService<RelationMetadat
         icon: relationMetadataInput.toIcon,
         isCustom: true,
         targetColumnMap: {
-          value: isToCustom
+          value: isCustom
             ? createCustomColumnName(relationMetadataInput.toName)
             : relationMetadataInput.toName,
         },