Currently, when performing string manipulations on HTML columns in KNIME, the resultant columns are coerced into the standard string data type. This breaks compatibility with subsequent operations or nodes that expect HTML types. It would be extremely helpful if the String Manipulation nodes offered a dedicated conversion or cast function—such as “toHTML()” — to retain or restore the HTML data type after manipulation. This enhancement would allow seamless workflows involving HTML columns or types without cumbersome workarounds.
Hi @mwakileh ,
thank you for the feedback. While we do not plan to add this to the String Manipulation node, we are considering how to best add HTML support to the Expression node (internal reference AP-24070).
Can you describe typical tasks you perform on HTML data with the String Manipulation node?
Have a nice day,
nan
1 Like
Hello,
Let’s imagine that, according to a filter made previously on the workflow, we would like to change the text color in a HTML column and put the text in bold. A way to do it would be to replace the code in the HTML column witht eh String Manipulaiton node, unfortunately is is automatically converted to String and it is not read as HTML by the Table View node (however it is understood by the legacy Javascipt table view node).
Expression node does NOT handle HTML columns.
Another way to do it would be a “string to Html” node…
Thank you !
1 Like