Issues after migration | Upgrade done from R12.60 SR2 (May 2021) to R12.70 SR2 (May 2022) | Object says No Data to display

[lincoln]

Document Bookmark works when opening the document locally but not from Qlikview Server. It shows "No Data to display" when the document is opened from the server.

[Maria_Halley]

@lincoln 

Did you move QlikView to a new server? Or did you just upgrade QlikView?

[lincoln]

We upgraded the qlik view.

Thanks 

[Maria_Halley]

@lincoln 

Does it work if you create a new bookmark? Or if you make the same selection manually?

[Chip_Matejowsky]

Hi @lincoln,

Did you back up the .Shared/.TShared files before performing the upgrade?

Best Regards

[lincoln]

Hi Chip,

Is it necessary to back up .Shared/.TShared files before performing the upgrade? What these file associate with?

Thank you.

[Chip_Matejowsky]

Hi @lincoln,

Backing up .Shared/.TSshared files is part of the recommended best practices in preparing for a QlikView Server upgrade or migration. See Qlik Help entry Backup and Upgrade Preparation for more details. Bookmarks are stored in the .Shared/.TShared files. Refer to Qlik KB article Shared Files - General Information for more details. 

If you have backups of the .Shared/.TShared files, you can restore them to see if the bookmarks are present. 

Best Regards

[lincoln]

Hi @Chip_Matejowsky

A simple Document bookmark (Set Director= ‘Gregory La Cava’) was implemented so you could show it to Qlik.

1. when we open the document locally, we see the chart as shown (Pic: s1).

2. If we put this document in the 12.70 server when trying to Open it in the Server, the same table will appear as (Pic s2 ). It shows the document bookmark is not considered in the expression.

3. when we put this document in QV R12.60, we will see the same table as in the (pic s1).

Is it because of the bug in the new 12.70 or could it be because of no backups of the .Shared/.TShared files?

[Chip_Matejowsky]

I don't believe there has been any bug regarding bookmarks within QV May 2023 confirmed. If you believe there is a bug, then please do open a Support case and provide a sample app and steps to reproduce the issue.

As Maria asked previously, do you have the same result if create a new bookmark?