Anyone solved the issue about using multiple formula fields in a search-based Map/Reduce

use different names for your formulas

No need to use hardcoded reference to the formulatext columns, you can do something like this:

var aColumns = [];
var oColumnsDefinition = {};
for (var sKey in COLUMNS_MAP) {
   oColumnsDefinition[sKey] = search.createColumn(COLUMNS_MAP[sKey]);
   aColumns.push(oColumnsDefinition[sKey]);
}

that strategy will not work in the map or reduce state after the search results are stringified

They will if you properly handle your searches in the getInput stage... returning raw result object and accessing hardcoded properties is far from being a good practice...

you will have to make a very good argument when NetSuite's best practices says otherwise

I'm aware of that document and also aware of another 30+ crappy/bad SuiteAnswers, NetSuite is not exactly consistent per say, if netsuite changes the underlaying result object structure at any given moment which they can do and updates the "methods"

result.getValue

and

result.getText

any script passing or using the raw result object will break and any script using the official API methods will prevail. I don't know what makes people happy, but I know what makes me happy, knowing that 5+ years old MR never returned to me after ~10 NetSuite releases.

the json that you see from the result object is not the underlying structure, its the output of a .toJSON method. If NetSuite changed the underlying data structure, they can change the code of the .toJSON method to still output the old representation

Or they may not since

.toJSON

is not officially documented anywhere as far as I know? Right?

my argument is more that the hypothetical problem has a hypothetical solution

Its a bit slower but you could run the search in the get input and cast the columns in the map phase. Alternatively you return from get Input just the internal id and in the map phase run the search again. Nothing is ideal, just work arounds

Thanks everyone for the feedback