🅹🅰🆈🅱🅴🅴 Posts

🅹🅰🆈🅱🅴🅴

•Created by 🅹🅰🆈🅱🅴🅴 on 8/7/2024 in #❓︱help

Upgrade 0.22.1 to v0.23.0 issues

Following the guide I'm running

yarn database:migrate:prod 
yarn command:prod workspace:sync-metadata -f 
yarn command:prod upgrade-0.23

yarn database:migrate:prod 
yarn command:prod workspace:sync-metadata -f 
yarn command:prod upgrade-0.23

But during workspace-sync I receive:

0:11 PM   ERROR [CompositeColumnActionFactory] Current property not found for altered property: primaryLinkLabel
[Nest] 762  - 08/07/2024, 2:10:11 PM   ERROR [WorkspaceSyncMetadataService] Sync of standard objects failed with:
[Nest] 762  - 08/07/2024, 2:10:11 PM   ERROR [WorkspaceSyncMetadataService] Error: Current property not found for altered property: primaryLinkLabel

0:11 PM   ERROR [CompositeColumnActionFactory] Current property not found for altered property: primaryLinkLabel
[Nest] 762  - 08/07/2024, 2:10:11 PM   ERROR [WorkspaceSyncMetadataService] Sync of standard objects failed with:
[Nest] 762  - 08/07/2024, 2:10:11 PM   ERROR [WorkspaceSyncMetadataService] Error: Current property not found for altered property: primaryLinkLabel

if I then continue with next command I get:

36 replies

TTwenty

•Created by 🅹🅰🆈🅱🅴🅴 on 8/1/2024 in #❓︱help

Upgrade issue to 0.22

Running on my test server to see if upgrade process from 0.11 to 0.22 During start of containers a migration is run automatically so I assume migrate is not needed anymore so I am not running yarn database:migrate:prod manually anymore when i first run workspace-sync i receive an error (see comment, too long message) then I run command:prod upgrade-0.22 it also receives error:

[Nest] 519  - 08/01/2024, 10:56:31 AM     LOG [UpdateMessageChannelSyncStageEnumCommand] Running command on workspace 75f6e77a-ec52-43fd-af2b-5e1ca8319b2e failed
[Nest] 519  - 08/01/2024, 10:56:31 AM   ERROR [UpdateMessageChannelSyncStageEnumCommand] Migration failed for workspace 75f6e77a-ec52-43fd-af2b-5e1ca8319b2e: type "workspace_6zezc5oiagj6yqldcepfgb226.messageChannel_syncStage_enum" does not exist
[Nest] 519  - 08/01/2024, 10:56:31 AM     LOG [UpdateMessageChannelSyncStageEnumCommand] Command completed

[Nest] 519  - 08/01/2024, 10:56:31 AM     LOG [UpdateMessageChannelSyncStageEnumCommand] Running command on workspace 75f6e77a-ec52-43fd-af2b-5e1ca8319b2e failed
[Nest] 519  - 08/01/2024, 10:56:31 AM   ERROR [UpdateMessageChannelSyncStageEnumCommand] Migration failed for workspace 75f6e77a-ec52-43fd-af2b-5e1ca8319b2e: type "workspace_6zezc5oiagj6yqldcepfgb226.messageChannel_syncStage_enum" does not exist
[Nest] 519  - 08/01/2024, 10:56:31 AM     LOG [UpdateMessageChannelSyncStageEnumCommand] Command completed

if I then run workspace-sync again it works and then I can run command:prod upgrade-0.22 again without error followed up with workspace-sync without error. Is this expected behaviour or is there a better way then just "rerun both commands twice"? I noticed that if I run

yarn command:prod upgrade-0.22:fix-object-metadata-id-standard-id

yarn command:prod upgrade-0.22:fix-object-metadata-id-standard-id

before running workspace-sync i seem to get around this "run twice" behaviour, is this the/a correct solution?

25 replies

TTwenty

•Created by 🅹🅰🆈🅱🅴🅴 on 5/14/2024 in #❓︱help

v.0.11.2 Column syncStatus type is not the same as the field metadata type

After upgrade to 0.10 this error showed up in workspace health and in 0.11.2 it still persists. Is it possible to manually correct or will it be correct in future releases?

8 replies

TTwenty

•Created by 🅹🅰🆈🅱🅴🅴 on 4/23/2024 in #❓︱help

Upgrade error 0.3.2 > 0.3.3 : duplicate key value violates unique constraint

duplicate key value violates unique constraint "IndexOnNamePluralAndWorkspaceIdUnique"

yarn command:prod workspace:health -w  75f6e77a-ec52-43fd-af2b-5e1ca8319b2e

yarn command:prod workspace:health -w  75f6e77a-ec52-43fd-af2b-5e1ca8319b2e

reports healthy but:

yarn command:prod workspace:sync-metadata -w 75f6e77a-ec52-43fd-af2b-5e1
ca8319b2e -d

yarn command:prod workspace:sync-metadata -w 75f6e77a-ec52-43fd-af2b-5e1
ca8319b2e -d

fails with:

detail: 'Key ("namePlural", "workspaceId")=(activityTargets, 75f6e77a-ec52-43fd-af2b-5e1ca8319b2e) already exists.'

detail: 'Key ("namePlural", "workspaceId")=(activityTargets, 75f6e77a-ec52-43fd-af2b-5e1ca8319b2e) already exists.'

I tried deleting in "metadata"."objectData" to see if it had any effect but it did not:

 
delete from "metadata"."objectMetadata" where "namePlural"='activityTargets';
DELETE 2

 
delete from "metadata"."objectMetadata" where "namePlural"='activityTargets';
DELETE 2

217 replies

TTwenty

•Created by 🅹🅰🆈🅱🅴🅴 on 3/14/2024 in #❓︱help

GraphQLError: Variable "$orderBy" got invalid value { position: "AscNullsFirst" }; Field "position"

Testing upgrade from 0.3.0 to 0.3.1 we get this error. I have added the field "position" to company/people/opportunities but I am still getting it. I suspect it might be an issue with updating the TypeORM layer but I am not sure if this is the actual issue. Is there a way to add this Field and continue with the current data?

141 replies

TTwenty

•Created by 🅹🅰🆈🅱🅴🅴 on 2/1/2024 in #❓︱help

STORAGE_LOCAL_PATH relative, why?

Why is storage set relative to process.cwd? https://github.com/twentyhq/twenty/blob/8abd5be4b5f174e02be5b35141c5490ddc51ee20/packages/twenty-server/src/integrations/file-storage/file-storage.module-factory.ts#L26

5 replies

Gaming

Programming