Cannot edit entries in RDM using Hub Personal
I am using the Hub Personal with RDM. I was fine last year using it but recently went in to add a credential and realized that I wasn't able. I then realized that I can no longer edit an existing item either in my vault. I am able to go to the Hub Personal website and do it there but that is quite cumbersome to have to go back and forth to do any adds, deletes or edits in the vault. How can this be fixed?
All Comments (10)
Hello,
Are you using the latest RDM? (2024.1.17) If you are using RDM 2023.3, your RDM is in read-only mode because it mismatches the server version. Please try updating to the latest and try again.
Have a good day!
Maxime Morin
Hi Maxime,
I also have the same issue. I can edit/add entries in my mac (version 2024.1.8.6) which is the latest version if I check from "check update", but I cannot edit/add entry on my Windows machine (version 2024.1.31.0 64-bit) also latest version. Do you have any idea?
Hello,
Are you using Hub Personal or Hub Business? With Hub Personal, we have seen some cases where the data source in RDM needs to be re-created (without duplicating the data source). Simply, create a new data source with the same email address for Hub Personal. Your data will be accessible from the new data source; no migration needed. If it works, simply delete the old data source in RDM.
Let me know if it helps, have a good day!
Maxime Morin
I'm using Hub Personal, I tried your suggestions and it works. Thank you!
Glad to hear it, have a good day!
Maxime Morin
Good morning,
it didn't work for me tho. I updated from 2024.1.28.0 to .32.0, created a new Personal Hub datasource and I still can't edit my entries. I now try to update to the version 2024.2.8.0. Haven't seen or thought that I have to update again. :D I will let you know if the problem remains.
Best regards,
Steven V.
Good morning,
it didn't work for me tho. I updated from 2024.1.28.0 to .32.0, created a new Personal Hub datasource and I still can't edit my entries. I now try to update to the version 2024.2.8.0. Haven't seen or thought that I have to update again. :D I will let you know if the problem remains.
Best regards,
Steven V.
As I thought the second update cleared the issue. But thank y'all!
Stopped working for me too. Today.
Yesterday worked fine. I've updated the client and recreate the database connection, but did not help.
BR, Mitja
98bab54e-4c41-4f6c-9345-56b542dd1f9c.png
Just tried the update again, and seems to do the trick. The clue was alet: 
But I have restarted the RDM many times in between but did not saw the alert before.
I've nov upgraded the client from 2024.1.32.0 to 2024.2.8.0 and it did automaticly the databese upgrade to version 1.12:
And now it works... :)
I do not know why, but it seem I had to do two updates one after another... to work.
Best Regards!
7adb34a7-1d70-486b-bbc6-a858758f1480.png
ed0b4bb0-dabf-460e-a0ae-e0e522bf1580.png
@mitja,
Thank you for your feedback.
Glad that is now working as expected.
Best regards,
Jeff Dagenais