My Stuff
On Friday, October 10, 2025, at 8:00 PM Pacific Time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
Share Your SuiteWorld Experience & Earn a Special Badge!
Comments
-
There is no consequence for NetSuite, I think that's why I get so mad when this happens. Sorry, thinking out loud.
-
I feel your pain brother! https://usergroup.netsuite.com/users/showthread.php?t=11461
-
dead in the water.
-
word from my users is that it's fixed. Thanks for the info and the quick action. Time for me to crash now.
-
Hi Ken, [LIST=1] [*]What was the problem? What was affected? I'd like to know in case I see any other problems I will know what to associate them with. [*]What do we need to do? Do my users need to grab a fresh session?[/LIST] Thanks for the update. -Steve
-
FYI, this is still very much broken. I've heard it was fixed but it's not.
-
Thanks for the confirmation. No scripts running, just checked my Scripted Records list to make extra sure. 2009.2
-
I have tested this in the debugger and it's BUSTED. I went through the 'apply' sublist and don't see anything set incorrectly. Here is the code I'm testing with: var CUST_PYMT_FLD = { APLD : 'applied', AUTO_APPLY : 'autoapply', ACCOUNT : 'account', CHKNUM : 'checknum', CUST : 'customer', EOB : 'custbody_custpayment_eob',…
-
I just tried every conceivable way to reproduce the error and I can't. So it was either a fluke or they've fixed it already. Thanks for the reply, I'm glad it's working now.
-
The workaround is to explicitly set the amount and applied fields on the lines you want to apply. // Explicitly apply var count = payment.getLineItemCount('apply'); if(count) { payment.setLineItemValue('apply', 'amount', 1, 1.55); payment.setLineItemValue('apply', 'apply', 1, 'T'); payment.setLineItemValue('apply',…
-
Case# 934453 Created: 9/18/09 update broke nlapiTransforRecord -> Customer Payment
-
Hi Mark, All of my code is server side so that doesn't jive with what you have noticed.
-
I am, yes. Some of my searches are now timing out that used to take just seconds. I will contact support and start that process. Thanks Michele.
-
If we can't delete the files then it shouldn't count towards our allocated space. As long as they don't charge me $$$$ for additional storage then I don't mind not being able to delete the files.
-
I've never used this method and in fact it seems strange that you could get an nlobjField instance from an nlobjRecord - sorta mixing layers, isn't it? Anyway, I saw something in the help that just *might* be a clue: This method does not return ALL fields on a record. This method returns only the fields that have been…
-
don't try 'internalid' - apparently it's 'id' (consistency, right????) :o Anyway, the following code works fine for me: var record = nlapiLoadRecord('customer', 1175); if(record.getField) { var fld = record.getField('custentity_customer_coinswaiveronfile'); if(fld) { nlapiLogExecution('DEBUG', fld.getLabel()); } }
-
[LIST=1] [*]I think of nlobjRecord as a simple data object or maybe now with the additional calculation logic it could be a domain object. On the other hand I think of nlobjForm as a presentation object that does not contain any of the model data. You can create tabs, move fields, disable fields, etc; all UI stuff. Either…
-
Man, 7 hours later and they are still queued? Is that correct?
-
Hi Ken, It still shows as 0 sent. I never saw anything that said they were queued and in fact I received email confirmation from NetSuite at 6:03 (1 minute after NetSuite says they were sent in the UI) that "29 copies of the message were sent" which is why I'm so confused the UI is telling me none were sent. I'm glad the…
-
Do I need to do anything to get this rolling or are you already taking a look into this?
-
It's executed at 6:02pm today. So it s normal for it to report that it sent zero when actually it did?
-
yes, if you look at the campaign detail report it should say "Queued". When it says "Sent" that means we actually got a success message back from the recipient mail server. Do you see better results now? From the logs I see all but two of your messages were successfully delivered. Thanks Ken NOW I see what you mean, I was…
-
Anyone else experiencing this? Yes, mine are all messed up too!
-
No, I'M back! It was my error actually :o ALTHOUGH!..... the error is totally misleading and random. If anyone from NetSuite cares to file an issue for this? Request SOAP: <soap:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"…
-
This is back!! I'm getting this error again out of the blue! Anyone else?
-
Jim, Have you checked to see if there is a difference if you use the RichTextEditor or not? Not that it should do what you have described in either case...
-
Thanks. FWIW it seems to have settled down and behaving right now. I was just wondering if anyone else experienced the same thing.
-
Client sorting would be quick as you suggested but the sort is essentially a new query against the DB. Oracle (or app server) is most likely caching the request so that is why you are seeing 1 minute versus 3+ The search is probably taking so long because the message field is not indexed. If it was indexed it would consume…
-
It's working on my end now as well.
-
If you don't get a solution to this in time you can try this: [LIST=1] [*]Create saved Task search with the following results:[LIST] [*]Assigned To [*]Company : Sales Rep[/LIST] [*]Sort by Company : Sales Rep [*]Enable Editing [*]Batch update the Assigned To field[/LIST]It's a compromise between mass update and one-by-one…