In the example that @temesgen-dadi provided, the workflow works well with “CSV Reader”. However, the “Path” variable disappears if a) “File-Reader” node is selected b) you are working with a local file.
Same things happen with the “JSON reader” and a local file
Anyone understand why the “Path” variable disappears?
the file reader requires a URI as input instead of a standard string so you need to convert the string to an URI first using the String to URI node. So you workflow would look like this:
The JSON Reader does not require the String to URI node so it would look like this:
Im sorry for the inconveniences and we are working on migrating more and more nodes to the new file handling framework which will then make this workaround unnecessary. Going forward all new and migrated reader and writer nodes will only support the new Path type.
as of now we do not plan to deprecate the String to URI node. It will take some time until all nodes from us and the community that work with files are converted to the new file handling framework and some might still require a URI.