Handling of .qwv and .qvf files in QlikView 12.70 May 2022

[Daniele_Purrone]

Starting with QlikView 12.70, .qvf is now the default format in QlikView.

The contemporary existence of .qvf and .qvw files with the same name might result in conflicts (for instance, when having to deal with a unique .Tshared file), and this is how the Desktop Client and Server handle that.

The reasoning behind this was a move towards a common format for QlikView and Qlik Sense, primarily as QlikView files have already been distributed to Cloud where they are converted after the fact. Switching to QVF allows for more seamless integration into Qlik Cloud and provides a common format.

The .qvf file format takes priority over the legacy .qvw format. 

This is what happens with the different parts of the product:

1. Saving files in the Desktop client
   

   When trying to save a file with the same name, but different extension, the desktop client will alert you to avoid mix-ups
   
   
   
   However, it will not prevent you from saving the file.
   
   
   

2. Opening files in the access point
   

   If the files are stored in two different folders on the file system, they will both be openable (behaviour fixed in SR1).
   If the files are stored in the same location, the .qvw will be grayed-out and won't be openable.
   
   

3. Open In Server in the Desktop Client
   

   If the files are stored in two different folders on the file system, they will both be openable (behaviour fixed in SR1).
   If the files are stored in the same location, the .qvw will be grayed-out and won't be openable.
   
   
   

4. Editing Source Documents in QlikView Management Console (QMC).
   

   When stored in two different folders, the file names will look normal.
   When stored in the same folder, the .qvw will be marked in red and a pop-up will appear when hovering over the name alerting over the presence of a duplicate
   
   
   
   

5. Editing tasks in the QMC
   

   When stored in two different folders, the task  names will look normal.
   When stored in the same folder, the task will be marked in red and a pop-up will appear when hovering over the name alerting over the presence of a duplicate
   
   
   
   

Known issues (to be fixed):

1. As of October 2022, it is not possible to publish a .qvf to the Qlik Cloud via the QlikView Publisher. Manual upload works. Publishing .qvw files also works
2. test.QvW and test.qvf  are currently seen as two documents and not one.

Related Content:

QlikView May 2022 (12.70): .qvf is the new default file format for saving files - how to change that...

[AdamBS]

Hi @Daniele_Purrone 

I don't recall seeing a "why" reasoning for QV creating .QVF files; do you know of one?

I experience no metadata from .QVF QlikView Apps, is this expected?  When opening a .QVW as an XML file you'd see the metadata.

Thanks, Adam

[Sonja_Bauernfeind]

Hello @AdamBS 

This would be a question best taken to our product management team. I will see if I can get an answer for you for this, but it may be necessary to have this run through an official support case. Will update you whether or not we need one.

All the best,
Sonja 

[Sonja_Bauernfeind]

Hello again, @AdamBS 

The reasoning behind this was a move towards a common format for QlikView and Qlik Sense, primarily as QlikView files have already been distributed to Cloud where they are converted after the fact. Switching to QVF allows for more seamless integration into Qlik Cloud and provides a common format. The legacy QVW format continues to exist on-premise if users prefer the old format. 

For the second question I would need to request a case for an investigation; include what you are attempting to achieve so we can best help you.

All the best,
Sonja  

[AdamBS]

Thanks Sonja - of course, it makes sense. As for the access to metadata, please don't worry, it is something we only need during a migration from QV to QS; and that won't be an issue in a few years.  All the best, Adam