Unable to use path variable to write into excel

[nikhil_benny]

Hello, I have a workflow where I have to generate report daily and the file name should be the date of execution. I have used date and time configuration node to get the execution date and string manipulation node to prepare the path. Here is my code for the string manipulation:
string(“C://Users//nikhilci//Documents//Reports//” + “TransactionData” + $${Sdate-input}$$ + “.xlsx”)

This statement works fine. When I use the string to path variable node, it gets converted into ‘FSLocationVariableType’ data type. For some reason, excel writer does not recognize this as a path due to which I’m not able to write it into the required excel sheet. Weirdly, this same ‘FSLocationVariableType’ works fine when I am using the excel reader node.

Please suggest how to fix this or a workaround.

Thanks in advance

[hmfa]

Hi @nikhil_benny .
Have you tried \\ instead of //?
Br

[rfeigel]

Take a look at this.

Excel Name with Date – kabrah

[mlauber71]

@nikhil_benny you can create file path in a node. You can combine the names of the files with current time stamps.

Write multiple CSV file to a loop

@VJAM the creation of Flow Variables for Paths is maybe not 100% straightforward. Maybe this example might help to sort it out. The “path_values” is maybe not perfectly named. I think this is constructed that you could pass several Folder variables as collection strings. Also: CHunk Loop Start might have to be set to 1. Often I prefer the Table Row to Variable Loop Start node. [image] [image]

[nikhil_benny]

I did, it did not work

[mlauber71]

@nikhil_benny maybe you can provide an example and a logfile about what is going on. BTW the syntax you posted above will not work since the quotation marks are not correct.

Error Installing Python Extensions

@Xtian you could try and do a fresh installation. Then you could provide us with a clean log in debug mode: Set logging level to debug in the preferences [image] find the location of the log file [image] Delete or rename the existing log (you might have to close KNIME first and store the path to find the log) [image] Restart KNIME and do the operation that causes the problem find the Log again and zip it and send it to support or post it in the forum Reset your log level to W…

[nikhil_benny]

Hello, I was using 5.2.5 version. I updated it to 5.2.6 and it works now. I’m not sure exactly what the reason is. I was trying to configure the file with date to an existing workflow. Maybe you have to replace the existing excel reader node with a new one and configure it. Maybe this is a bug?

[takbb]

Thanks for the update @nikhil_benny .

I think there may be an obscure bug here somewhere. I experimented to try to replicate what you were doing and created a string variable which I then converted to a path. When I first did this, the Excel reader node could not see the path variable even though the nodes were fully executed up to that point, so it should have been visible.

I then created a second variable and executed again, and this time excel reader could now see both of them. I tried to repeat this but I couldn’t reproduce it. If I find time, I may have a further investigation while videoing the screen to see if I can reproduce and document.

Certainly there is something going on here that doesn’t feel quite right, but clearly whatever it is does not always show itself, and possibly resolves itself through other interactions so had gone largely unnoticed. I think I was using KNIME 5.3.3.

Glad you have it working now though.