Re: Exporting PDF Reports in XML from QlikView Server

I don't believe that it will be directly possible within the server. But you could use the above mentioned macro-statement within the fat-client. Maybe with a loop through your directories and triggered per server-task which runs an app with an execute-statement which runs such a macro-app.

Re: Exporting PDF Reports in XML from QlikView Server

They're not really "lost". It's just that trying to recover user-generated content is a very tedious process at the moment. It would help a lot if Qlik would provide a method to copy-paste entire sheets - including the objects on 'em - in the GUI interface...

Re: Exporting PDF Reports in XML from QlikView Server

Yes, you are right - the reports aren't completely integrated in qv and handling them is far away from easy and beautiful. But you could (manually) export and import reports within the report-properties and you could do a copy & paste per macro. Both I have already done and it made really no fun - but should I do it again I would use export/import and use the possibilty of edit the xml-files manually and then adjust it after an import final again manually.

Here an example which read and copied the most important report-properties:

Re: Exporting PDF Reports in XML from QlikView Server

I went a little bit further in my investigation on this issue and found out a couple of things.

1) QlikView stores user created local reports in %appdata%\Roaming\QlikTech\QlikView\Reports\ in an XML file with the QlikView file name and an UUID.

Technically this one could be moved from a PC to another one, given that the UUID is replaced correctly.

The problem eventually would be replacing the ObjectIDs with new IDs of the session of another PC (as you do in the macro), but I suppose it's possible to export the XML of the original objects and recreate it in the other session and then replace the ObjectIDs with these new IDs.

2) If the user moves the report to the server, the report then is deleted locally and saved in the shared file so it is possible to get the XML only through GUI or Power Tools (SharedFileViewer). Then this report can be shared with any server user but it is impractical to know which user objects were included in the original report and to match the objects manually.

----

As a side note, I wonder if this is in any way related to the difference between the ActiveDocument.PrintDocReport, ActiveDocument.PrintReport and ActiveDocument.PrintUserReport, API functions as well (maybe another topic actually).