Reports can indeed only ever be Viewed. You may be looking to add the "Report Customization" and "Report Scheduling" permissions

Unfortunately the report you attached just isn't loading for me, so I am unable to review it. Unfortunately jschneller seems to have been able to see it and report that it's not a true NetSuite Script performance audit performed by qualified Suitescript experts. There are a number of optimizations SuiteScript Developers…

There should not be any inconsistencies in the behavior of form and api. If a form can do that then api must also be able to do the same That is not always valid assumption with Netsuite. In any case, if you take a look at UI behaviour, you'll also see the Opening Balance field is only available when you create an Account,…

I'm not sure how you are trying to go about doing this, but the proper - and only - way to give an account a value is to use a transaction, like a Journal Entry. You cannot just give a value to an account. Netsuite is a transactional system.

Usual suspects of scripts/workflows?

NetSuite support multiple Invoice Forms, which in turn each support their own PDF Layout. The layout, fields, static information (bank details) and logo can each be set per-form. Without resorting to customization, though, you will need to manually select the right form at order entry time.

There is a setting in Accounting Preferences to make edits to SOs make them require approval again.

Did you file a Case with NS Support?

Are they plain Inventory Items or do you use Serial/Lot Numbers? Do you have Bin Management on?

Hmm. You should probably contact NS Support. The only thing I can maybe think about would be a Transfer Order where the items were shipped out but not yet received. I can't rememeber what that would look like in terms of committed and available. Probably best to just ask Support.

This regularly happens. Try calling NS Support, they can "reboot" your queue.

This is a known Excel problem, not a NetSuite one. The solution is either simply not to open (and ESPECIALLY not to save) a CSV file using Excel, or every time you need to touch the file, import the data as text as per these instructions:…

Ok, couple of things. Unless you are in a business with an exception where you must set your own special tax rates, best practice is not to set the Tax Item on the Customer's record. You should use Netsuite tax engine. It sounds like this is what is happening for California. So, oddly, it would seem perhaps the CA setup…

Correct, that is not a script error. You'll need to contact NS Support to receive more information about the Unexpected Error, they can give you the backend message. I might suspect it's a problem with a custom field. Have you added new fields recently?

Can you provide the exact error message you are receiving?

The plot thickens. Hmm. It could be a client-side script deployed directly on the form, which would indeed not appear in Scripted records as well as cause the error to pop BEFORE the submission.

They have release notes, it's not a technical restriction. The problem is that the day they start releasing note fixes to the public is the day SAP issues a press release that says "Netsuite riddled with bugs: engineers fight 100s of bug a week!" It can't be done for political reasons.

There is no limitation to deploying Suitelets to Partner Center. You must have a deployment issue.

Thanks again :) I have now officially undeployed all client side scripts (and indeed, almost all scripts) that were listed under Script Deployments. All we really have deployed at this point is a couple of custom user event scripts (one on RMA's, one on SO's) and 2 bundle installations. The error still occurs! I just want…

Hi, That is very simple, I don't know what would cause NS to not diagnose this right away. You have a broken script deployed on your POs and Bills. Undeploy all your scripts then turn them back on one by one to identify the failing one. Then, contact the provider of that script and tell them to fix it.

It's happened. I would recommend contacting NetSuite Support to get the ball rolling. They will require some information from you, but you should go through that channel to get results.

Could be just about anything. You'll need to contact NS Support, they can provide more insight.

Thanks Evan

Hmm. Do you have any sort of scheduled workflows or scripts? I recall the Last Sales Activity bundle causing issues like this a while back.

I recommend you open a Case with NS Support's performance team. They will be able to provide advice on what could be causing that kind of load time.

If the script just edit/saves without changing anything (i.e. it is basically badly coded) then there might not be any notes to show.

I didn't check that link, but does it say the solution is to include the field on the SO, but erase the label? This makes the field invisible but still "there" and thus able to receive the value. Educated speculation: the problem here is the way sublists are coded. They aren't really "there". It's a floating div object…

Oops. Well, there is probably an enhancement request you can tag on to. Aside from that, it's just a limitation, I don't know any way around. Well, you can try opening a Support Case and ask for NS to execute a zero out. I think I've seen that happen before.

That's indeed a common issue. The "severity" of the performance difference between Sandbox and Prod seems to vary from account to account, which makes me think NS might have some control on it (for example: perhaps they can change the server your Sandbox is hosted on or something). For some very large accounts where I was…

Try filing a case with NetSuite in regards to performance. In theory, there are some things they can do to increase performance. You don't really have any other options anyway, so that's your best bet.