In v. 4.5.2 Excel Writer generates an error if added tab is a source for pivot table and tab name specified is the same and set to be overwritten. At the same time, if the tab name is the same but specified by variable, no error generated. I believe if overwrite option for tab is specified, it’ not suppose to check if this tab is involved in Excel calculations.
To be clear,
Excel file was created by KNIME with source tab (say Data).
It was converted to Excel table object (Table1).
Pivot table was created based on Table1.
Next time tab Data needs to be overwritten by KNIME
New table object Table1 created
On pivot-table source, broken source fixed as Table1
New release failed on step 4 if its name directly specified and generate error Illegal table name: ‘Table1’.
I can avoid error specifying tab name as Data1, in Excel delete existing tab Data, rename tab Data1 to Data so on. If the same will happen in case the tab name is dynamic (happily, so far it is not) it will be a problem.
My point that both cases have to work the same way as it was before.
thanks for reporting your issue! Iam not quite sure if I totally understood how to reproduce. You are saying you are having an excel file with some data and the Sheet (this what I think you are referring to with “Tab”) is called “Data”.
Afterwards you are going to “Insert” tab in excel and create a table from that data by clicking “Table”. Table name is now “Tabelle1” (german version of Excel) and after that you create a Pivot Table based on “Tabelle1” like so
And after that you are trying to use the excel writer in “Append” mode, Sheet name “Data” and Sheet Overwrite option (append or overwrite) and this causes your issue?
I currently cannot reproduce the issue but there is chance that I made a mistake along the way. Please let me know if this is correct. The optimal case would be to prepare a small workflow which contains a sample excel file in the data area of the workflow and the excel writer which tries to write and fails.
hi @izaychik63 and @laaaarsi . i just checked the same workflows on version 4.5.1 and then again on 4.5.2 . The workflow does not give an error on 4.5.1. but fails on 4.5.2
i see that @izaychik63 has already loaded a simulation. Would be interesting to know what we find