Improve Column naming when removing one with identical name

Feedback & Ideas
1

Hi,

when extracting data i.e. from XML, JSON you often have a column which you want to remove / replace by it’s extracted contents. In the followign example I got JSON containg tags:

[
    "transformers",
    "gguf",
    "mergekit",
    "merge",
    "en",
    "base_model:mergekit-community/MN-Hekate-Enodia-12B",
    "base_model:quantized:mergekit-community/MN-Hekate-Enodia-12B",
    "endpoints_compatible",
    "region:us",
    "imatrix",
    "conversational"
]

I want to extract the tags as a list but with the same column name. Due to the chicken egg problem the new column is suffixed tags (#1).

I’d like to propose, to not suffix a column if the is no naming conflict by removing of the source column or add an option to replace the source which would also insert the extrated data at the same column index position.

Best
Mike

2

its an issue in many nodes:

if you have a checkbox to remove the column(s) which is/are processed after processing and a new column with the results to be added, it will create the result column first (given it the #1 ending if you chose a name already present).

the nodes do not include an additional rename / name availability check after finishing their operation.

this issue is not limited to JSON nodes

3

Yes, that is what I wanted to point out and suggest to improve.