I thought the same thing ... but its in there (not sure why its not in my example)

Hmmm ... ok. I don't think you want currentResult.columns[0] I think you want salesResults.columns[0]

Noticed at a coupel of places, some equal to symbols in your sample tags within the Datacurve tag, Please check if they are causing syntactical issues. <sample x=3D"2016-10-1" y=3D"203140"/><= sample x=3D"2016-10-2" y=3D"230008"/> Ya, something went wrong when I copied that code into this editor. I corrected the xml…

Hello all, I was able to fix this issue myself. I ended up downloading and installing the BFO Generator locally and ran my xml through it. So I got much more detailed error output than the generic Netsuite one. Ended up my TrueType font file was corrupt! Everything is right in the world again. Cheers to those that helped…

Noted! Thanks David for the feedback. And ... what?!?!? ... where did you hear/read that Netsuite will have SQL abilities. I may stop pulling our my hair on this if that is the case. As for the runPaged(), ya .. never. jSuite's runSearch makes recursive calls in order to grab all data (bust through the 4000 record limit).…

I'm going to spend an hour building out simply use cases using ss2 and ss1 and will post the results here. Chanarbon. I'll include trying to 'edit' an existing deposit as well as using record.submitFields().

I don't normally plug pre-built solutions, but you guys should really check out https://www.tacticalconnect.com/

I'm in agreement with you Eric, thanks for chiming in.

I'm assuming you mean the "customerdeposit"? What seems to be the issue? Actually no, I mean 'deposit'. I've built an integration that is receiving bank deposit information, and I'm building a Netsuite deposit based on its information. It'll be pretty sweet. But man .. this bug! Please say I don't have to revert back to…

My guess is the Netsuite plans to deliver support for legacy SS2.0 versions. Meaning, if you 'tag' your script with 2.0, Netsuite will execute that code against its 2.0 engine, even if it has already launched 2.3, 2.4, 3.0, etc. In the past (SS1), it was difficult to update (or fix) functions/features as it would require…

Maybe its an SS2 thing .. I did the exact same thing in SS1 and it worked. I get this error in SS2 "type":"error.SuiteScriptError","name":"UNEXPECTED_ERROR","message":"ReferenceError: "document" is not defined.…

So, here we go. Very simple test case. SS1.0 code works fine ... var deposit = nlapiCreateRecord('deposit'); deposit.setLineItemValue('payment', 'deposit', 1, 'T'); nlapiSubmitRecord(deposit); SS2.0 throws an error var deposit = record.create({type: 'deposit'}); deposit.setSublistValue({sublistId: 'payment', fieldId:…

So, Netsuite has acknowledged this is a bug .. server-side. The work around is either Client scripts or SS1.0. See Defect # 418131. Arg. SS1.0 it is!

All I did was set the class/department and set 'deposit' to true on the first line of the 'payment' sublist. Should work fine as a PoC. Is this a Netsuite bug in SS2? 

Out of curiosity, why the timeout? Is there a reason you don't use document.ready?

I was able to get a sublist field to disable within a client script. The following is in the lineInit. var currentRecord = scriptContext.currentRecord; var currIndex = currentRecord.getCurrentSublistIndex({ sublistId: 'item' }); var objSubrecord = currentRecord.getSublistField({ sublistId:'item', fieldId:'amount',…

Ya, it sucks. I've added a inline html field on the beforeload and injected the javascript as a value. Of course, this way, you're limited to the size of you script then (unless you have the script simply LOAD in a Netsuite file that contains your actual client script). So, obviously, a variation on that is to add an…

So, Against my better judgement, I hacked this. Instead of trying to use Netsuite's API to disable/enable the sublist 'item' field, I did this ... jQuery('#item_item_display').prop('disabled', true); Don't tell on me!

We think alike! But ya, it yells at me! So, hack it is!

Eesh ... just looked through the SuiteScripts 1.0 to SuiteScripts 2.0 API Map, and there's nothing listed beside nlapiDisableLineItemField(type, fldnam, val). Crap

Ok, reference Defect #413823 and Case # 2524386

I had the same issue with a client about a week ago. They reported they could no longer authenticate, but I could. They opened a case with netsuite and it was resolved in short order. I'll ask them for more details to see if I can get you some help.

Further to this, I attempted to simply use the getSublistField function, but apparently that function doesn't exist on the CurrentRecord either! I get an SSS_INVALID_SUBLIST_OPERATION. Is there no nlapiDisableLineItemField equivalent in SS 2.0 yet?

Is there a way I can view/monitor that defect? In SuiteAnswers or SuiteIdeas?

Why are you saving inside the catch? It'll never be reached (unless the file/create throw an exception. Try it like this /** *@NApiVersion 2.x *@NScriptType Restlet */ define(['N/file'], function (file) { var fileRequest = { name: 'test' + '.txt', fileType: file.Type.PLAINTEXT, contents: 'test', description: 'f', folder:…

Happy to see that Defect # 412503 is resolved. I hope some day that Netsuite is more transparent with their 'silent' updates every Thursday night. Cheers!

Chanarbon/Infinet Cloud, That's so much for the feedback.

Fair enough David, I'm always pleading with my clients to use modern browsers, but I cannot control that. In some cases, the browsers are locked down my their IT department (that are pre-historic) and have no control over them. Point is, I know if I strip that line, I'm good.

Jonathan, The bigger issue is, your code has no valid entry point

Ok, so I figured it out (but don't FULLY understand). Here's the changes that made it work for me I added this line to my script <span style="color:'#808080'"><span style="font-family:'Menlo'"><em>///&lt;amd-dependency path="./lodash" name="lodash" /&gt;</em></span></span> This produced the define line as follows <span…