I am struggling to get the List Files/Folders (or any other node) to accept the main workflow data area (/data/) as a Relative path either by entry or by flow variable. I have always used calculated absolute paths as a work around, but it would be way cleaner to be able to keep them as a relative path for simplicity.
The Relative to Workflow Data Area methodology seems to default to the data folder itself, but then for some reason it requires you to select a subfolder in order for it to be valid. Why wouldn’t it point to the main data folder when no sub-folders are selected? Anyone found a workaround to create relative links to the main data folder?
I created a workflow by last March to provide a solution that transferred files in Loop. Aiming to implement it working for any download from Hub, I had to make it work from Workflow Data Area.
You may take advantage of the learning curve; it works even from temporary -when executing it straight away from ‘Downloads’ folder-, without saving it into knime-workspace.
This will be helpful if I run into issues requiring temp file locations in unsaved workflows. It looks like your Relative path List File/Folder pointed to sub folders in the workflow data folder, and not the main data folder.
A relative path to the main workflow data folder seems like such a basic requirement… It feel like I must be missing something obvious since this is such a commonly used directory.
Here is a link to an Interactive View based component using this relative data file reference. It is a stand alone 1 time file launcher / folder viewer for the relative data folder contents of a workflow. It is just designed to be an easy manually controlled shortcut to make data file changes without exiting KNIME.