We're getting so many emails that the time on the 'sent' is two hours behind the time 'received'. Even though the email unhandled errors is turned off, still getting bombarded with emails.

Yep, Getting the same thing on our transactions. Perfect. Christmas season, heavy orders, "unexpected errors". Throwing them in multiples but yet orders are still coming through so cannot tell if users are seeing these or what. Started for us at 10:02 pm Eastern U.S. time. Getting slammed with these errors in my inbox.…

Boston, not down but might as well be. Taking several minutes to load a page. Production at a stand still trying to get product out the door to UPS.

Oh wait, it miraculously fixed! Now it is firing.

Yeah, I'm afraid you are missing the point. Not looking for "how" -- I know what I "could" do. With hundreds of thousands of transaction records it would not be a worthwhile exercise whether by script or mass update. The point of the topic was to suggest that wiping out a field when changing within the same type (e.g.…

Right, it gives you a warning but that's the point. It should warn you "Some data may be truncated or lost" rather than just wipe out. Too much historical data (in transactions) to export and re-import. Still think this is wrong and should truncate. At least with truncation, you pretty much know if you are going to lose…

Solved -- very bizarre (https://usergroup.netsuite.com/users/showthread.php?p=167646#post167646)

Yeah, this is something else. It has to do when editing the custom form definition and attempting to save the form definition. I've seen it before (a long while back). And... like before, it just disappeared after a while and everything is working as expected... I think it may have something to do with a corrupt login…

Yeah, this has nothing to do with saved searches or with browser cache. I am editing a custom form and cannot save it because I get a "custom field already exists" error (which is completely irrelevant to what I am doing). It is something with NetSuite and I believe a corrupt session. Once logged out completely (no…

The problem with these sorts of issues is you need to build in work-arounds (like setting the default to 'disabled' and then adding script to 'hide' for every load rather than a simple check to see if the user is valid and if not the script is done). Then the issue gets quietly fixed at some point and you have this…

I just re-tested and still get the same result. Here are more details: * Note: access to script and for the custom fields is always admin/edit (no restrictions) Custom Record (Custom Catalog): - {name} = 'My Test Catalog' Item Record: - Name = Custom Catalog - ID = custitem_custcat_catalogitem - Type = List/Record -…

After our account was upgraded we were experiencing errors sourcing values for hidden custom fields on transactions. It was identified by support that the error was with the custom form, and i had to create new custom forms for these transactions to remedy the issue. Interesting... However, I am using a user event script…

Yes, I've noticed this as well. I do have a field group assigned. I did not move any fields from sub-tabs (though someone else could have). Also saved the form, logged out and closed the browser and still the same when I tried again. Funny thing is that when you try and drag it up it snaps back to the very bottom, but…

OK, I think I have inadvertently discovered a bug in NetSuite form editor. Wondering if someone else could confirm as well. Add three custom item fields and set them to display 'outside above'. Then create another custom item field and set it to display normal (don't set 'insert before' to anything). Go to the entry form…

Hi Steve Is this still occurring or did you figure it out? Can you post more of the code you are using? I've run into a similar error when trying to use call nlapiYieldScript within a forEach call. Hi Brett, Yes it is still occurring. The code is quite complicated (over three library files, a number of native javascript…

Hello Steve, As an alternate solution for the time being, you may be able to prevent the error by setting the character encoding on the file before calling the getValue method. e.g. fld.setEncoding('UTF-8'); setEncoding(encodingType): Sets the character encoding of a file. The available encoding types are as follows:…

Hi Steve - please report this to support. Regression in functionality is always prioritized highly. Thanks, -e Hi Evan, We did. Case #1550168 Thanks.

Hi, The defect is #231555 The workaround for anyone who may run into this is to first save the file to the file cabinet and then load and read the value. This was not the behavior prior to last Friday (9/14) and adds some overhead since you now have to save, load, and delete afterwards. It also adds governance points…

VERY SLOW. Probably about to crash...

Hi Steve, there is indeed no "firstname" or "lastname" field on the entity record. (see the records browser) Hmmmm.... First, Entity wasn't there the other day (I know Kate said she was going to add it).... However, my comment was not to confirm whether there or not, it was to say "Really???". All so-called "entity"…

I may be suggesting something you've already tried/confirmed, but just in case... Have you tried doing this same search in the UI? Were the results different? My issue had to do with not being able to read the multi-select value(s) using the nlobjSearchResult methods available. Yours appears to be a filtering issue. Best.…

You may want to try using an array with "@NONE@". e.g. nlobjSearchFilter("fieldid",null,"noneof",["@NONE@"]);

Up 4:29 ET

Down here as well (East Coast U.S.)

Down an hour and counting. Good progress however to have concluded there is a technical error... :h_a_w:

Hardly up... 3+ minutes to load the home dashboard. Nothing else. System is hosed.

Another good suggestion, unfortunately this customer is looking to pull back from NetSuite costs (the storage costs alone are driving them crazy) so not a possibility at this point. Looks like I'll be carving this up into painful chunks. Leaves a bad taste in everyone's mouth however that this isn't easier.

Well that's discouraging. Perhaps NetSuite is content being a "very small business" ERP...

Yeah, good idea, but unfortunately I've only been successful in batches of 40,000 or less and it takes about 15 - 20 minutes for the process (run the search, export, wait for file download dialog, download at 340K/sec). *very* painful... Was hoping another solution might be out there, but doesn't appear so. This does raise…

You use it in the aftersubmit because you need to know that the record properly saved before applying the additional logic. Besides, really not my point on where, but rather "it doesn't work" and it should, at least according to documentation. Best. -Steve