This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

Any see this before in a M/R? View	System	UNEXPECTED_ERROR	2/7/2020	11:35 am	Darren Hill	TypeError: Cannot call method "split" of undefined (Governance.scala#52).  `I don't use split anywhere in this M/R nor anything imported`

Governance.scala suggests that the error is one of netsuite's internal code errors

Would specifying 2.0 avoid the script using scala?

i asked because your error looks extra weird

Great, now we have JavaScript, Rhino(Transpiling to Java) and Scala, then on top of this add TypeScript... what can possible go wrong.

More info.  If I return a `search.Search` object in the getInputData stage that has zero results, I rightfully (and immediately) go to the summary stage.  But that's where the error happens ... and I never get a chance to execute the first line of the summary stage either

<@U5FHY30BV> ~does it happen in getInputData or in one of the stages? It could be from a user event on one of the records you interact with~
Nvm you said it happens with zero results

in the getInputData .. I'm merely returning a search.Search object

Are you using any iterator in the summary stage

I just got the same error in a scheduled script
```Error: UNEXPECTED_ERROR
TypeError: Cannot call method "split" of undefined (Governance.scala#52)```

I guess it's a bug in NetSuite's script queue architecture?

probably should file a case - since you're not alone!

Still getting this today -- I just submitted a case.

Only affecting one script (so far)

Execution does not even reach the first line (a log statement I added) of the schedule script btw

I'm still tickled to see them using Scala

Update on this <@U5FHY30BV> <@UL2H7R5PE> <@UKNAAR40K>
After debugging with NS support, for me the error came from importing `lodash` with`@NAmdConfig` directive in a custom module.
Double check that the `@NAmdConfig` directive is at the top of the entry point script and not just in the custom module or try importing using a absolute file cabinet path.

No idea if your situations are the same, but in my case the error message is completely spurious.

<@U8CT0V220> the fact that @NAmdConfig works only in top level modules is a showstopper for me. I just use relative paths, not @NAmdConfig and life is simpler.