In my case, we're Solution Providers, so often during implementation we may need to delete everything for x reason, such as a bad import or whatever. But generally, you're right, you shouldn't really be deleting transactions. There may be specific reasons why you'd want to, but I don't think you'd want to do that as part…

Erm, where in Netsuite is there a Mass Delete Transaction functionality? Ir is that the one where you have to call support to have it enabled?

I don't think so, but you can do a CSV update.

There isn't really a limit, but I've seen system performance take a nosedive at half a million. What order of magnitude are you lookin at?

Where does it display est gross profit? I have never seen this functionality but it sounds useful. Setup->Company->Enable Feature, Transactions Tab, Gross Profit checkbox. It requires some config, so you should read the associated Help to set everything up.

I am intimately familiar with COGS problem, having just spent 6 months helping fix it in a customer account (well, technically, it's not fixed quite yet, but getting there). I think there's a couple of reasons why this can happen to an account. But it seems the primary reason has something to do with very small numbers…

Last time that happened to me, it was because the account had, say, 20 users, but had recently cut that down to 15. But there was actually like 16 people that had access... Which caused a bug similar to what you are experiencing. I'd call Support.

Right - but my Sales Unit is in Pounds also, NOT my base unit of Gallons.

I had when it first happened last week. It got tagged as an S3, I phoned and had it bumped to S2. I couldn't wait for even a S2 so on a hunch I deleted all the deployments and recreated it, which fixed the problem (for a while anyway). But it's a good thing I tried on my own cause the case was on the verge of getting…

I get an Unexpected Error when trying to access the Help, and no results are ever found.

Affirmative. Down too.

You can call NS Support and ask them to tell you the error they are seeing in the backend database. Usually this is FAR more descriptive.

I have dozens of workflow critical scripts timing out. This is not good... Can we get an explanation and a fix ETA?

I believe that means the FedEx service you selected (standard overnight) is not available where you are trying to ship. -not all fedex services are available everywhere. On FedEx.com you can try to make a shipment to the zip and see if standard overnight is available. It probably won't be.

A Sales Order either create a Cash Sale or an Invoice based on the Payment Method. If you select a Payment Method, it will turn into a Cash Sale. If you use Terms, it will turn into an Invoice. Note that I think you have to use the correct base Form for this. I think there's one like "Sales Order - Cash Sale"... don't use…

Perhaps we can help. I have emailed you.

I'm having the "Connection Reset" every other page load as well.

I think NS Support is your best bet.

It is normal to be able to create SOs for more items than you have in stock. Netsuite commits what it can, and sets the remaining to Back Order. You should not* however, be able to create Fulfillments for Back Ordered items. *this depends on your settings - it's actually possible to allow Netsuite to fulfill BO items, thus…

Ah didn't know you were talking about web store orders. According to your settings, you're correct then.

Nah, you could pass along stuff like internal ids as string or integers before. I've entered numbers as '123456' as well as 123456.

I also talked to a rep and was told that my search related errors were different than the saved search errors. I'm getting UNEXPECTED_ERRORS on non-saved searches (from scripti). Per Gladstone's info I tried constructing a new String for the 4th parameter and that changed the error to a complaint about an invalid filter…

We're trying to determine the extent to which data was corrupted due to searches seemingly working but returning random data. Some spot checks seems to indicate that a lot of searches continued to work. We checked some major scripts and it seems everything is ok for those. However, it may be very very difficult to assess…

Hi all, If you use an integer variable for the 4th argument, you can simply add .toString() method to it. Here is an example: That worked!!! It works with nlapiLookupField as well.

To echo Eric's concern, please make sure the fix will be compatible with intergers as well as strings - I don't want the code I corrected with .toString() to stop working when the fix goes in.

Ah ha! I can confirm that the problem IS still searching not working! I have the following line of code: taxRate = nlapiLookupField('taxgroup',taxCode, 'rate'); I am passing taxCode = -8 "-8" is the value of -Not Taxable- The above lookup should return 0, obviously. It is returning 4.00 So looks like SOME searches are…

I just ran a little test - I used nlapiLookupField and it worked. In fact, for my script that is currently failing, I can see in the execution log that everything was and continues to execute normally. My script is a beforeSubmit field, and it throws unexpected errors when the record tries to save. As the script changes…

What changed last night?? I have a client getting unexpected errors on ALL their orders - all 400 a day of them. They are script heavy, but the scripts are critical. WHAT WAS THE CHANGE??

Inventory Adjustments cause overnight recalculations when they are dated to a point BEFORE any existing transactions. It is doubtful a Support Rep that is not an inventory expert would have known this. I'm not sure this is written anywhere in the Help either. But basically, when you place an Inv. Adjustment dated to a…

Just talked to a rep - All saved searches are throwing Unexpected Errors. It is S1 pending hotfix push, expected "today".