In a 2022.1 sandbox instance, we’ve discovered that a search result being passed into the Map context of a map/reduce scripts seems to be handing multi-select fields differently. Logging

context.value

in the map reduce script before 2022.1 returns multi-select values as an array. After 2022.1, this same value is being returned as a comma-separated string. Our

getInputData()

function returns the transaction search itself with no modification. The column in question is defined as

{ name: 'custitem_multiselect_for_custom_record', join: 'item' }

. Before 2022.1, context.value contained: 

"custitemr7defaultsrptemplates.item": [
  "102681405",
  "176424579"
]

After 2022.1, context.value contains:

"custitem_multiselect_for_custom_record.item": "102681405,176424579"

Has anyone else seen this? We’ve already opened a support case with NS.