I am trying to configure a wrapped Metanode to make a workflow easily useable for others by only specifying some options at the Beginning.
I ran into two Issues I cannot solve:
The order of the Quickforms seems to be random, before there was the weighing option in the Quickforms to handle the appearance. Is there a Similar Option or any way to influence this?
For the user it is really unconvenient to have a random order of related inputs.
Earlier I used the file uploader to let the user specify a file URL for an output file, now I am getting an Error if the file does not exist, hence the workflow does not work. The deprecated node I used before is not shown in the Metanode Dialog when used. Is there a Quickform which allows the User to specify a file URL by browsing his files?
Thank you in advance for your help. Looking forward to your Ideas.
thank you so much for the quick reply.
I never noticed that button, great but I did try it out and the Metanode shows me that the rows are changed:
But the metanode itself does not change the appearance: (eg The Molecule column entry should be in row 2)
(I did close and reload the workflow and afterwards whole KNIME but it did not change)
The file chooser node somehow only lets me chose from my KNIME workspace I guess I am missing out on the right configuration? If I am trying to Browse the RootPath I get the error:
“No server mountpoint was found for selection of root path. Please log into a server you want to use for browsing.” Not sure where I am going wrong or missing a config step.
As for the System I am using its Ubuntu 16.04LTS and KNIME 3.5.2 just in case its not me but the System missing out on something
Sorry for so many questions,
is there any update on this? Am I messing up or should I check my KNIME installation?
Would be great to get a solution!
the ordering Roland mentioned is only used for the KNIME Webportal, or if you open the composite view on the wrapped metanode. The order in the dialog is defined by first come first. You cannot change this afterwards.
Hi Iris, thank you for the clarification. So for the normal wrapped metanode the ordering is really random? Is there a reason why the ordering functionality was not continued?
Did you get the File Chooser node working? If so, how?
Unfortunately not, I am still using the old deprecated node. But to be honest since the update to 3.5.3 I also did not try it again.
So I would assume you ran into the same Error?
Yes - I wanted to allow the user to select a file within a specific folder on a filesystem, but cannot figure out how to configure to achieve it. I could use the File Upload, but then I lose the path to the file, which is something I want to track!
@Iris / @RolandBurger - any pointers to how we do this?
It would be great to get a solution.
So I assume the file Path of the File Upload variables is not enough?
From where do you want to select the file? From a local client via the WebPortal? Or just from your local machine? As you said, the File Upload node won’t give you the path to the original file if you run it on the WebPortal (it does, however, when run locally). Can you please confirm which file path you need?
I want to be able to pick a file from the webportal, from a directory which is accessible to the webportal host machine, and get the path to the selected file. Ideally, I would like to be able to give the user a starting top level directory to browse from.
Thanks for confirming. As you might have guessed already, that is currently not supported. I’ll check with our devs if this is something we can implement!
Thanks @RolandBurger. That would be a great addition!
Hi Steve, Does the ‘File Chooser’ quickform node allow you to do what you need?
@jonfuller - no. We want to be able to choose a file (ideally with extension filter, and a starting folder to look in), and return the path to that file in the webportal. As far as I can figure neither the File Chooser nor the Upload File nod will do what we want (we want to store the path, and then process the file downstream in the workflow - that path is important in our application!)
Thanks for the info Steve. That makes sense. As we move towards distributed executors real file paths on the server start to have less meaning to a remote executor which is one reason that we’ve been adding KNIME protocol support to most nodes. It also makes it much easier to control access to files/workflow groups.
@jonfuller - great suggestion (actually I already use almost exactly that approach for selecting various databased fields!). Thanks!
Hi @jenniferh / @Iris
I’ve just had the same problem with quickforms order in a wrapped metanode dialogue box.
Fortunately I’ve found a work around - the order of the quickforms in the dialogue box appears to be driven by the NodeID number (lowest at the top to highest at the bottom). So I copied each of my out of sequence quickform nodes and pasted them back into the workflow, followed by connecting them to the pipeline being careful to get the NodeIDs in the sequential order I want. I then check to ensure the settings were correct for the “new” duplicate quickform nodes before deleting their old equivalents. The order of the quickforms was now in the order I wanted!
Hopefully you already know this but I thought it good to get this up on the forum in case other folks encounter the same problems.
thanks for the work-around! I suspected as much but to be honest I never tried it out as I would have had to copy and paste about 20 nodes.
But its great to know it works, then I will actually consider doing this for better usability of the node