Hello Everyone,
Is there an available node to connect knime directly with Qlik Sense?
Something like this node should be able to generate qvd files which is native to qlik sense.
I saw a node developed for tableau and was wondering whether we have something similar for Qlik Sense:smiley:
Text from KNIME log:
2020-08-13 09:40:27,680 : ERROR : KNIME-Worker-5-QVX Writer 0:862 : : Node : QVX Writer : 0:862 : Execute failed: (“ArrayIndexOutOfBoundsException”): -1
java.lang.ArrayIndexOutOfBoundsException: -1
at us.analytiq.knime.qvx.writer.QvxWriter.insertInto(QvxWriter.java:398)
at us.analytiq.knime.qvx.writer.QvxWriter.writeBody(QvxWriter.java:171)
at us.analytiq.knime.qvx.writer.QvxWriter.writeQvxFile(QvxWriter.java:78)
at us.analytiq.knime.qvx.writer.QvxWriterNodeModel.writeQvxFile(QvxWriterNodeModel.java:70)
at us.analytiq.knime.qvx.writer.QvxWriterNodeModel.execute(QvxWriterNodeModel.java:56)
at org.knime.core.node.NodeModel.execute(NodeModel.java:747)
at org.knime.core.node.NodeModel.executeModel(NodeModel.java:576)
at org.knime.core.node.Node.invokeFullyNodeModelExecute(Node.java:1236)
at org.knime.core.node.Node.execute(Node.java:1016)
at org.knime.core.node.workflow.NativeNodeContainer.performExecuteNode(NativeNodeContainer.java:558)
at org.knime.core.node.exec.LocalNodeExecutionJob.mainExecute(LocalNodeExecutionJob.java:95)
at org.knime.core.node.workflow.NodeExecutionJob.internalRun(NodeExecutionJob.java:201)
at org.knime.core.node.workflow.NodeExecutionJob.run(NodeExecutionJob.java:117)
at org.knime.core.util.ThreadUtils$RunnableWithContextImpl.runWithContext(ThreadUtils.java:334)
at org.knime.core.util.ThreadUtils$RunnableWithContext.run(ThreadUtils.java:210)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.knime.core.util.ThreadPool$MyFuture.run(ThreadPool.java:123)
at org.knime.core.util.ThreadPool$Worker.run(ThreadPool.java:246)
any idea why? i tried to play with all options in QVX Writer Node, but no success.
I am sorry that the error message is a bit confusing, this extension is located on the Community Extensions (Experimental) update site which is not enabled by default. It seems like you were able to enable it though.
The issue you are describing looks like a bug in the code. Can you confirm this is happening for all kinds of data for you or only a specific table?