I just saw a 68 second save time on a customer record. Using the Script Performance Monitor I am showing slow, slow save times across every record type I check: Contact, Estimate, Customer, etc. It's untenable. We have a case with NS support but they are just asking for PET screenshots and not giving any indication as to…

The speed, or lack of it, has been bad for a while and worse recently. I am seeing the same kind of wait times. I keep waiting for something to change but it just keeps getting worse.

Wow. That beats anything I've seen.

Not just transactions for us. We had times of up to 34 seconds for customer saves yesterday and slow as molasses again today.

I'm seeing pending as well going on half hour now Mine is in sandbox and supposedly premium architecture.

I got a bunch over the weekend but they were attributed to some 'performance related issues'. They were all workflow related. Had a couple today from the Avatax bundle, though. And we were extremely slow today. I get the feeling there are some changes happening.

Nice work around.

That's how we do it, too.

Cache rules everything around me.

Make sure you are using the function on client side if you want to have something other than west coast. See the image I posted above. If you are trying to use a date/time field with people in different time zones you can totally forget about trying to get any usable metrics in searches and, I assume, reports. They are…

Ok, that was interesting. I created three cases and had my east coast rep set the field (initialize the case) and got some interesting results. And in a way that I can show what is happening. If you look at this first screenshot you can see the column Initial Response (minutes from incident date) showing inflated minutes.…

The formula given to me by Raziel (my support rep) gave me an invalid expression error: from_tz(CAST(to_Date({custevent_cxs_init_res_time}) AS TIMESTAMP),'UTC') at TIME zone 'US' What really puzzles me about this bug is that it is fixed if someone on the west coast edits and saves the case. The weirdness is gone after that.

Evan, I was unaware of any work around. I have contacted my support rep and I will report back.

I do: Defect 241183 Here is the latest reply from my case #1794125 Hello Corey, We are very sorry for the delay. The issue was already escalated internally. I saw that it's already assigned to our Development team. They found that Date/Time custom field used outside formula is converted to:…

I would really like to hear from someone at NetSuite about this.

It's interesting that you mention web services. This really came to a head after we turned off syncing to our legacy CRM. It turned out that running these web services had the effect of editing and saving these cases which, as mentioned above, seems to fix the issue. In order to get decent data I installed a stripped down…

Update. The defect was fixed and I am now able to correctly manipulate the datetime fields in formulas. The formula that I am using, given to me my NS support is: round((cast(nl_tz.convert({custevent_cxs_init_res_time}) as date) - {startdate}) * 1440, 0) It is the nl_tz.convert that does the trick. The above formula will…

I am going to really fight against the notion of redoing something that is supposed to be native to the app. Especially now that I would have to update upwards of half a million records. We are at 490k or so cases now. I have it limping along with web services but if I was going to apply a field like this on another…

I haven't tried that, specifically but I have played around with this field and formulas for weeks on end. I will give it a shot. Might as well.

Are people just not trying to actually use this kind of field? I'm Flummoxed.

Have you tried just leaving all the remaining parameters blank? Supported http methods are HEAD, DELETE and PUT. This parameter allows for easier integration with external RESTful services using the standard REST functions. Note that if the httpMethod parameter is empty or not specified, this behavior is followed: the…

As of Dec 6th 2013 the update seems to have this working pretty well. No hiccups, so far.

Oh I'm pretty doubtful that a fix is coming, to be honest. This was a purchased app by NetSuite built by Celigo. Celigo is no longer working on it and I would be NS is far too busy to dedicate a team to fixes for this. I could be wrong but we were waiting for a couple years for the last integration to even support 2010 and…

Sorry Evan, I read the wrong subject; I have been encountering a few bugs lately. The Outlook Integration bug is Defect #- 259364. I have not associated myself with it. We were discussing it on this thread I have turned off even and task syncing since this issue showed up. I am leery now of turning back on this part of the…

Now, my client won't even run. Says it doesn't have the right permissions. SyncManager is currently inactive as it lacks the authorization to continue. Possible reason: you have entered an invalid email or password' That's not the case, however; it will run through the entire configuration again which won't happen with bad…

I have to exit the client and then restart Outlook to get it to start up again. This thing is more annoying than useful, at this point.

Careful now. Uninstalling and reinstalling can double your events in NS.

My bad. I have yet to make it my first instinct to go to the SuiteAnswers site for answers. I still just hit help and then sulk when the links are all broken after I search for Advanced Printing forms. Sure enough, though, when I search for Advanced Printing on SuiteAnswers I see FreeMarkerr referenced.

defect 263819

I take it back, kind of. <thead> works but <tfoot> does not.