Multi-subsidiary customers can now be enabled by support according to the release notes for 2017.2: If Technical Support has enabled the Multi-Subsidiary Customer feature in your sandbox account, you can create a multi-subsidiary customer record from a multi-subsidiary vendor record.

Did you attempt to specify the field as follows: <field>[scriptid=custbody_my_field]</field> And if the field is a custom field, did you include it as a dependency in your manifest.xml file or in your SDF project?

If you have already done your sandbox refresh to bring internal IDs into sync, then you should be able to have the workflow set the field to a formula that resolves to the record's internal ID. It would be cool if SDF would allow you to reference a record by external ID since external IDs can be maintained across accounts.

I believe it's a feature of NetSuite's Human Capital Management solution that let's employees give other employees "kudos" for doing good work.

I can't tell if you're kidding or not! Completely serious :-) There's a big market for employee recognition software, here's a competing solution where employees can be nominated, receive points, and redeem those points for gift cards and other prizes: http://www.octanner.com/

Glad you found a solution! It's annoying when an upgrade breaks something. You can usually upgrade-proof links by referencing a task link instead of hard-coding the URL itself. However, I can't find a task link directly to a PDF, so that might not be a solution here.

Saved search formula fields are documented search columns whereas the template uses documented fields. For the difference, in the SuiteScript records browser compare the fields section of the relevant record type: https://system.na1.netsuite.com/help/helpcenter/en_US/srbrowser/Browser2017_1/script/record/purchaseorder.html…

This is doable in the Freemarker template as well, for example: [LIST=1] [*]Create a variable to track a list of items already printed [*]Loop through item list, and if item is not in the list of items already printed:[LIST=1] [*]Loop through item list to get the total count and price [*]Print the item, its total count,…

We had to re-write the logic ourselves in a before submit user event script. But for your purposes, you can leverage the netamountnotax search column - write a before load script that performs a search and sets that value in a custom non-store-value field or custom page field when type == print

We need to set other fields on the transaction based on the discounted amount, and when you're setting fields on the transaction the best practice is to set them before submit so that you don't have to re-submit the record. Re-submitting the record is a major performance hit. If you're just using the information on the…

I agree that this would be a valuable enhancement. Calculating the application of discounts ourselves is not a good solution, especially with the waters further muddied by the new SuitePromotions feature.

NetSuite has a number of e-commerce product offerings including SiteBuilder, SuiteCommerce Advanced, and, soon, SuiteCommerce Standard. There are NetSuite consultants who will build a web store for your company on one of these platforms. These platforms are part of the core NetSuite product and therefore very tightly…

Hi Rachel, how do your needs extend past the built-in gift card functionality within NetSuite? That would help us point you in the right direction!

Will this integration better than Ava tax? Absolutely! I'm the lead developer on the ONESOURCE SuiteApp, so I'd love to speak to our solution's advantages. ONESOURCE is a single unified end-to-end solution from sales and use tax calculation to signature ready returns based on Thomson Reuters's enterprise tax research and…

I'm sorry, I thought you were asking whether it was safe to ignore the error. As far as how to go about ignoring the error, if you move your record updates into a workflow action script you can use a JavaScript try/catch statement around them.

The location and department should source in automatically from the employee record. Try adding the fields back to the form, and disabling or setting them to inline if you want to prevent users from changing them. That said, if you're not able to get the native functionality to work the way you want, a script or workflow…

If you're seeking the visibility of a single field on the record that tells you what created it, then it sounds like you've already implemented the best option. Workflows can generate logs if logging is turned on, but I'm guessing you've already done that and that tracing through the logs is more steps than you were hoping…

You can add a condition that the Old Record's status is not Completed.

The error is indicating that some process in your account is not completing successfully. So your options are: [LIST=1] [*]Track it down now [*]Or ignore the error and deal with it when/if you notice problems in the data [/LIST]

This error generally pops up when two different processes attempt to edit the same record at the same time. I'd investigate what is attempting to edit the record at the same time as the workflow in your account.

Under setup > company > autogenerated numbers, you can check the ALLOW OVERRIDE checkbox to allow the document number field to be edited for the desired transaction type. Then, you can write a script or workflow that sets the document number according to your formula.

Not sure if this is what the NetSuite dev was referring to, but you can automatically create an invoice or cash sale for a sales order using the "Transform Record" workflow action. That would result in the status changing to billed.

I don't believe there's any supported way to add custom code to the cancel button. What you can do is hide the native cancel button and create your own button labeled "Cancel" that does what you want it to do. But keep in mind that the user could close the web browser as well which would leave you in the same predicament.

If you want to do it only through scripting, then a workflow action script would not be the appropriate type of script. Try creating a client script with a fieldChanged method.

If I remember correctly, all user event scripts execute and then all user event workflows execute. You can re-arrange scripts among scripts and workflows among workflows, but all scripts always run before all workflows. But as khultquist pointed out, a better answer to improve speed/performance is to move as much of the…

Try triggering your workflow action on "after field edit" of the terms field - that approach worked for me.

I have also tried this approach and it works well. However, if the user has edit permissions they will be able to make the vendor inactive or active regardless of the Workflow via Lists > Relationships > Vendors as long as they have vendor edit permissions. I have made the field disabled in the vendor entry form. Any way…

Probably not the answer you're hoping for, but you can add the button via script and then trigger the workflow upon clicking it with nlapiInitiateWorkflow.

In a saved search, the first time you've received an item would be the MIN of ITEM when ordered by TRANSACTION DATE. When it comes to alerts though, I'd have the saved search with a filter that the MIN transaction date is the current date and group the results by item. Then you can schedule that search to run every day.

I'm referring to the minimum summary option.