v1.6.7 - no more notes tab on opportunities
Hey guys!
I upgraded to the latest version this weekend, and now the notes tab is gone from the Opportunity View.
Honestly, that's pretty inconvenient 😅
I tried going to the notes object page and creating a new note, but the "relation" field stays empty even after typing the exact Opportunity name.
After a while, it shows "No record found" and stops searching, even when I try to add new text.
Thanks for the help!
Honestly, that's pretty inconvenient 😅
I tried going to the notes object page and creating a new note, but the "relation" field stays empty even after typing the exact Opportunity name.
After a while, it shows "No record found" and stops searching, even when I try to add new text.
Thanks for the help!
29 Replies
GitHub
Opportunity view - no more "notes" on the page - v1.6.7 (Docker) ·...
Bug Description I upgraded to the latest version this weekend, and now the notes tab is gone from the Opportunity View. Honestly, that's pretty inconvenient 😅 I tried going to the notes object ...
Hey @Lucas does this ring a bell to you ?
No, maybe @Raphaël
sorry to bother you, but any insights about that?
Hi,
I have a similar problem. Before upgrade to 1.6.7, i had some notes associated with company, and after upgrade when i cliking on a company view note disappears.
Look screenshot to view an example
When i display the notes list view i can see the record for the company in example and relation between the relationship between the two seems to exist
@Etienne @charles any hints ?
Could this be coming from graphqlschema refactor ?
I've checkout on v1.6.7 locally, I can' reproduce this issue - I have note tab on opportunities 🤔
damn.. I would be happy to give you more insights and even share my screen at some point. I just deployed again (as usual) to get the last docker version
Hi everybody,
And for me ? Can you said to me if the problem that i showed with my screenshot is similar or if i can create another feed ?
The note target object d'on't work correctly and task target to.
We tested with Felix and realized that it was a bit more complex than hoped...
Lets see with @charles as it may be related to the last "relation bug".
- The relation are still as standard in the object manager
- checked and reset the user rights (no changes)
- nothing has been changed in the database
I hope we'll find a way!
Up, up? It would be great to get some help with that. I’d say it’s very inconvenient.
Hi @Jb Ronssin , i have exactly the same problem with 1.6.7 and now with 1.7.3
I tried many way but for the moment i don't have the solution for issue.
I had tested to deploy an new instance and that work without note issue.
I also noticed the issue is with task.
One way i exploring is noteTarget and taskTarget table in database.
Have you custom object that are in relation with note and task in your data model ?
nope.. just the standard stuff bout notes and tasks. I believe that it's a migration problem as I jumped two small versions at the same time
Migration one by one version is a real problem ! In my case twentycrm was hosted with an easypanel instance on my server and the upgarde is automate by this app. I can't control when a new docker image was upload and deploy.
Hello there, @Félix you've debugging this with @Jb Ronssin directly ?
Hey, auto cli upgrader is planned and should be released in by the end of the year at the latest
I can't control when a new docker image was upload and deploy.You're not able to set a specific twenty version ? your issue might coming from consuming
latestYes i had set latest for docker image in easypanel. I saw that like a very convenient way to be always update. The latest version that work for me is the 1.5.3 . Do you thing is it necessary to restart with this version and upload the database i saved ?
Yes i had set latest for docker image in easypanel. I saw that like a very convenient way to be always updateYes but unfortunately it's incompatible with the incremental upgrade requirement, I personally tend to be removing the
latest mirror from dockerHub until we have released the auto-upgrader
Do you thing is it necessary to restart with this version and upload the database i saved ?Yep I would recommend doing so and incrementally upgrade to next minor, you can consume
major.minor mirrors directly such as 1.5 1.6 so you will get the latest version agnostically of the patch version
You can review your workspace verrsion at core.workspace.version
It should be equal to your twenty installed version
Your workspace version won't get updated to the next version unless they have a difference of one minor ( example 1.4.0 current workspace version and 1.5.0 installed next twenty version ) at 1.5.0 bootstrap it will search for 1.4 workspace to upgrade no commands to run if it's not updating the installed twenty instance versionIn my case i upgraded from 1.5.3 to 1.6.7 and when i look core.workspace.version, i had 1.6.7
i'm not sur to understand correctly. How can i find the last version that work for me and how can i restart an instance without issue ?
Hi @prastoin is it possible to have instructions and guideline to rebuild my instance without issue and with my saved data ?
Hello @Sebastien is that you https://github.com/twentyhq/twenty/issues/14655#issuecomment-3363634595 ?
GitHub
Search is not returning results · Issue #14655 · twentyhq/twenty
Bug Description Search is not returning any results. Example: I know for a fact that there is a Person that has a first name of "Cliff" in the database. Return object: {"data":{...
Regarding what you're telling me it does not seem to be a corruption due to miss played upgrade version.
To dig deeper I would need an access to an instance where I can reproduce the issue @Jb Ronssin @Sebastien
DAMN ! 🎉 @Félix @prastoin it went back by deploying to the last version.
Soo cool.
Thanks!
@prastoin i had also the same issue than #14655 sharing above.
I can give you an acces to my test instance who are similar than production.
Write me an mp with your email and i create that for you.
@Sebastien it seems like 1.7 contains the fix, please upgrade to the latest version
If still not working please feel free to reach out
I'm on 1.7.3 and that don't work. Relation with note and task are break, and global search to.
Please share any related errors
Also please double check your workspace version in database, to assert you've successfully upgraded to 1.7
Please try running
yarn command:prod cache:flush in your twenty-server too
Hey @marie could this initial bug related to the filtering fix you've done yesterday ?When i looking core.workspace.version i have 1.7.3
I tried to execute command but my server was down ! I restore it and retry after.
didnt read the whole thread but the problem i fixed yesterday was introduced on sept 30th or son so if the issue discussed here dates back to 22nd then no @prastoin
@prastoin i runned the command yarn command:prod cache:flush and that work good now.
Thanks for your help !
Cool ! No worries !
Feel free to reach out