Qlikview extension does not work in KNIME 5.3

Hello,
I have noticed that the Qlikview extension was not added to the new KNIME Community Extensions (Experimental) update site for KNIME 5.3 but it remained in the 4.6 version.
When I tried however to add this site to my sites list and install the extension now, I could see it but it couldn’t install because I am missing some requirements which is normal.
My question is therefore if the extension will be added to the 5.3 update site or it will not be supported anymore? And if anyone knows a getaround I’d be very happy!

Thanks a lot.
Cheers!

Cristian

@qvx123

Hello @rastasanu,

The QlikView extension was created as part of a grad student project and is unfortunately no longer maintained. It hasn’t been added to the KNIME 5.3 update site, and we’re not sure if it will be in the future.

As a workaround, consider using Qlik Sense’s ability to connect to various databases (like Oracle, PostgreSQL, and DynamoDB) via KNIME’s database connector nodes.

Best,
Keerthan

4 Likes

Hi @rastasanu,

Adding to Keerthans message above. Qlik usually allows you to export files in different file formats as well. Is there any specific reason why you want to read/write Qvx files?

Best regards

2 Likes

Hi and thanks for the answers @julian.bunzel @k10shetty1 !

The reason is that I am working at implementing KNIME in a company where they use extensively Qlik so having a way to generate directly in a Qlik native format would work better in terms of metadata than an Excel file (since they don’t use much DB solutions).

Cheers,
Cristian

2 Likes

@rastasanu is it possible to provide some sample file of a QVX file you would want to import and also some dummy data you would want to get transformed into a qvx file.

Since there is a description out there it might be possible to have some sort of parser.

The next question would be if it might make sense to employ CSV or another format like parquet to transfer data.

3 Likes

Hi @mlauber71

Thanks for the input and the interest!

I think however that I would rather try to make them use another format like CSV or Excel as developing a parser would take some time and there is not a specific need to do that right now.
I was just thinking that if the extension would’ve worked then it would be a nice-to-have addition to the node portfolio that they could use.

Thank you all again and I will come back to the forum if there will be a specific need and if I would need help developing such a parser!

Cheers and have a great day!

Cristian

4 Likes

Thanks @rastasanu for providing more context.
I’ll pass it to the product team and we might pick this topic up again in the future.

4 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.