My Stuff
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
Comments
-
OneWorld is the best choice. Option 1 is the way to go if you are unwilling to pay the price of OneWorld (it is, of course, more expensive). The 2 account option no longer makes any sense now that OneWorld exists. 2 accounts will most likely be more expensive than a OW account, and you won't be able to run consolidated…
-
User Event script affecting line items are basically 100x faster, yes. What information do you need to pass on to beforeSubmit?
-
I really, really don't recommend doing that. Hacking the sublist is a very bad idea. It will almost certainly cause all sorts of problems with any other line item script, and your code will probably break out of the blue one day when NS patches something one fine Thursday night in the backend.
-
Playing with line items in client side is a bad idea. Yes, performance is absolutely terrible - usually 1 to 2 second per line. If at all possible (it may very well not be due to desired business case), I'd strongly recommend switching to a beforeSubmit script. Now, you're also using an unsupported method to copy line.…
-
Hi Derek, If you want to give users a chance to edit the modified lines before the transactions is changed, then no, you do not have a choice. It must be done in client-side and for orders of that size, you will indeed run into problems. To resolve the performance problem, you have to drop to User Event. The user would…
-
You'll need to script it using nlapiXmlToPDF()
-
I believe we faced the same problem, so we stayed on version 2, for now.
-
As I recall, this is on the roadmap, but not yet available. Last release they enhanced the way Cases and support emails worked, allowing you to have 1 return email per sub. I recall them saying multi-branded employees were eventually going to happen, but not yet.
-
Please see this thread
-
Did you also define the parameters on the script record?
-
Before Submit will work, yes. Emails are sent between Before Submit and After Submit.
-
No this is not yet supported. I encourage you to file an enhancement request though, because I see a lot of people asking for this.
-
If you go in the UI on that SO, do you see the Bill button? Are you able to invoice this SO from the UI?
-
In Accounting Preferences you'll need to turn on "Invoice ahead of fulfillment" (might not be that exact wording).
-
You can't customize the file cabinet screen
-
Well I guess you could catch it, do nlapiSendEmail(), but then to kill the standard NS email about to be fired... throw an error? Not very graceful.
-
Oh, I see. Mmm.. I don't think so. I think that trigger refers more to the action when you push the yellow email button, or if you press the small grey email button that pops up the email building box. The email sent out when you tick in to be emailed doesn't trigger any events as far as I recall. But you should be able to…
-
You would need to calculate the value of these fields with suitescript, and write it into a custom field. Afterwards, there would be no problem to print this information.
-
Changer the header... what do you mean by that? Do you mean change the columns? You can't do that in client-side. You would need to submit yourself to execute back in user event and then come back into client-side. Messy. Alternatively, well, you COULD do it all in client-side but you'd have to custom build your sublist…
-
It's been a while since I played with Web Queries but IIRC you'd need 1 page per Query.
-
The simplest solution would be to email each search seperately. Non-Users cannot be granted access to a tab that had portlets on it - or rather, you can, but they won't see the portlets, as these are built to respect permissions.
-
Those look like Searches, not Reports, no? Searches don't have Web Queries. There are fancier alternative for sure, but they all involve a fair sum of development costs or 3rd party module purchases. You'd have to REALLY want it though. Free vs Expensive is not usually a tough choice...
-
Hmm... I'd stick a link in the email, which would be the URL of a suitelet with some extra params to identify the report to approve and such. When clicked, the Suitelet would activate and cause the approval of the expense report.
-
Yes, in the help for nlobjSearchFilter, the entire list appears.
-
Users need the "List->Financial History" permission to see the transaction tab on customers.
-
The Help documentation for nlapiXMLToPDF lists a couple of simple examples, though I won't deny you need some pretty solid technical understanding to use this API correctly. If you decide to give it a shot feel free to start a thread and post your code as you work on it, I'll give you a hand.
-
Those are Netsuite standard (built-in) reports, so cannot be limited to roles. Oh yes they can. Edit a role and check out the Reports tab.
-
Add a subtotal item first, then add the markup.
-
You'll need to call a Suitelet, that ought to do it
-
If you're saying you're trying to ADD a line to the customer payment sublist - you can't do that, no.