Yes Olivier, I converted the script to NOT use dynamic mode ... and I'm good. Thanks! However, doing the same on an ItemFulfillment is 100% broken ... had to resort to building an SS1.0 script for ItemFulfillments with Inventory Details. Not fun.

SS2.0 still doesn't handle Inventory Details (Serial/Lot Numbers). I have lots of pure SS2.0 solutions that I need to sprinkle in SS1.0 Suitelets for handling Inv Detail interaction. Its a crying shame.

I do this, no issues. I did notice, your first example ends with _quantity were as your second example ends in _qty Perhaps that's the real problem

I also read that, in SS1.0, if you omitted the deploymentId from nlapiScheduleScript (or passed a null), that Netsuite would use the next 'available' deployment. That would be ideal! Anyone know if the same holds true in SS2.0? I'll give'r a go and let you know. I appreciate all the help! Keep it coming!

Great news everyone, passing a 'null' for the deploymentid forces Netsuite to choose the next available deployment. Wicked!

Simply, I have a RESTlet that is capturing large amounts of data, and I want to hand off the processing to an available script deployment.

Below is the code (typescript) I'm currently using (not working quite right). export let queueMRTask = (config: QueueMRTaskConfig): void => { let i = 1; while (i <= config.PROCESS_QUEUE_COUNT) { try { let msgProcessor: task.MapReduceScriptTask = < task.MapReduceScriptTask > task.create({ taskType:…

Ok, thanks Maher! Step in the right direction for sure. Now, I've been staring at this for a while. I've got 10 deployments for a Map/Reduce. I want to run a Scheduled Script Instance Search, and get the list of the deployments that are 'idle' So, if deployments 1 and 2 are 'in use', I should get back 8 in the result set.…

Check this out ... https://usergroup.netsuite.com/users/forum/platform-areas/customization/suitescript-2-0-custom-code/422023-client-script-hack-that-could-save-your-life Happy Friday

Thanks for sharing Mark!

Well, on the bright-side, since its encapsulated in a Suitelet, you can keep this SS1.0 solution and call it from SS2.0. I'd go a step further an open a case citing both the working SS1.0 and the broken SS2.0.

Esh, Mark .. that's a tough spot you're in. Sounds like you've got everything in order. I few quick questions. Are you doing this in a Suitelet? or what? Do you have an equivalent SS1.0 script that works?

See my latest post ... Client Script hack that could save your life!

So frustrating. Anyway I could 'wrap' the nlapiDisableLineItemField('assignee', 'serviceitem', true); and call it from SS2.0? I'd hate to undo the SS2.0 migration for a single line of code.

Nice work mattdahse! I think I'll use that and swap in my hack for your jQuery. Cheers!

Cool find! Seems like this can be yanked at any time and is probably not wise to do. Any time I see "hack" and netsuite code, I immediately see a nightmare of maintenance. I'll be long dead before Netsuite yanks SS1.0. Believe me, I'm all for using API's ... but if they don't exist (or work), one must search in dark…

So, on a new record (pick one, any one) .... try a disable a sublist field. For example, on a NEW Project Task, try and disable the 'serviceitem' on the 'assignee' sublist. Through my endless hours of doing this, I observed that ... if the sublist is empty, SS2.0 API's associated to this task (disabling) all fail. There…

Oh the hours I've burnt trying to do this! Lemme know how you make out!

See my latest post ... Client Script hack that could save your life!

Ok, so here's a bit of a beef (rant) ... The script context gives me the currentRecord, so do I really need to import the currentRecord module? Example: context.currentRecord.getField({fieldId: 'entity'}).isDisabled = true; Works exactly the same as var record = currentRecord.get(); var field = record.getField({ fieldId:…

Ouch, I know the feeling. Yep, its a real short coming. Don't bother trying to 'solve' or 'workaround' it either ... its a major flaw.

Hey guys, Ya, this is a real show stopper for Map/Reduce solutions.

Ooof ... I should really start reading the release notes more closely. Thanks Eric.

So, I've kind of have the opposite problem. I'm trying to set to undepfunds to true with no luck. I've tried true, T and 1 all the same. Also, I'm setting this value LAST, to ensure it gets set and not overwritten somehow. And, I'm in dynamic mode. Anyone ever get this to work?

context.response.renderPdf({ xmlString: reportData.pdfXML });

Hello all, I battled with this as well. Seems like a bug. I resolved the issue by converting my field type to decimal. Not ideal, but ...

Thanks all ... this is great info. By the details above ... it looks like I could SET a custom Company Pref?!?!? Wow. That would be an HUGE upgrade from SS1.0. I'll keep you all posted

Last thing, try doing currentResult.getValue(currentResult.columns[0]) (In your original solution) Notice you're passing the column in directly, rather than a property of an object. 

starlingMark , care to share more code? Can we see how you setup the search in the first place? Reason being is, in some situations, the searchResult object won't be fully populated (ie. when being uses in the Map/Reduce script. When you log-out currentResult, what does it look like? 

Oh undocumented glory! The request obecjt IS there. Just NOT in the SS2.0 documentation. After JSON.stringifying the context, I see that the request is in the ... as http.ServerRequest (odd, I would have expected https)