For those of you affected by Defect 586586 yesterday, how are your web sites functioning today? We were affected between around 2-4pm est yesterday. I'm getting some reports this morning of slow page load times for bot of our accounts/websites.

Our websites went down again about 20 minutes ago, displaying the Error 520 message again. Update: They are going down for just a few minutes at a time before coming back online. So far, this sequence has happened 5 times in the last 40 minutes.

Also using Cloudflare, and both sites are currently back online.

We appear to be completely back to normal. I just tested the websites for both of our accounts, and was able to log in and submit sales orders through both. Customer service says they are back to normal as well. I just noticed an email update from NetSuite I received about 5 minutes ago: Our engineers have manually applied…

Same here. UI: We are now able to log into the UI again. We are now able to save Item Fulfillments again. We are NOT able to process credit card payments. Website: Websites are now loading and displaying correctly. We/Users are NOT able to access the Sign In, My Account, Cart or Checkout pages. This means we are NOT able…

Call your NetSuite rep directly and have them submit a case for you.

I am able to the issue message on the status page. It seems to be getting worse. Our websites are either not loading with stylesheets, or not loading at all and displaying the 'down for routine maintenance' message. We are no longer able to access the UI at all.

The Sales Order was a recent order, which was submitted through our web store. I just created a Sales Order through the UI, and the Department and Class are both populated for the Kit. I then submitted a test Sales Order through the web store and the Department and Class is not populated. So it looks like the info is not…

I sure can. Here is an Item Record for a Kit Item that was on a Sales Order we received yesterday: This screenshot is from the Sales Order, which shows the Department and Class info is not populated. I checked the item's System Info to see when the Department and Class fields were populated. The Class field was populated…

We've also experienced some sporadic success for very short periods of time using Microsoft Edge, but there has been no consistency at all. By 'success', I mean able to get a record to save without crashing after a long period of waiting...while holding our breath and crossing our fingers. It up, it's down, it's up, it's…

Same for us. Users are still experiencing the issue. Is there an estimated time frame for how long the 'lingering slowness' period may last?

Thank you guys for the replies. Yes, I can confirm that both the Department and Class fields are visible on the Group/KitAssembly item records (Entry Form). All of our Kits also have a Department and Class assigned. The Department and Class info gets populated at the transaction line level for Assembly items, just not the…

I am starting to get reports from several users that the the system is starting to run slow again. Anyone else experiencing this?

Why are issues taking so long to resolve lately? The update to 2019.2 took both of our companies completely down for 10.5 and 12.5 hours. When 2020.1 rolled out, we could not process any orders that used FedEx Real-Time rates, which is about 90% of our orders, for about 40 hours. The current issue has been ongoing for…

I am able to fulfill and bill orders on my macbook using Chrome. A co-worker's desktop PC is timing out when trying to fulfill and bill, but she is able to do both when using her PC laptop using Edge. On her desktop, we have tried clearing browser cache, an incognito window, rebooting her desktop, and other browsers, but…

Same here. Our users are still not able to fulfill or bill orders.

Both of our accounts are still very much affected by this issue. My phone has been ringing off the hook all day asking when this is going to be fixed.

Yes, both of our accounts are experiencing very slow page load times in the UI.

Thank you for posting the Defect number. We just discovered that both of our accounts are affected by this. Were they able to quickly resolve this for you guys that were affected?

I can not agree with you more, and thank you for posting this. I've wondered for a long time if it was just me that felt this way. The old forum was so much easier to use.

Both of our accounts are in the same data center. How many accounts were affected, and how many are left to be restored?

One account came back up an hour ago, still waiting on the other one. How much longer is this going to take??

Can you share a screenshot of the Inventory Adjustment form filled out before you try to save it?

Awesome, thank you David! I expected it to be fairly easy, but not that easy.

That did it! Yes, I had the Customer Name grouped, Amount summed, and Number counted I was trying to set the criteria under the Standard Criteria, not the Summary Criteria. I had the feeling I was missing something. Thank you very much for your help!

I just got the formula figured out. It needed single quotes around the 1.5. Formula (Numeric) - Sum - CASE WHEN {custitem_pr_factorial} = '1.5' THEN 1 ELSE 0 END However, my question still remains, because the working formula was formatted identically. How could one formula work and the other not? Thanks, Chris

That was it! Thank you very much!

Thank you! I have the formula working perfectly from my original post, but I am having trouble with the next formula. Basically, there are two parts to this formula, which are the formula mentioned above a custom field: Part 1: ROUND(SUM({custrecord_qtyshippedyesterdayea})/NULLIF(SUM(CASE WHEN {custrecord_available} > 0…

Thanks for the sanity check. I thought that paren needed to be removed, but after looking again it definitely should be there. However, that paren was the difference between "An unexpected error has occurred. Please click here to notify support and provide your contact information." and Error:Invalid Expression I started…

That's correct. This works: ROUND(SUM({custrecord_qtyshippedyesterdayea})/NULLIF(SUM(CASE WHEN {custrecord_available} > 0 THEN 1 ELSE 0 END),0)*10,2) This generates the unexpected error: ROUND(SUM({custrecord_qtyshippedyesterdayea})/NULLIF(SUM(CASE WHEN {custrecord_available} > 0 THEN 1 ELSE 0…