Since employee roles are exposed to SuiteTalk and SuiteScript, you could build an integration to accomplish this. But no, not out-of-the-box.

No, not supported for admin role

If you edit a folder, you can restrict it by class, department, subsidiary, location, or group. You can create a dynamic group of all employees and restrict all folders to this group, except the folders you want to make available to partners.

The first thing I'd investigate is whether the error using the bulk invoicing feature can be resolved. If not, then I'd look at a simple mass update script like this and run it as a custom mass update: function billSalesOrder(type, id) { try { // invoice sales order var inv = nlapiTransformRecord(type, id, 'invoice'); var…

With SuiteScript you can load a record, set the external ID, and submit it. Depending on your use case, you could do this in a user event script, mass update script, scheduled script, etc. The code would be: var recordId = '123'; var recordType = 'customrecord1'; var record = nlapiLoadRecord(recordType, recordId);…

Have you considered a before load user event script instead of a client script?

I'll throw in a shameless plug for Thomson Reuters ONESOURCE Indirect Tax, we should be able to be much more competitive on pricing: http://suiteapp.com/ONESOURCE-Indirect-Tax-Integration-for-NetSuite

This is often addressed with an approval workflow that "locks" bills after they're approved.

Try going to Lists > Mass Updates > Mass Update, expanding General Updates, and selecting Invoice. Then you can restrict your results to the invoices you'd like to send on the criteria tab, on the Mass Update Fields tab select the checkboxes in both the Apply and Value columns corresponding with the "To Be Emailed" field,…

Are you using any system integrator tool such as Boomi, Mulesoft, Jitterbit, etc.? Although customer deposits appear not to be available via CSV import, they are available in the SOAP schema for integrations: https://system.netsuite.com/help/helpcenter/en_US/srbrowser/Browser2017_1/schema/record/customerdeposit.html They…

Maybe a better way to ask my question would be - what exactly is on hold pending approval if you're already sending out bills? What functionality should be waiting for the sales order to be approved?

No, that's by definition what the sales order approval process is supposed to prevent. If you're using approvals for a different reason, you might want to look into using a custom field instead of the built-in approval status.

The deposit will automatically apply, but the deposit application can be edited and applied to another invoice instead.

If you don't want the account to be used at all anymore, consider inactivating the account record.

Not possible in 2017.2, but the 2018.1 release is adding the ability to edit cancelled vendor bills. The 2018.1 release will likely permit deletions as well, but you'd have to wait until you have access to check.

You're not the only one, that page does not offer much in the way of customization. Have you clicked the Customize button on the Bills sublist to see if the field you're looking for is available there?

Yes, let me provide some more details. The goal is that our AR dept. wants to send a deposit invoice to the customer. We've customized the SO approval workflow to add approval buttons for 3 separate depts. Clicking the custom "[Dept.] Approval" button will check a corresponding custom approval box on the SO. After all 3…

I can create a custom field, but the native Status field will still need to be Pending Fulfillment before we can invoice. True, my suggestion was to set the status field to pending fulfillment for sales orders that you need to bill and track whatever else you're trying to track now by having the status as pending approval…

As far as I know the status field is not available as a standard mass update and would require a custom mass update script if you wanted to use a mass update. Have you considered using a CSV import?

File a case with NetSuite Support and reference this ticket number: j8ym72hbzb8no8fgxzwm NetSuite Support has the ability to see back-end logs that end users and partners don't have access to.

It sounds like your tax provider may have implemented inconsistent rounding rules. I'd report the bug to your tax provider instead of trying to fix it yourself.

The editor doesn't make it obvious, but you can use tags that reference fields in the subject of the template just as you do in the body. So the subject of your template would be ${case.title}

If you import customers and contacts together, you can map the "Attached Role" field on the contact to the desired role.

Create your own button that pops up a window with the URL of the send email popup with the following appended: &record.recipientemail=abc@def.com If you want to get fancy, you can hide the native "Email" button on the sublist inside a before load user event script and replace it with your custom button. You may also be…

On the customer record, look at the contact list. Right above it there's a button called "Update Primary."

I don't believe that's possible. Keep in mind that that email may go out to a user who has access to multiple NetSuite accounts, so the email couldn't be customizable within a single company's account. What you can do is send out your own scheduled email

In addition, try to limit how much scripting you are doing synchronously. If you defer all of your custom logic to scheduled scripts, the submission will be much faster and the user probably won't be tempted to re-submit the form.

Those are script IDs of custom CRM fields in your account. Those fields may be mandatory and missing from the form or exist in the form definition but missing from the HTML template.

Here's a list of all fields on vendor bills: https://system.netsuite.com/help/helpcenter/en_US/srbrowser/Browser2017_1/script/record/vendorbill.html If that's not a custom field, then it is the "Customer" field on the expense SubList.

I've only had trouble with using the bundle repository, so I'd recommend avoiding it. Use one NetSuite account for development and COPY to a separate NetSuite account for deployment. Then end-users can install the bundle directly from the deployment account, no repository necessary. If you need to support multiple versions…