Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
["ticketsbytype","YmubDR"],
["ticketsbyproblem","BDxcGUF"],
["ticketsbydept","QxJnLNp"],
["tickettrend","hZatsK"]
];
me.createExport();
//...... some stuff here
angular.forEach(me.exportXLS, function(value, key) {
app.obj.app.getObject('QV'+value[1],value[1]).then( function( vizModel ) {
// Prevent clicking on the button too early
$('#'+value[0]).show();
$('#'+value[0]).on('click', function() {
vizModel.exportData().then(function( reply ) {
console.log(reply.qUrl);
window.open(reply.qUrl);
});
});
});
});
}
Thanks Ragul
After hours of looking, yes, Desktop uses Exports and the server used TempContent. When I created in Desktop version, then pushed to Server, somehow, the Exports carried over. I restarted the Server Engine and it started using the TempContent.
I think it is a combination of learning how Qlik works (Desktop vs Server side) and angular coding.
As of now, exportData() is now working as expected. Data is being downloaded correctly.
Thanks for your time
Les
Are the exportdata() extensions used in Desktop version. Then you may find differences in the temp folder path for Desktop and Server.
Example :
Desktop : Qlik\Sense\Exports\
Server: C:\ProgramData\Qlik\Sense\Repository\TempContent
"Exported files are temporary and are available only for a certain time span and only to the user who created them."
For more information on ExportData method Refer :
Thanks Ragul
After hours of looking, yes, Desktop uses Exports and the server used TempContent. When I created in Desktop version, then pushed to Server, somehow, the Exports carried over. I restarted the Server Engine and it started using the TempContent.
I think it is a combination of learning how Qlik works (Desktop vs Server side) and angular coding.
As of now, exportData() is now working as expected. Data is being downloaded correctly.
Thanks for your time
Les