Columns getting mutilated after addition of multiple objects/ fields.
The number of fields returned by the graphql is changing after addition of multiple objects. They stop showing on the front end and all the tables do not show. This is happening on both self hosted and the cloud version.
Why is this happening?
9 Replies
Could you write a scenario to reproduce the issue?
I am sharing a module named workspace-modifications. Please put this inside core modules, add WorkspaceModificationsModule to core-engine.module.ts
Subsequently, call the controller create-metadata-structure. You will find that the database is getting mutilated as the job proceeds to add the functions of jobCreationService.executeJobCreationFlow
Let me know if you need any help in setting up the workspace-modifications controller
To be honest, that's way above my knowledge, I'd wait for someone from core team to answer this question as I don't know how to answer this question (also, what version of Twenty are you using as on 0.40.0-canary there's no
packages/twenty-server/src/engine/integrations
folder, I've fixed most of the errors related to importing except for the TokenModule import in workspace-modifications.service.ts
)I am on 0.20, but the problem persists in the hosted cloud version as well.
To test the cloud version, run this postman collection:
https://arx-twenty.postman.co/workspace/Arx-Twenty-Dev~a596b9cf-950a-47c8-a067-b5ca4b5da393/folder/28416978-b2778616-2efc-4b1e-aaeb-34f259ce1a7e?action=share&creator=34243102&ctx=documentation&active-environment=34243102-f670a21c-6508-4bae-9243-3e7e307c3fda
I don't have an access to this colelction as my account doesn't belong to your (arx-twenty) team, could you write which endpoint with what data you used to reproduce it or export collection as JSON (or other format) and send it here?
Please DM me your email and I’ll add you to the collection.
Since it’s a series of objects and fields added (30-40) it’ll be difficult to paste them here in a way that makes sense. The best thing is to run the collection which sequentially adds the objects, fields, relations and finally the data rows in different objects.
@arnavsaxena Perhaps you create an issue with an attached contribution/PR. If the core team sees a reason to merge they'll be able to do it quickly.
I've sent you a DM with email
Hi, @Raph I have created a pull request with workspace-modifications :
Workspace Metadata modifications mutilates the Metadata Responses/ Graphql #9361
@ɃØĦɆᵾS , I have also shared access to the postman. I have also made edits to the TokenModule problems you were facing. I have tested this in 0.40.0- canary and should work seamlessly. You can also take a pull request of the workspace-modifications branch that I have created a PR for which can be used for testing.
Also, you can now checkout the branch workspace-modifications. Then, starting with a new workspace, click on the workspace-modifications button created in the settings>general and replicate the issue.