We recently upgraded to 3.7.2 and we are facing issue using the Send To Tableau (Hyper) node when values are passed using the flow variables. These settings used to run fine in 3.7.1
ERROR Send to Tableau Server (Hyper) 2:1260 Execute failed: Bad Request: Invalid page number '2' (Error code: 400006).
DEBUG Send to Tableau Server (Hyper) 2:1260 Execute failed: Bad Request: Invalid page number '2' (Error code: 400006).
org.knime.ext.tableau.hyper.sendtable.api.RestApiConnection$TsResponseException: Bad Request: Invalid page number '2' (Error code: 400006).
at org.knime.ext.tableau.hyper.sendtable.api.RestApiConnection.checkResponse(RestApiConnection.java:463)
at org.knime.ext.tableau.hyper.sendtable.api.RestApiConnection.get(RestApiConnection.java:454)
at org.knime.ext.tableau.hyper.sendtable.api.RestApiConnection.existsDatasource(RestApiConnection.java:257)
at org.knime.ext.tableau.hyper.sendtable.SendToTableauHyperNodeModel.execute(SendToTableauHyperNodeModel.java:159)
at org.knime.core.node.NodeModel.execute(NodeModel.java:733)
at org.knime.core.node.NodeModel.executeModel(NodeModel.java:567)
at org.knime.core.node.Node.invokeFullyNodeModelExecute(Node.java:1186)
at org.knime.core.node.Node.execute(Node.java:973)
at org.knime.core.node.workflow.NativeNodeContainer.performExecuteNode(NativeNodeContainer.java:559)
at org.knime.core.node.exec.LocalNodeExecutionJob.mainExecute(LocalNodeExecutionJob.java:95)
at org.knime.core.node.workflow.NodeExecutionJob.internalRun(NodeExecutionJob.java:179)
at org.knime.core.node.workflow.NodeExecutionJob.run(NodeExecutionJob.java:110)
at org.knime.core.util.ThreadUtils$RunnableWithContextImpl.runWithContext(ThreadUtils.java:328)
at org.knime.core.util.ThreadUtils$RunnableWithContext.run(ThreadUtils.java:204)
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)
Our ticketing system indicates this fix was pushed in KNIME 4.0. Are you still seeing the Invalid page number ‘2’ error, or is the log indicating something different?
The ‘Invalid Page’ is fixed. Thanks for that but we cannot use a flow variable for password.
Our password expires every month and it would be great to if we can update the password via flow variable. Our workflows are designed in such a way that it reads the credentials from a file based on user and passes on as flow variable to these nodes. We replace the file for any credential change. This helps us to avoid touching the node config. It would be great if we can get the flow variable working for Password field as well. Thanks
Username and Password through flow variable still does not work for us in 4.1. Could you please share a screenshot of the Tableau server setting tab ? It throws an error while selecting the project.
Ah, I see the problem now. To be able to select the appropriate project, the node configuration requires that valid entries are present for both the username and the password (and it won’t take the flow variables into account for this part), which is what I did above.
But after doing some more testing just now, I realize that the node doesn’t appear to be using the values for the flow variables at all - it only uses what’s been manually entered in the node configuration.
Sorry for the the trouble. Let me run this by the developers.
Curious if this has been resolved yet? Have a similar workflow where I would like to pass the UserID and Password to the “Send to Tableau Server” node using flow variables.
Also curious about the encryption method used for the password-enc flow variable in the Tableau node. I can’t find documentation on it and not sure what method I should use to encrypt or hash the password.
There is a ticket for this in the system (AP-14093) and the dev team has recently been working on revamping the Tableau nodes for the next KNIME release. So - this fix is not in place yet, but hopefully soon. Sorry for the trouble.
while looking into this issue it turned out to be more complicated than expected, hence we will not be able to ship the fix with 4.2., though we added a better error message.
Please excuse the inconveniences we’re causing you