this is not too obvious, but I think the node in your first screenshot seems to expect the Path as String type as you only see variables of type string.
Your Path variable is of type FSLocationVariableType:
Let’s say I agree that it’d be great if all nodes handled it this in the same and consistent way… however for now some support Path Data Type whilst others require Path as String. This can be a bit problematic in cases where workflows may be used on different Operating Systems - e.g. Windows and Mac - one file system uses forward the other backslash…
Something I cam across a while back is that you can actually use both forward slash or back slash in Windows in KNIME and it doesn’t care.
You can even mix and match in the same path
e.g. c:/temp\somefolder/anotherfolder/PowerBI_sample.accdb
will work fine as a string!
The String to Path node converts it without problem, and it can be used directly in nodes that still use String instead of Path variables, so happy days!
So my suggestion if having to build string paths is just use forward slash for everything and it should work across all platforms. It also makes building in string manipulation much simpler as you don’t need to worry about “escaping” backslashes
As you can see, the Access Connector is happy with that jumbled path string too:
@takbb I do not like such mixes. They tend to cause trouble somewhere down the road. Also I use these paths in R or Python nodes. But indeed to use one type might just work.
Hi @mlauber71 - lol, I’m not recommending that they be mixed, but just giving a demonstration that KNIME on Windows handles both (I’m not crazy about mixing either)
I confess I hadn’t tried it with R and Python, so I should add a health warning to my suggestion of just using forward slash. Be interesting to know if it works ok for those too.