Skyfox675 Posts - Answer Overflow

Skyfox675

•Created by Skyfox675 on 8/28/2024 in #❓︱help

Question about Many-to-Many relationships

Apologies if this has been answered already, is a many to many relationship possible? For example: Custom Object "Plans", has: - Personal Hosting - Business Hosting - Email Basic - Email Plus I am curious about linking the following relationships: Company A's Plans Field: - Business Hosting - Email Basic Company B's Plans Field: - Personal Hosting - Email Basic Company C's Plans Field: - Business Hosting - Email Plus Based on the weird behavior I'm seeing on each individual Plan Object I'm pretty sure this isn't possible at the moment. If not, any thoughts on if this is being considered?

3 replies

TTwenty

•Created by Skyfox675 on 8/23/2024 in #❓︱help

Webhook Event duplication

Hi team! I'm working on extending TwentyCRM with a Zapier-like automation tool called N8n (N8n.io). I'm seeing some odd behavior with how TwentyCRM is sending Webhooks. I have a custom data model called "Automations" that is effectively an extention of the standard Companies model for things such as client onboarding, system email send status, etc. I'm on v0.23.2, and I have a Webhook filtered to Automations, UPDATE events to be sent. But I'm receiving ~4 duplicate webhook payloads on a single field's value change. I've incorperated some consistancy/idempotency into my worflow to set concurrency=1 and a GET to ensure we're using TwentyCRM's latest value and not the value in the Webhook payload. This has solved the duplication issue on my end, but it is 4x the workflow execution load at the moment to filter out these events. Does anyone know what the cause could be of why so many events are being thrown? Do record view's or GET's via API cause these events to be thrown? Thanks! Additional info: Data model this is being seen on: Custom - Automations Field type: Select - esigContract Allowed values: NOT_SENT SEND QUEUED SENT VIEWED DECLINED SIGNED Example field change: NOT_SENT -> SEND

40 replies

TTwenty

•Created by Skyfox675 on 8/23/2024 in #❓︱help

Webhook Event duplication (old thread)

10 replies

TTwenty

•Created by Skyfox675 on 8/6/2024 in #❓︱help

Upgrade to v0.23.0 failing

Hi @charles hope you and team are doing well! I'm running into issues with the v0.23.0 migration following the upgrade guide on the docs page. - yarn database:migrate:prod ✅ - yarn command:prod workspace:sync-metadata -f ❌ I'm receiving the following errors after running the second command:

[Nest] 551  - 08/06/2024, 12:14:56 PM    WARN [SyncWorkspaceMetadataCommand] Workspace contains 7 issues, sync has been forced.
[Nest] 551  - 08/06/2024, 12:14:56 PM     LOG [WorkspaceSyncMetadataService] Syncing standard objects and fields metadata
[Nest] 551  - 08/06/2024, 12:14:56 PM     LOG [WorkspaceSyncMetadataService] Syncing standard objects and fields metadata
[Nest] 551  - 08/06/2024, 12:14:56 PM     LOG [WorkspaceSyncObjectMetadataService] Comparing standard objects and fields metadata
[Nest] 551  - 08/06/2024, 12:14:56 PM     LOG [WorkspaceSyncObjectMetadataService] Updating workspace metadata
[Nest] 551  - 08/06/2024, 12:14:56 PM     LOG [WorkspaceSyncObjectMetadataService] Generating migrations
[Nest] 551  - 08/06/2024, 12:14:56 PM     LOG [WorkspaceSyncObjectMetadataService] Saving migrations
[Nest] 551  - 08/06/2024, 12:14:56 PM   ERROR [WorkspaceSyncMetadataService] Sync of standard objects failed with:
[Nest] 551  - 08/06/2024, 12:14:56 PM   ERROR [WorkspaceSyncMetadataService] Error: Field demoUrl not found in originalObjectMetadata
[Nest] 551  - 08/06/2024, 12:14:56 PM     LOG [SyncWorkspaceMetadataCommand] Finished synchronizing all active workspaces (1 workspaces).

[Nest] 551  - 08/06/2024, 12:14:56 PM    WARN [SyncWorkspaceMetadataCommand] Workspace contains 7 issues, sync has been forced.
[Nest] 551  - 08/06/2024, 12:14:56 PM     LOG [WorkspaceSyncMetadataService] Syncing standard objects and fields metadata
[Nest] 551  - 08/06/2024, 12:14:56 PM     LOG [WorkspaceSyncMetadataService] Syncing standard objects and fields metadata
[Nest] 551  - 08/06/2024, 12:14:56 PM     LOG [WorkspaceSyncObjectMetadataService] Comparing standard objects and fields metadata
[Nest] 551  - 08/06/2024, 12:14:56 PM     LOG [WorkspaceSyncObjectMetadataService] Updating workspace metadata
[Nest] 551  - 08/06/2024, 12:14:56 PM     LOG [WorkspaceSyncObjectMetadataService] Generating migrations
[Nest] 551  - 08/06/2024, 12:14:56 PM     LOG [WorkspaceSyncObjectMetadataService] Saving migrations
[Nest] 551  - 08/06/2024, 12:14:56 PM   ERROR [WorkspaceSyncMetadataService] Sync of standard objects failed with:
[Nest] 551  - 08/06/2024, 12:14:56 PM   ERROR [WorkspaceSyncMetadataService] Error: Field demoUrl not found in originalObjectMetadata
[Nest] 551  - 08/06/2024, 12:14:56 PM     LOG [SyncWorkspaceMetadataCommand] Finished synchronizing all active workspaces (1 workspaces).

Any help would be appreciated, thanks!

175 replies

TTwenty

•Created by Skyfox675 on 8/1/2024 in #❓︱help

How to correctly create a custom timelineActivity with multiple relations

