@Daniel_Weikert could you give us more details for example what the error message says? Better even could you provide a workflow that would demonstrate the error?
Two possibilities would be date and time variables where there seem to be problems.
@toscanomatheus this might be an interesting case. I will have to have a closer look at your specific file.
I startet to look into the question pof the Python Labs nodes and Date and Time variables (again) and indeed there seems to be a problem with the handling of types. In a previous discussion I toyed around with several formats and then exported the data thru Parquet files and brought the data back to KNIME which worked (mostly):
This time I tried two things with string formats exported …
Or might there be an issue with RowID and index in pandas?
Hi @mohini1329 ,
as the others have already suggested, you should make sure that each row in the Pandas DataFrame has a unique index.
Dropping/resetting the index is not the best option though, because KNIME uses the RowID (which is equal to the DataFrame index) to identify rows when you select / highlight individual cells in your data. If you reset the index, then this row identification will no longer work.
The best solution would be to let the index of all values in your input table as they…