Bookmarks lost after upgrade
Answered
Hi Team,
We lost our bookmarks after upgrading from 7.1 to 7.3. Is this is the expected behavior?
Do you know if there is a way to export/import this bookmarks back?
Where are the Bookmarks stored on the filesystem or on the Database?
Thanks,
Bharath
Hi Bharath,
No, an upgrade from 7.1 to 7.3 should not cause bookmarks to disappear. This sounds like a bug to me.
However, I just tried to replicate this over here and was unsuccessful, the bookmark I created in 7.1 was still available after my upgrade to 7.3.
So I suspect that the issue you have experienced may be due to a specific build of 7.1 or 7.3 (or both). Because of this, I request that you please send me your YellowfinPatchLog that you will find in the main Yellowfin folder so that I can see the specific builds of Yellowfin that were part of this upgrade.
There isn't a way to export/import bookmarks. Bookmarks are stored in the ReportInstance table. You can find them by running the following query:
regards,
David
Hi Bharath,
No, an upgrade from 7.1 to 7.3 should not cause bookmarks to disappear. This sounds like a bug to me.
However, I just tried to replicate this over here and was unsuccessful, the bookmark I created in 7.1 was still available after my upgrade to 7.3.
So I suspect that the issue you have experienced may be due to a specific build of 7.1 or 7.3 (or both). Because of this, I request that you please send me your YellowfinPatchLog that you will find in the main Yellowfin folder so that I can see the specific builds of Yellowfin that were part of this upgrade.
There isn't a way to export/import bookmarks. Bookmarks are stored in the ReportInstance table. You can find them by running the following query:
regards,
David
Hi Bharath,
ah, uninstalling and reinstalling Yellowfin, that is different than "upgrading"!
If your customer has kept the original Yellowfin configuration database then you can point the new installation of Yellowfin to that old Yellowfin database (although if the Yellowfin database is still on the 7.1 schema you will have to upgrade it to the 7.3 schema so that it is compatible with the new installation of 7.3).
The way to point a new installation of Yellowfin to a pre-existing Yellowfin database is by going to the web.xml file (\appserver\webapps\ROOT\WEB-INF) and changing the values of the parameters JDBCDriverClass, JDBCURL, JDBCUser, JDBCPassword, JDBCPasswordEncrypted so they are correct for the pre-existing Yellowfin database.
However, if the customer doesn't have the old Yellowfin database then it is not possible.
regards,
David
Hi Bharath,
ah, uninstalling and reinstalling Yellowfin, that is different than "upgrading"!
If your customer has kept the original Yellowfin configuration database then you can point the new installation of Yellowfin to that old Yellowfin database (although if the Yellowfin database is still on the 7.1 schema you will have to upgrade it to the 7.3 schema so that it is compatible with the new installation of 7.3).
The way to point a new installation of Yellowfin to a pre-existing Yellowfin database is by going to the web.xml file (\appserver\webapps\ROOT\WEB-INF) and changing the values of the parameters JDBCDriverClass, JDBCURL, JDBCUser, JDBCPassword, JDBCPasswordEncrypted so they are correct for the pre-existing Yellowfin database.
However, if the customer doesn't have the old Yellowfin database then it is not possible.
regards,
David
Hi Bharath,
I'm cleaning up my work list and I noticed this ticket is still in the "Awaiting Reply" mode, so I'm just wondering how you got on with it?
regards,
David
Hi Bharath,
I'm cleaning up my work list and I noticed this ticket is still in the "Awaiting Reply" mode, so I'm just wondering how you got on with it?
regards,
David
Hi Dave,
You may close this call, thanks for the help.
Regards,
Bharath
Hi Dave,
You may close this call, thanks for the help.
Regards,
Bharath
OK, thanks Bharath!
OK, thanks Bharath!
Replies have been locked on this page!