Hi Team!! I'm working on building some really amazing integrations with N8n.io for my TwentyCRM instance that I self host! First off thanks again for a really solid product! I'm hoping to add in some "custom" events into the Company's Timeline and a custom object of "Automation"'s Timeline for events of "contract viewed", "contract signed", etc. However I'm struggling to find a good example of how to create a timelineActivity via API. I'm using: https://twenty.com/developers/rest-api/core#/operations/createOneTimelineActivity But when I add the two relations, it starts to throw internal server errors that too many attributes (greater than 100) have been used and I cannot view the company or automation record attached to this new timelineActivity until I delete the timelineActitivy via API. It looks like properties JSON object/attribute doesn't have a schema listed, does anyone have more information on what this should look like when putting in a custom message/status? Hosting type: Docker/K8s Docker Images: - twentycrm/twenty:v0.22.1 - twentycrm/twenty-postgres:v0.22.1

4 replies

TTwenty

•Created by Skyfox675 on 7/17/2024 in #❓︱help

v0.22.0 Webhooks failing to send

After upgrading to v0.22.0 (and running db migrations) I'm now receiving the following errors in the container logs from Twenty:

[Nest] 1  - 07/17/2024, 11:25:32 PM   ERROR [SyncDriver] No handler found for job: webhook-queue
[Nest] 1  - 07/17/2024, 11:25:32 PM   ERROR [SyncDriver] No handler found for job: entity-events-to-db-queue
[Nest] 1  - 07/17/2024, 11:25:32 PM   ERROR [SyncDriver] No handler found for job: entity-events-to-db-queue

[Nest] 1  - 07/17/2024, 11:25:32 PM   ERROR [SyncDriver] No handler found for job: webhook-queue
[Nest] 1  - 07/17/2024, 11:25:32 PM   ERROR [SyncDriver] No handler found for job: entity-events-to-db-queue
[Nest] 1  - 07/17/2024, 11:25:32 PM   ERROR [SyncDriver] No handler found for job: entity-events-to-db-queue

I do have multiple Webhooks configured but payload is not being sent and doesn't appear to be attempting to make connection to the configured endpoint.

61 replies

TTwenty

•Created by Skyfox675 on 7/10/2024 in #❓︱help

v0.20.x+ has broken docker builds

Hi team! Seeing the following on container start:

Running database setup and migrations...
Need to install the following packages:
  ts-node@10.9.2

Running database setup and migrations...
Need to install the following packages:
  ts-node@10.9.2

This is when attempting to version bump from v0.12.2 ->v0.20.2

80 replies

TTwenty

•Created by Skyfox675 on 5/30/2024 in #❓︱help

Error "cannot pass more than 100 arguments to a function" when calling create "insertIntodeal"

I have a custom object called "deal"/"deals" and I am attempting to create a new deal object via Rest API and am receving the below error. However it is working via the UI when providing only a name field. Thanks in advance! 🙂

[
    InternalServerErrorException: GraphQL errors on insertIntodeal: {"message":"cannot pass more than 100 arguments to a function"}
        at computePgGraphQLError (/app/packages/twenty-server/dist/src/engine/api/graphql/workspace-query-runner/utils/compute-pg-graphql-error.util.js:30:12)
        at WorkspaceQueryRunnerService.parseResult (/app/packages/twenty-server/dist/src/engine/api/graphql/workspace-query-runner/workspace-query-runner.service.js:279:80)
        at WorkspaceQueryRunnerService.createMany (/app/packages/twenty-server/dist/src/engine/api/graphql/workspace-query-runner/workspace-query-runner.service.js:110:43)
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
        at async WorkspaceQueryRunnerService.createOne (/app/packages/twenty-server/dist/src/engine/api/graphql/workspace-query-runner/workspace-query-runner.service.js:127:25)
        at async field.resolve (/app/node_modules/@envelop/on-resolve/cjs/index.js:36:42)
        at async /app/node_modules/@envelop/core/cjs/orchestrator.js:383:27
        at async YogaServer.getResultForParams (/app/node_modules/graphql-yoga/cjs/server.js:304:26)
        at async YogaServer.handle (/app/node_modules/graphql-yoga/cjs/server.js:77:29) {
      path: [ 'createDeal' ],
      locations: [ [Object] ],
      extensions: [Object: null prototype] {}
    }
  ]

[
    InternalServerErrorException: GraphQL errors on insertIntodeal: {"message":"cannot pass more than 100 arguments to a function"}
        at computePgGraphQLError (/app/packages/twenty-server/dist/src/engine/api/graphql/workspace-query-runner/utils/compute-pg-graphql-error.util.js:30:12)
        at WorkspaceQueryRunnerService.parseResult (/app/packages/twenty-server/dist/src/engine/api/graphql/workspace-query-runner/workspace-query-runner.service.js:279:80)
        at WorkspaceQueryRunnerService.createMany (/app/packages/twenty-server/dist/src/engine/api/graphql/workspace-query-runner/workspace-query-runner.service.js:110:43)
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
        at async WorkspaceQueryRunnerService.createOne (/app/packages/twenty-server/dist/src/engine/api/graphql/workspace-query-runner/workspace-query-runner.service.js:127:25)
        at async field.resolve (/app/node_modules/@envelop/on-resolve/cjs/index.js:36:42)
        at async /app/node_modules/@envelop/core/cjs/orchestrator.js:383:27
        at async YogaServer.getResultForParams (/app/node_modules/graphql-yoga/cjs/server.js:304:26)
        at async YogaServer.handle (/app/node_modules/graphql-yoga/cjs/server.js:77:29) {
      path: [ 'createDeal' ],
      locations: [ [Object] ],
      extensions: [Object: null prototype] {}
    }
  ]

7 replies

Gaming

Programming