From 193be7228907741a7c3c982ddfb95432c30e6cc8 Mon Sep 17 00:00:00 2001
From: Etienne <45695613+etiennejouan@users.noreply.github.com>
Date: Thu, 4 Dec 2025 13:47:24 +0100
Subject: [PATCH] Null - Fix emails field (#16317)

fixes https://github.com/twentyhq/twenty/issues/16270

It happens with api user only.

Integration tests were ok because we expect a returned empty string
(check in test) even if null value is expected in db (not test). How can
we improve this ?
---
 .../record-transformer/utils/transform-emails-value.util.ts     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/twenty-server/src/engine/core-modules/record-transformer/utils/transform-emails-value.util.ts b/packages/twenty-server/src/engine/core-modules/record-transformer/utils/transform-emails-value.util.ts
index b600694c4a..1acbe02449 100644
--- a/packages/twenty-server/src/engine/core-modules/record-transformer/utils/transform-emails-value.util.ts
+++ b/packages/twenty-server/src/engine/core-modules/record-transformer/utils/transform-emails-value.util.ts
@@ -10,7 +10,7 @@ export const transformEmailsValue = (
   }
 
   let additionalEmails: string | null = value?.additionalEmails;
-  const primaryEmail = value?.primaryEmail
+  const primaryEmail = isNonEmptyString(value?.primaryEmail)
     ? value.primaryEmail.toLowerCase()
     : null;