Just got a call from one of my clients and troubleshot the error to the nlapiLoadRecord If have the correct customer ID (checked) and have the correct record type. Interesting about this is that it is occuring against one record but not another. In other words, I have a Customer list field set up on a quote form. When I…

It will great to hear what's planned. I will put in for enhancements and post back here. Thanks Yang.

In reference to my previous statements for exposing preferences and lists, here is a bunch of enhancements around that. Please vote and vote often... Enhancement 156948 - Setup > Customization > Entity Fields > New >Type = List/Record > List/Record: Add "Country" as one of NetSuite's standard lists in the List/Record field…

I have the need for use case 1.a / 1.b now from a form suitelet I've built. Is there a workaround for this or must I manually create the two select lists and write my own "onChange" js association code (to display the correct states for the currently selected country)? Thanks, Chris The latter for now. Re: vote for…

Did you ever enter an enhancement request for this? Isn't the problem with contacts that login on behalf of customers or partners or vendors? Thanks, Yang Thought there was an enhancement but it's been going on 2 years now so can't remember for sure. Do know however that this was discussed (at least on this forum). Not…

This has become an issue for us too. We want to have the "Contact" field on a case submitted from the Customer Center default to the contact logged into the Customer Center... however we can't pull the Contact internal ID to populate that info. Can you suggest another way around this? AFAIK, this has not been fixed. There…

have you clicked the "select all roles" box? David, You are my hero. 6 hours laters - wow. I had not selected 'All Roles' but DID select the role of the logged in customer center role which obviously was not working. So, as I see it (for FYI to all): - 'Execute As Admin' :: $0 - 'Available Without Login' :: $0 - Selection…

I believe you are limited to non-stored custom fields for this operation. Thanks, -e Bummer. Would be nice to be able to do pre-display setup of a form's field statuses. Wonder if it would be a stretch to expand the UI objects to include a 'setValue' method? Then we could get the form object on beforeLoad and reset the…

Yes - in the 2009.1 release we added a new API to nlobjContext that should return the internal ID for the contact that is logged in on behalf of a customer, vendor, or partner: nlobjContext.getContact() Thanks, Yang Excellent! Is this a contact object (first, last, telephone, etc)? Or is it just the contact record ID? Step…

Seems to be a weird quirky thing.... I live by the rule of switch it all on and then see what you can take off. It's definatly annoying that in certain senarios you need to "select all roles" when really you shouldnt need to. If you play about with enternal suitelets by any chances make sure you have the following set: -…

FYI. Seems this error generates when you try and add select options to a select field that you have assigned a list ID to. What I had done was create a custom list that was empty, and assigned it, then tried to add more options. When I realized I did not have to assign a list for a select field (documentation was not so…

1) The fields you add would be available when the page is submitted. Excellent. That makes sense and is perfect for what I need. 2) There is a client side API however for adding/removing options from select fields: nlapiInsertSelectOption(fldname,value, text, selected) Great. Did not see that. I also see a remove select…

I have a problem similar. I have a simple UI field that is inlineHTML to show a message I want displayed across the entire tab at the top and then have two columns of fields below it. I can display the columned fields correctly and assign the column break via setLayoutType OK. When I setLayoutType on this UI inlineHTML…

Solved. Sort of. If you pass ONLY the type parameter (e.g. setLayoutType('outsideabove'); ), it works as expected. If you pass in the break parameter (e.g. setLayoutType('outsideabove','none'); ), it does not work correctly (only spans one column). This is true even if you set the break parameter to 'startrow', which will…

One more nice to have... On client side, when we add custom fields (or add them through the UI functionality), the workflow can sometimes dictate required versus not required (e.g. enter certain countries then state is required, otherwise not). Would be nice to be able to change the mandatory field designation along with…

I will notify our documentation team of this error. Thanks for pointing this out. These XML APIs (as well as any API listed in the library section) are available in both Client and Server SuiteScript. Thanks, Yang Re: Docs - Thanks Yang. Re: Available on client - good to know as the docs state: "Library functions are…

Thanks Yang. FYI, the docs for nlapiXMLToString state that the input parameter is a string. Based on your answer, this should be W3C XML Document Object Model... Also, why are these XML API's only available server-side/suitelet and not client? If I process an XML string into a field for storage, I want to grab it and read…

As soon as I used nlapiGetFieldValue instead of nlapiGetRecordId, nlapiLoadRecord, and getFieldValue, the script worked in IE and Chrome as it did in FF. What do you think? Throw an alert message in after the nlapiGetRecordId and after nlapiGetFieldValue and see what the values are. If not the same then obvious (e.g. -1).…

For Internet Explorer users, there is a dependency on the MSXML add-on for several of the API calls including nlapiLoadRecord, nlapiCreateRecord, nlapiCopyRecord, nlapiStringToXML, and nlapiXMLToString. Furthermore, this dependency has existed since the addition of these APIs to Client SuiteScript. However it is our goal…

I also am getting this error. I put a try/catch on the nlapiLoadRecord and an error was thrown (error message however was undefined). The script this is used in has been working flawlessly for nearly a year and began giving the behavior last Thursday. One thing of peculiar interest: I do not get the error on my machine…

Thanks Yang for keeping us informed. -Steve

Found a (workaround) but I would not call it a solution to the problem. -Steve

My error is client side on a valid existing record. A search was performed right before and then during the loop of the found record, it is trying to load a specific one. nlapiLoadRecord is the problem

Based on my conversations with support, it seems NS is using some newer DOM related calls in the API (perhaps in other APIs as well that have yet to manifest themselves on any great scale to notice). I am however surprised at the slowness to resolve. Asking everyone to download and install the latest and greatest DOM…

We found that installing the Threaded XML DOM Document 4.0 add-on for IE7 stopped the problem. Still doesn't explain why this manifested itself in the past week or two and why all of sudden we would need to have users installing add-ons. That seems extreme. -Steve

I narrowed it way down and have found out the following: Multiple Record Level Client deployed scripts will work fine. For example, two scripts that alert() in their respective onInit methods will each be called. calling nlobjForm.setScript() in a BeforeLoad UE script does NOT work. Yang? Expected? Defect? By Design? :(…

Hey Steve, Unfortuntately this sublist is not yet supported. The Items sublist that is supported is the inline editor item sublist on sales transactions (orders, cash sales, estimates, etc..). There is a plan in place to add support for more of these sublists (the current list is available in the SuiteScript reference…

Yeah, Fulfillment is a fun screen to script. I don't think you should give up, cause you can probably eventually do whatever you need to. Do schedule +200% dev time though. Like you said, lots of trial and error. Agree. But I hate going around APIs to solve the problem. Just erks me how much trial and error is STILL…

Is a field change event not firing when you update a field on that sublist? It should also pass you a type (sublist) name, a field name, and a line number. Calling nlapiGetCurrentLineItemValue(type,name,linenum) should return you the current value of a field (cell) in the sublist. Thanks, Yang The field is firing and I can…

I'm also noticing that I can not change the value of the 'quantity' cell for the line item because: a) For the call to nlapiSetLineItemValue('item',...) the following code in the function stops me: if (type != 'item' || fldnam.toLowerCase() == 'description' || fldnam.toLowerCase() == 'revrecstartdate' ||…