Definitely unusual. We've never had a complaint about the checkout speed in over 3 years. If this is an isolated incident, it could have been any number of issues on the client end.

I concur. We've been with Netsuite for 4 years now and have also noticed a marked improvement in the last 6 months to a year. We had a lot more than 2 issues this year but support is much quicker to respond, usually responding within hours to an online case. That used to take weeks. Keep it up Netsuite. Edit: We have gold…

All fixed on our end. Thanks.

There are all sorts of web store image problems in 2008.2 Here are two of them that are related: https://usergroup.netsuite.com/users/showthread.php?t=15176 https://usergroup.netsuite.com/users/showthread.php?t=14845

Fix is supposed to be released Thursday (Oct 23) or Friday.

We're waiting on this too.

For once, they have updated their status page. http://status.netsuite.com/status.html Sort of ... The uptime stats aren't live apparently. They should be dropping by .1% every 15 minutes or so. I suspect that they'll do that after this blows over. As bad as this whole thing is, I'm so happy it's not me scrambling right…

Even www.netsuite.com is down now. Ouch!

Yup ... big time outage. Netsuite and Website both dead. -- Time for brunch I guess :)

Us to ... whew!

And we're back. That was just bad timing because we had just sent out our monthly ezine.

we are up here in Vancouver BC 2:20 PM PST Hey! Someone else around here. Cool :)

Yup ... dead in the water for all users. Not good. status.netsuite.com says .. Minor Service Interruption Few accounts affected. Please login to your account for more specifics Login to my account? That's the problem though, isn't it!

Yes ... just when I thought things were getting better, 2008.2 messed a lot of things up for us. Some time ago Netsuite mentioned that they would avoid doing major releases during the last quarter. Well, it's almost November and we're still dealing with the aftermath of 2008.2. I would love to see only one major release…

SLT: Service Level Target In other words, a method for assessing severity and projecting associated timeframes for fixes. A more detailed explanation can be found in the NS Support Center at https://system.netsuite.com/app/center/center.nl?sc=30 Ahhhh ... Thanks guys.

I'm not sure, but it might depend on what the report is looking for. What are you reporting on?

That did it. Thanks Phillip.

Issue #141540 Any chance of getting this bumped up a severity level? Without divine intervention (that means you, Evan almighty :) ) I'll need to re-do all the affected templates if this will take months to fix. It's embarassing having error messages all over our web site.

Case# 693261

You betcha: Floor(ABS({today}-{custitembirthdate})/365.25) PS: The error is gone (for now) and the age appears correctly online. I'll let you know if the error message comes back.

Seems to be fixed in 2008.1. Thanks again.

Any progress on this? Should I start removing the age field from our templates?

Thanks Evan, I really appreciate it.

Ooooo ... that's a handy little tip! Thanks Angela.

I stand corrected. Now it's broken again. So ... this is an intermittent problem. Hope that helps narrow it down ;)

Yes. Third time (at least) this month.

I don't see fiscal year anywhere in company setup. Where is that? PS: We did set up our Accounting periods, but that's not under Setup > Company. EDIT: Ah-ha ... there it is! Setup > Company > Company Information > First Fiscal Month The searches work now ... kind of. I think the searches are never going to work properly…

Yup ... ours is too (again). It's not been a good month.

We can confirm that on 02/18/2008, between the approximate times of 2:30 PM and 3 PM (PST), hosted web stores experienced intermittent slowness. Our monitoring detected the interruption and the cause is under active investigation. We will provide updates once they become available. Thanks, Ted That leads me to wonder why…

Yup, I tried that. It's simple to re-create. Create a transaction search. Choose date as a criteria. Select "within last fiscal year". It chooses last calendar year instead. The problem is most apparent in all of our dashboards. None of them are accurate.