#Microsoft integration with Email visibilty fails

1 messages · Page 1 of 1 (latest)

stray belfry
#

Hi there, we are running a twenty docker setup on version 0.41.15 and are stumbling across this error:

 BaseGraphQLError [GraphQLError]: Value "SHARE_EVERYTHING" does not exist in "MessageChannelVisibilityEnum" enum. Did you mean the enum value "share_everything"? 

Found out that the enum default workspace_<id>."messageChannel_visibility_enum" a problem is. Our default value is in lowercase instead of the uppercase default value.
This only happens when i try to select visibilty setting of the email settings.

#

Microsoft integration with Email visibilty fails

golden stump
#

Hi, did you upgrade recently?

#

that was 9 month ago. You must have old metadata remaining from an upgrade

stray belfry
#

Hey, yes we upgraded from 0.35 to 0.40 recently and now i wanted to upgrade from 0.40 to 0.41. We are using Twenty since june of 2024 so we could have some old metadata, is there any way to fix this or do we have to start over?

golden stump
#

There were probably a command that migrates that enum. Either you look for it either you update manually the enum default value in you DB. Since this is your only issue, not sure it worth starting over. But before you do it, you should still export your data

stray belfry
#

Alright, i tried to look for a command but havent found anything :(. Also tried changing the enum values to uppercase but than i get:

 [
    BaseGraphQLError [GraphQLError]: Enum "MessageChannelVisibilityEnum" cannot represent value: "SHARE_EVERYTHING"
        at new BaseGraphQLError (/app/packages/twenty-server/dist/src/engine/core-modules/graphql/utils/graphql-errors.util.js:86:9)
        at generateGraphQLErrorFromError (/app/packages/twenty-server/dist/src/engine/core-modules/graphql/utils/generate-graphql-error-from-error.util.js:14:26)
        at /app/packages/twenty-server/dist/src/engine/core-modules/graphql/hooks/use-graphql-error-handler.hook.js:38:194
        at Array.map (<anonymous>)
        at handleResult (/app/packages/twenty-server/dist/src/engine/core-modules/graphql/hooks/use-graphql-error-handler.hook.js:36:66)
        at handleStreamOrSingleExecutionResult (/app/node_modules/@envelop/core/cjs/utils.js:113:5)
        at onExecuteDone (/app/packages/twenty-server/dist/src/engine/core-modules/graphql/hooks/use-graphql-error-handler.hook.js:73:74)
        at /app/node_modules/@envelop/core/cjs/orchestrator.js:391:42
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
        at async YogaServer.getResultForParams (/app/node_modules/graphql-yoga/cjs/server.js:304:26) {
      path: undefined,
      locations: undefined,
      extensions: { code: 'INTERNAL_SERVER_ERROR' }
    }
  ]
golden stump
#

Hi @stray belfry , do you still have issues with this enum?

stray belfry
#

Yes, this issue is still going on. We have since then upgraded to v0.50.3, but i encountered more and more issues.