Rob
New Note Errors
hi @thomast @charles @marie @Weiko , thanks for your help with this issue on the githuib issues page, as @Weiko suggested, I am reaching back out here to try and solve the issue on discord. Is there a time we could jump on a call to debug together?
https://github.com/twentyhq/twenty/issues/7231#issuecomment-2405365700
7 replies
New Note Errors
Thanks @thomast It seems this is an elusive bug, but something that heavily impacts my experience with Twenty. I have shared some additional info and docker compose in the GitHub issue. Hopefully this helps to identify what I’ve don’t wrong.
7 replies
New Note Errors
i created an issue about this here: https://github.com/twentyhq/twenty/issues/7231
7 replies
Upgrade 0.22.1 to v0.23.0 issues
@charles my upgrade to v0.23.2 from v0.22.1 is failing with the following error
I ran
yarn database:migrate:prod
and then yarn command:prod upgrade-0.23
. I also tried with yarn command:prod workspace:sync-metadata -f
in the middle
Do you have any suggestions to fix this? THANKS!36 replies
TTwenty
•Created by marie on 7/16/2024 in #🏡︱general
v0.22 upgrade warnings
@charles @marie thank you, again, for helping with my upgrade issues. And then helping to identify that I needed to delete fields to reduce below the 100 limit because of the new standard fields added in v0.22.
Just an FYI, I ran in to another problem. All my rest calls started failing even on depth =1. I’ve removed additional fields and changed depth to 0 for now. I will probably move to graphql next to optimise the queries and stay below the 100 limit. I suspect that rest queries might ignore that fields are deactivated.
I just noticed that there is a PR to add further standard fields (created by). Which will mean I need to delete more of my custom fields to ensure the webui works.
I understand that the product is in constant development and you will be adding new features and fields etc. I’m pleased to be an early user and understand that means potential bugs or that I may need to change our workflow over time. Can you provide any rough guidance as to how many custom fields you recommend I use and don’t go above for the next few months (until you switch out the underlying library)?
36 replies
TTwenty
•Created by marie on 7/16/2024 in #🏡︱general
v0.22 upgrade warnings
Thanks. I have now removed enough fields and it is working. I think it was 12+ fields to deactivate.
Thanks again for the great software
36 replies
TTwenty
•Created by marie on 7/16/2024 in #🏡︱general
v0.22 upgrade warnings
Thanks @charles and @marie . Appreciate the help. I am now trying to fix the number of fields issue. I have removed 10 fields and the people page is still not loading. I will continue to try and remove additional fields.
36 replies
TTwenty
•Created by marie on 7/16/2024 in #🏡︱general
v0.22 upgrade warnings
And I am using the docker image " image: twentycrm/twenty-postgres:v0.20.0" for the database. Should I upgrade to v0.22?
36 replies
TTwenty
•Created by marie on 7/16/2024 in #🏡︱general
v0.22 upgrade warnings
@charles I can jump on a call. Can you do in 20 min from now?
36 replies
TTwenty
•Created by marie on 7/16/2024 in #🏡︱general
v0.22 upgrade warnings
Thanks @marie please let me know if there is anything I can do/share to make it easier for you. I can also jump on a call if that’s easier for you. Thanks again
36 replies
TTwenty
•Created by marie on 7/16/2024 in #🏡︱general
v0.22 upgrade warnings
Thanks @marie . I am upgrading from 0.21 to 0.22 (0.21 seemed to work perfectly for the last few weeks). Sending you the db dump now
36 replies
TTwenty
•Created by marie on 7/16/2024 in #🏡︱general
v0.22 upgrade warnings
Thanks @marie I have attached both info as csv files. Thanks for your assistance!
36 replies