Perfect! Exactly what I was looking for. Thanks!

Can you trigger it off Status? I know from the UI you can trigger alerts based off Status = Pending Receipt (and/or Pending Billing) which only occurs after all approvals in the chain have been received.

Case: 1688544 URGENT DEFECT: Contact Record Returning Unexpected Errors

My case is tied to that defect but it shows the defect as S2

6 hours and no resolution/update? We are effectively unable to do anything -- all scripts are throwing unexpected errors.

Same problem here on contact records...

We built a custom integration that imports card activity from our employee's corporate AMEX cards. This process imports the AMEX charges and creates expense reports on behalf of the employees. The "advance" amount is set to the same as their total charges -- so this nets to $0 due on the expense report. The process (prior…

Case: 1351694 Defect 181100: Expense Reports Automatically Marked Complete when Net Amount is Zero... Marked as an S2. This is killing us and throwing off our financial statements significantly since we can't process these expense reports!

Yes they fixed that problem.

csebastian - thanks but that isn't the problem we are having. I’ve done some debugging on our side. The problem narrows down to a change in NetSuite code sometime after July 7 (not sure of the exact date – but we know that on 7/7 the system was working properly). There are two bugs that were introduced since that change:…

Good info. Unfortunately #4 makes it impossible for us to manage since we have over 5,000 saved searches and several more created every day throughout the organization. This seems like a pretty substantial bug since it exposes all customer/contact data to Partners.

Perfect. Thanks for the info.

Any update on this? It still exposes all of our customer data to all partners so we obvioulsy haven't implemented this solution yet. Case: 1302508 Defect 193690: Partner Role = T on a custom role and restriction ...

The custom role has dashboards, searches, views, etc. that expose results from ALL customer, contact and transaction records regardless of the Partner setting. Defect 193690: Partner Role = T on a custom role and restriction is not working This is only listed as an S2 which seems strange since I would assume this is…

Thanks to a quick response from NS Support the problem has been identified and fixed. We had implemented some workflows recently which had only affected the webstore.

We have this problem too. All of our scheduled scripts are stuck in deferred status now (for the last couple hours). We've had a couple specific scripts stuck in deferred off & on since July. NS seemed to fix the problem once but the problem reappeared a couple weeks later. Tonight it is particularly bad.

I did last night Defect #188639 - SSS > Scheduled scripts stuck in In Queue/Deferred status

Still a problem... the NS support response was: "Just want to verify if this is the specific certificate that you were using: ThawteServerCa.der since this is the documented one" The problem is a list of supported root certificates does us no good unless we can map that to a specific product offered by a specific company.…

Thanks for your quick response!

Tried that and it didn't work for Item Options. I also tried Trans Column field which works internally but not on website with a logged in user.

This works perfectly now... thanks!

The problem is I'm trying to have the filtered list on a Customer (Entity) record. We haven't had the issue with Transaction records... but the process doesn't work on Entity records.

No scheduled search alerts for us this morning. Anybody else?

Fixed! For anybody following this thread, the solution is to add .id at the end of the sales rep formula. For example, I was originally trying to update the transaction sales rep with a formula of {customer.salesrep} but I needed to put {customer.salesrep.id} It now works perfectly (on both transactions and activity…

Funny you should ask... we've been dealing with the same problem for the last week. I was actually on the UG today looking for an answer to a problem we've encountered trying to address this issue. We put in a couple things to address this specific problem... they are not ideal workarounds but better than the default…

I was doing a Mass Update: Mass Updates / General Updates / Opportunity then using the formula on the "Mass Update Fields" tab. It should be noted that in order to Mass Update that (or any) field you will need to have visibility & access to that field from your normal UI for that transaction type. In other words, if you…

Thanks for the suggestion. We currently are editing the mass update each time with a new rep name (if we hard code the name it works fine -- just the formula doesn't work). We are actually trying to use this formula as part of a scheduled mass update. There are a lot of accounts that need to be moved on a regular basis so…

Defect 166402 - Mass Update > Opportunity > Set Formula for Sales Rep field > Getting the message "An unexpected error has occurred. Please click here to notify support and provide your contact information."

Apparently the source of the problem was the employee record had a "customer center" role (among others). This allowed the two entity records to be merged together. Unfortunately these records are still tied together with no update from NS on how to separate them. It continues to be a problem every day... I'd be interested…

Email (domain only)