Transfer Files (Table) doesn't rename anymore

I have a workflow moving the processed file to an archive folder at the end. This worked perfectly until very recent. The node now fails and reports the source file was not found. I invested quite some time debugging with the result, that the source was (still) absolutely ok (tested it with various other nodes and it worked). After some additional tests, I found out, that the only input the node accepts as destination is a folder. Bad news for my workflow(s) as I move and rename the file so I need a file as destination. Any idea how to overcome this issue - my solution doesn’t work anymore ….

Hello @marcogertsch,

I have tried both KNIME versions 5.5 and 5.10, and Transfer Files (Table) node on which I rely a lot (same archiving reasons as you) is the same regarding Destination options if not mistaken. I use option From table as I prepare my archive file names and paths before in Column Expressions (legacy) node.

Which version are you taking about?

Br,
Ivan

2 Likes

@marcogertsch from my perspective the approach still does work to rename the files thru transfer files node:

3 Likes

Hi Ivon

Many thanks for your answer and sorry for the slow answer, but I’m currently very busy in my projects.

I fully agree with your approach, this works as you do not need to rename the file on the target. You do this already with another node on the source side. The issue is, that till recent, this was not needed and the Transfer File node moved and renamed the file without issues. This doesn’t work with the latest version anymore. Before I switch to your (alternative) approach I wanted to ask if this is a bug and will be fixed or if this is “works as designed” and this functionality doesn’t come back.

KR Marco

Hello @marcogertsch,

not sure I fully understand but if I do I would say this is “works as designed”. If you want you can share a workflow example using dummy data and relative path. This way it will be easier for everyone involved.

Br,
Ivan

Hi Ivan

I resolved the issue and found the bug in my workflow (I used a file separator variable that didn’t fitted the target file system :-(). Many thanks for your great support, I was really stuck before and when trying to build the example workflow, I found out it still works and my workflow must be the issue.

Have a great friday and once more thank you for your help!

Marco

4 Likes

Hello Marco,

glad to hear that!

Br,
Ivan

1 Like