admin/twenty
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Fix bug on relation on custom object (#3336)

Browse Source
This commit is contained in:
Charles Bochet
2024-01-09 17:49:05 +01:00
committed by GitHub
parent 6c00aa92a4
commit 69b558e03d
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
packages/twenty-server/src/metadata/relation-metadata/relation-metadata.service.ts
View File

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