I would add in criteria to limit the date range/period of the transaction type you are searching, which is Sales Order. "Billing Transaction: Period = This Period" doesn't restrict the Sales Orders, only the related Invoices, so NetSuite has to search all Sales Orders. Depending on how you're company operates, this may or…

What other criteria are you using? Are you restricting by date range? If not, that can make a huge difference.

I've found that the easiest way to do this is using script. If you're unfamiliar with scripts, it's not as hard as you might think for this case. For example, if you have a list of recordid in a spreadsheet, build a text file like this nlapiDeleteRecord(type, recordid1); nlapiDeleteRecord(type, recordid2);…

A few thoughts: In the non-summary, check to see if there are any values with errors Try with a smaller results set. I can't read your screenshot but you appear to have hundreds of results Try wrapping your statement in TO_NUMBER in case it's returning text

Yes, customize the email body using {results} and it will only show the results columns from your search. [ATTACH=CONFIG]n415646[/ATTACH]

I believe the record is submitted in it's entirety, so the user event script wouldn't know what has changed. But you could do the same thing by using a client side fieldchange script, that updates the custom timestamp. The timestamp would show the date/time of the event by the local user, not when the record was submitted,…

With a script you should be able to hide the button, using its id. I checked on an item entry form, the button's id is 'submitter' var save_button = document.getElementById('submitter'); save_button.style.display = 'none';

To expand on errol's post, you may want to set it beforeLoad if your users can set the value before submitting. And also check for condition of 0 items function beforeLoad(type){ var lineItemCount = nlapiGetLineItemCount('item'); if (type == 'create' && lineItemCount) { for (var i = 1; i <= lineItemCount; i++) {…

This can occur when a script or workflow is triggered on aftersubmit, and then re-submits the record. The process flow is [LIST] [*]Record is saved [LIST] [*]email alert triggered [*]script triggered [LIST] [*]record is saved [LIST] [*]email alert triggered [/LIST] [/LIST] [/LIST] [/LIST] If you have access, you can check…

Yes, it does indeed act that way (unless behavior changed in the last few releases). It's inconsistent with the triggering of script to script, so it would be nice if it was documented. See this thread [INDENT]corey Junior Member Join Date: Jan 2011 Posts: 832 #11 11-19-2012, 05:45 PM Ok, update. It turns out that, in my…

In my company, many people are allowed to create items, but certain fields must be completed before certain transactions are allowed. For example, anyone can create an Item with just a Name, Description, and relevant Accounts. But the Item cannot be added to a Purchase Order unless a custom Item field 'Tariff HTC' is…

A very short beforesubmit script could do it. Could possibly be done in a workflow as well. You can also try the built-in permissions but they are not very granular, for Cases you'd have to choose between View, Create, Edit, or Full.

You can automate it thru an emailed saved search, with the checkbox Send Email Alerts When Records are Created/Updated and the sublist Recipients from Results

Can you get a list of them, and just inactivate via CSV import? Or... if you really need to delete them, there are ways to script the process. For example create a custom checkbox called 'Delete This Record'. Then create a scheduled script that searches for records with the box checked, and delete them with…

We do something similar to JCirocco . Matching the date created on fulfillments and invoices catches most cases, but there is still one that we sort out manually: when we have multiple fulfillments on the same order on the same day. In theory you could also have multiple invoices for a single fulfillment, but we don't…

We are one world too, but all items are lot/serial. I'd try Inventory Items, and if you are using Bins you could try that too.

I use the INVENTORY_NUMBER table, with columns ON_HAND_COUNT and LOCATION_ID.

mms - You're right that Outlook is still alive and kicking, just not here! I suspect Outlook will be around for at least 20 more years, it's firmly embedded in the corporate world. Come to think of it, 20 years is probably not long enough, look at IE6!

I thank myself everyday for moving from Exchange/Outlook to Google Apps, about a year before we moved to NetSuite.

Try this function massUpdate(recType, recId) { rec = nlapiLoadRecord(recType, recId); rec.setFieldValue('custitem_wd_badges_refresh', 'T'); nlapiSubmitRecord(rec); }

The main question I have is, why does each division need it's own stock? Is it for tracking/reporting purposes, or do you have separate financials? If it's the former, I think you could accomplish what you're trying to do with custom records. It would take a lot of customization, but here's my concept [LIST] [*]Create a…

You can add a really simple client script to alert the user. If you're not familiar with scripting, you can build a Saved Search to warn to the user by email when they save a PO with wrong increments.

You could do this with a combination of custom fields/records/forms and scripting. The logic is to create a custom record that links the vendor, item, and multiplier (pieces/case). You would create you PO in units of each, and then the custom form would show a calculated column of Quantity/Multiplier (and hide the native…

You could still use the minimum quantity, set it to 31 or 31.25 linear feet. That might not be ideal but it does accomplish the same as the amount.

We use locations for this type of restriction. Also we have a custom tab on Items called 'Alerts' with custom employee fields for each type of transaction. With Saved Searches, we can then alert that employee anytime that transaction is created or modified. It doesn't prevent item usage, but it can be used as a warning.

Hi Gabby. Read this thread. There's an equivalent field called 'isserialitem' A couple years ago I tried it on my account with a couple of items that were accidentally created as non-lot. I haven't had any problems, but I don't know that I would recommend using this technique for your entire set of items. Since you are…

Hi Gabby - this kind of functionality can be added through simple customizations (saved searches with email alerts) or with complex scripting/workflow. We've added in first piece inspections, incoming inspection, assembly routing, machine and tool records, calibration, 3rd party outsourcing, etc.

Locations should be able to do what you are asking, with help from custom scripting. Essentially you create User Event scripts on the relevant transaction types that will stop those transactions from submitting. You might also be able to have locations unavailable to certain users/roles, so that only specific roles can see…

What about inactivating the old bins, doesn't that hide them in sublists?

To completely disassociate them you might have to use a script. Something like [LIST] [*]Add a checkbox field to bins called 'Remove this bin', or use the 'inactive' field [*]Create a saved search for items with bins checked [*]Create a scheduled script that uses that saved search to load item records, one at a time…