This is barking in my change node using JSONata: [ $map( payload, function($v) [ { "fieldKey": "fieldUUID", "value": $v.fieldUUID }, { "fieldKey": "fieldName", "value": $v.fieldN…

I ended up with a ternary operation to make it consistent: $count(payload) = 1 ? [ $map( payload, function($v) { [[ { "fieldKey": "seasonFieldUUID", "value": $v.seasonFieldUUID }, …

Hard to say with out the data you are mapping, but looks like you are missing the scope { } around the array. [ $map( payload, function($v) { [ { "fieldKey": "fieldUUID", "value": $v.fieldUUID }, { …

As long it is not expecting an object. The other test in the main ticket had a similar set of brackets {}.

Worked thanks again for the extra set of eyes. [ $map( payload, function($v) { [ { "fieldKey": "fieldUUID", "value": $v.fieldUUID }, { "fieldKey": "fieldName", "value": $v.fieldNa…

When there is more than one record in my CSV I get the correct JSON [ [ { "fieldKey": "seasonFieldUUID", "value": "1b3bac39-48fd-45e6-a394-9c9cbb455d6c" }, { "fieldKey": "fieldName", "value": "Paddy 1" } ], …

Related comment, which I don't understand why it would behave this way. [image] $filter array is return undefined in logs - flow.fileContents or payload.arrayEntry not accessible? General To note, if theere is only one match the output will be an object not an array with a…

What is the reason for using map ? By default JSONata acts like a map already, ie. *.[ { "fieldKey":"seasonFieldUUID", "value":$.seasonFieldUUID }, { "fieldKey": "fieldName", "value": $.fieldName } ] Not sure why it flattens the array when there is …

Ending that with is good to know.

Using the map functions should be faster than the . operator. @dubnemo I see no reason to use the ternary operator. You can add [ ]at end or surround the whole expression with [expression] it is has the same result.

[image] E1cid: surround the whole expression This doesn't seem to work. Using the map functions should be faster than the . operator. If speed is a concern, I would recommend to use javascript instead.

What doesn't seem to work, please supply example. The updated JSONata 2 has speed performance increases the functions I have tested are compareible to Javascript.

Node-RED

Node-RED Forum

Trying to use JSONata $map for Nested arrays, getting Invalid JSONata expression: Expected "{", got "["

General

dubnemo 23 May 2025 02:28 6

Related comment, which I don't understand why it would behave this way.

Topic		Replies	Views
JSONata exception -- JSONata expression help please General jsonata , change-node	17	359	3 December 2025
Setting payload to JSONata expression isnt working! General	2	1216	23 March 2019
Inject: inconsistent JSONata error message Core Development jsonata	10	166	15 November 2025
Unexpected behaviour when using jsonata expressions like payload[..][] in change node General	10	595	16 November 2020
Weird JSONata problem General	22	6488	21 August 2018

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Trying to use JSONata $map for Nested arrays, getting Invalid JSONata expression: Expected "{", got "["

Related topics