Eventually, as Sean mentionned, Netsuite will solve this problem. But untill that year or two from now, no, there is nothing nice clean and simple you can do.

You can perhaps consider using Description items. However, I'm basically with Amy - I think you're using the wrong medium to expose price information.

"Do it" is the guidance :) It is extremely bad practice to have many users on such powerful roles. You are one bad employee termination away from malicious acts that can destroy your business (ex: mass-scale record deletion, etc) You simply need to conduct an exercise to review what their daily duties are and map that to…

Option #2 is the best practice. It is not possible to make Employee records cross-subsidiary, by design.

I have had clients that touch the farming industry, but am not sure what you entail by "grower management". Can you elaborate a little on what specific functionality requirements are needed, and I can do my best to see if NetSuite support that.

Work Orders require the Light Manufacturing module, which you most likely do not have. Therefore, unless you are willing to buy the module, you will not be able to test or use them. In any case, I don't think WO would really help you. Yo are looking for a Product Configurator type solution - made all the more worse since…

You keep paying or export to an external database. NS does not keep data for free.

Hi Gary, Tribridge/DXC is experienced with enterprise accounts. Do you want to PM me a phone number and I can ask someone to give you a ring?

No. There are some 3rd parties that have developed tools to test NS code. I think you may be able to find some on SuiteApps.

Assembly Items have a checkbox on them called "Can be purchased". You can enable this to allow either purchasing or buying of assemblies. Deciding whether to build or buy is a business process question, so you'll need to figure that one out. If it is based on fixed rules, you can consider hiring a developer to script the…

1. This is a pretty good way of handling it. I have also customized this process to automate it a few times, but broadly speaking your "recipe" is correct. 2. You can do that, yeah 3. I strongly recommend the use of Auto-Elimination at all times. All things said though, proper interco accounting and elimination is ALL in…

Well, I'd check the following: 1. I think you said the Suitelet creates brand new fulfillment, right? It doesn't edit existing ones? If so, that looks ok. 2. Does the Suitelet set line-level departments to either 1, 2 or 3? 3. Did you check the script deployment record?

Sounds like you need a contract management solution. NS has an add-on module you can guy, but you can also consider 3rd party ones.

There is no way to commit stock when the SO is in Pending Approval. As you indicate, this is by design. The approach of using a sort of "custom" approval process as you describe with the "Sales Hold" box is not uncommon, and should be fine. If your company is small enough and disciplined enough to obey the checkbox without…

Suitelets trigger user event scripting. Double check your item fulfillment script to ensure it is properly deployed, including within the code to see if there are any restrictions, such as an "if" clause that would limit execution only to the UI context.

There is no out-of-the-box feature to do this, for many reasons. You can build your own local data warehouse and use a tool like CData to suck all the data out. Of course, you should not expect that data to be especially useful in any way. None of the table associations or anything like that will carry over.

FLOdocs is BY FAR your best option. Otherwise, you're looking at a monumental amount of diligent manual work, or preferably very strict change management handles outside of NS. Basically, anyone wishing to make a customization change should go through a strict process where all changes are reviewed and logged (probably in…

Well you should be using a Sandbox account. Large enterprise accounts should probably use multiple Sandbox accounts. A tool like FLODocs can be part of good release management. Aside from that it probably comes down to process.

Create a new account and use a Journal entry to reverse the old account's balance and set the new account's opening balance. Note that this gets more complicated if the account in question holds foreign currency.

Then you want FLOdocs. The type of reporting you're looking for is only available through them, via the metainformation spiders they fire off to collect that stuff. Otherwise, base NS has poor-to-non-existent reporting capabilities for what you're looking for.

I'm assuming you mean in bulk or automatically, since of course you can close them by hand. Workflows cannot cut it because workflows can't touch line items. A script or a CSV import are your best bets. Script is this is part of a logic set as opposed to a needed one-time effort.

Could be done with customization. Not possible without customization.

While BOMs do not allow variable quantities, Work Orders do. So one solution would be to override the Quantity at Work Order time. This could be automated via scripting, but you can also manage it by hand.

A Sales Order belongs to one and only one customer. The subsequent Invoice belongs to one and only one customer. So your presumption that "everything is fine" with one Sales Order that has items for multiple customers is false. You must submit one sales order per customer. "The customer of a SalesOrder is definitely not…

Hmm. Without the ability to flag the record in any way, that'll be tough - the emailing absolutely, in no way, modifies the order... so there is no real way to know it happened. The only thing I can think of is using the date created time stamp. Add a critaria so that date created is equal to or greater than 4 hours ago.…

Well, the good old answer is "depend"! It'll depends on what underlying module you have processing your subscription. If all you have is Billing Schedules, then yes, option 1 will typically be that way to do. You could customize your PDF Layout to trick the quantity into showing "1" all the time. Another method would be to…

You could have a link on the SO that points to the saved search, even filtering that to the correct results via the dynamic value of the Saved Search link. Then the user would need to manually press on Save and Email.

I don't immediately see any problems. It may affect some aspects of reporting but I think you'll be ok.

Are you uplifting your current account, or getting a new account?

That's not too bad. You'll mostly just need to think about how to "one worldafy" everything. Customers, Vendors, Items, etc. Might need to create new customers, in particular. Then consider interco setup. That's somewhat optional, but interco/auto-elimination is one of the strongest aspects of OW, so it's best to take…