How to export data from a sense table to a custom folder?

[michael_klix]

In my app, I need to export the content of a table to a special directory, where another application will pick the file and load it for further processing. This shall be as automized as possible. Today, we have to use the export to Excel, then open the file, save it as CSV and store it in the correct location manually.

• Format shall be ideally csv with a delimiter like '|' , but even excel would not be a showstopper.
• Location shall be ideally a shared drive that can be reached from the client PC where the App is run.
• The trigger for export shall be a button, but I am open for other options, too 🙂

Thanks a lot for any idea.

[dplr-rn]

to make it a custom location. you may need to use nprinting and output it as excel

[michael_klix]

Thanks for the hint. But currently NPrinting is not an option. I know from NPGeomaps that it is possible to create an export dialog in a way to choose the path... so there should be a way. Maybe te´here is already some "Export-Extension"?

[michael_klix]

Meanwhile, I found the great little extension from Stefan Walther:

https://developer.qlik.com/garden/57882593dd42cf18d2312a05

It is a big step forward but still lacks the custom directory. 

[vitaliichupryna]

Hi Michael,

Have you solved this problem? 

Thanks,

Vitalii

[michael_klix]

Hi, unfortunately no. Usually browser features are used an cannot be pre-configured. I still would appreciate any hint. Currently we use a rather customized extension that directly pushes data into a database via http post commands. It is not generically applicable.
But finally we reached our goal to export specific data on the push of a button.
Would be great to see this once as a sense feature.

Keep qliking
Michael

[rnorris]

Hi, did you ever find a solution to this? I need to do the same where I export to a specific folder.

[michael_klix]

Unfortunately no, as the export uses the browser function.
There is a workaround, however: Some browsers open a window to define the target folder instead of using a default. This may help, but the good old IE that does it this way is not really the one we should use 😉