when you check the data, it exists in the workflow archive. What I had to do was to take out the data and point to the file in the file Excel reader node
For an example I put in the server I had to upload the data and do the same thing.
“Relative to current workflow data area” already points to the /data directory in your workflow, so removing “data/” from the selected path should fix the issue.
SimonS’ suggestion solves the problem in my local machine. I have downloaded a flow from the Hub: “14_Interactive_dasboard_netflix_shows” and deployed it to the server. The file reader config is:
it runs in my machine but not on the server. My workaround was to copy the datafile elsewhere and point to the location, but since the data folder is in the worflow file there should be a better way to solve it…
On my Mac and also Windows I had the problem that just leaving it blank did not work I had to insert “…” (two dots). Maybe it is possible to somehow rework these features and make them more consistant across operation systems.
Also I liked the concept of KNIME protocol which has been somewhat out of focus lately.
Yes I still like to use the knime protocol. In the case of the excel reader it is not possible to access multiple files at once using the protocol. Not a big deal for me since I would still prefer loops and control explicitly what I would do with such files.