From 0959b86f98bf9bf7e5b60eb8cc42053e0947664e Mon Sep 17 00:00:00 2001 From: Weiko Date: Tue, 30 Sep 2025 19:07:12 +0200 Subject: [PATCH] fix view update in migration v2 (#14794) Legacy from early v2 implementation, we don't want to store relation ids in the cache as the new implementation handle that with flat entities properly already. This causes some issues because when we return the updated view, it contains an array of viewField objects with only the id in it so gql complains because some fields are non-nullable in the output and the resolver can't resolve viewField directly because viewField is in the output (not complete though) already so it just ignores it. --- .../services/workspace-flat-view-map-cache.service.ts | 6 ------ 1 file changed, 6 deletions(-) diff --git a/packages/twenty-server/src/engine/core-modules/view/flat-view/services/workspace-flat-view-map-cache.service.ts b/packages/twenty-server/src/engine/core-modules/view/flat-view/services/workspace-flat-view-map-cache.service.ts index fcf0f36c94..f347168c8a 100644 --- a/packages/twenty-server/src/engine/core-modules/view/flat-view/services/workspace-flat-view-map-cache.service.ts +++ b/packages/twenty-server/src/engine/core-modules/view/flat-view/services/workspace-flat-view-map-cache.service.ts @@ -34,12 +34,6 @@ export class WorkspaceFlatViewMapCacheService extends WorkspaceFlatMapCacheServi workspaceId, }, withDeleted: true, - relations: ['viewFields'], - select: { - viewFields: { - id: true, - }, - }, }); return generateFlatViewMaps(views);