I’ve just used the Splitout node and wanted to keep a value “person.label” and used the dot notation option to enable that field from carring over.
Here is my simplified workflow:
input json:
{
"persons": [
{
"first_name": "Max",
"last_name": "Mustermann",
"phone": "004404404444"
},
{
"name": "Maria",
"last_name": "Mustermann",
"phone": "004404404444"
}
],
"person": {
"label": "Grün"
}
}
Expected output:
[
{
"person": {
"first_name": "Max",
"last_name": "Mustermann",
"phone": "004404404444",
"label": "Grün"
}
},
{
"person": {
"name": "Maria",
"last_name": "Mustermann",
"phone": "004404404444",
"label": "Grün"
}
}
]
actual output:
[
{
"person": {
"first_name": "Max",
"last_name": "Mustermann",
"phone": "004404404444"
},
"person.label": "Grün"
},
{
"person": {
"name": "Maria",
"last_name": "Mustermann",
"phone": "004404404444"
},
"person.label": "Grün"
}
]
If I understand that correctly, the dot notation gets used on the input side of the node ,but not on the output.
Is that expected?
A solution without a breaking change would be to add a option to the splitout node which enables dot notation for the output seperatelly to the input.
Also found another post without an answer about this “issue”:
Information on your n8n setup
- n8n version: 1.65.2
- Database (default: SQLite): postgres
- n8n EXECUTIONS_PROCESS setting (default: own, main): own
- Running n8n via (Docker, npm, n8n cloud, desktop app): Docker, queue
- Operating system: Server: ubuntu 22.04, Client: Win11 Firefox