My Stuff
On Friday, October 10, 2025, at 8:00 PM Pacific Time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
Share Your SuiteWorld Experience & Earn a Special Badge!
Comments
-
firstname and lastname are only populated for Customers where is Individual = true. Otherwise companyname should hold the value.
-
I believe you. We're still having the problem though... I will work with Joel on the Case to see if we can figure this one out.
-
It used to work. Doesn't anymore, anything less than a cache flush doesn't work.
-
You must set the Price Level to Custom, not blank, to be able to specify a rate. This is not new from 2010.2.
-
You've got a pretty fundamental problem there. Your for() loops through the items but your XML string is built AFTER the for(). So of course it will only take the last item. You should probably concatenate your string within the for().
-
No, I opened a Case and got 1 reply saying they couldn't reproduce in 2010.2 accounts and asking for accounts where we encountered this problem, which I provided. Didn't hear anything afterwards.
-
Ok. Case# 1229142
-
As I said, you need to concatenate your strong within your for(). The below may work. function GeneratePdfXml(request, response){ if (request.getMethod() == 'GET') { var recid = request.getParameter('recid'); var record = nlapiLoadRecord('itemfulfillment', recid); //got the nlobjRecord object var entity =…
-
You'll need to add your logic on the recalc event. This event includes ANY change to the sublist. You'll then have to iterate through all line items annd figure out if that line needs processing or not. Basically, you can't trigger a per-line behaviour, You need to process the entire sublist every time.
-
Yes it will work.
-
It is indeed possible to change forms on Transactions. It is not on Customers.
-
Could you clarify if you are using suitescript or the workflow module? You mention both. If you're talking about suitescript, you simply need to ensure you populate the paramater of the API to attach emails to records.
-
You've got a typo. nlapiSubmitRecord(recoord); should be nlapiSubmitRecord(record);
-
Wow, I just tested in a demo and you're right, nothing happens. "As designed", huh? Oh well...
-
What tax settings are you using? Do you have multiple Nexus? Do you SOs have per-line dropdowns where you can select a tax code, or do you have a 'taxable?' checkbox?
-
Hmm, good one. All this is theoretical since I've never done this, but when you print you get a file object, right. And you can access the content of a file object (.getBody() IIRC). So perhaps you can get the content of all of them and create a new file and set the combined content as it's payload.
-
An Unexpected error is odd, so it could be some sort of actual NS problem, but common probblems with using nlapiLoadRecord in client side are a) does the record actually exist and b) do you have permissions to access that record?
-
IT starts all over again. It is your responsibility to code in mechanisms to pick up where you left off (e.g. tick in a box on records and add a filter "box not ticked")
-
Yeah, I pointed this out to Support a while back. They said it was as designed. I encourage you to also submit a case anyway.
-
Wouldn't you be better off handling that use case with Permissions?
-
//Bring in the saved search results var arrSearchResults = new Array(); arrSearchResults = nlapiSearchRecord('salesorder','customsearch19',null,null); //Fulfill the Orders for (var i=0; i<arrSearchResults.length; i++ ) { try{ var id = arrSearchResults[i].getId(); var fulfillRecord = nlapiTransformRecord('salesorder',…
-
Hmm, here are some starting points - Filter based on Type (SOs, POs) Mainline = true Columns: formula (currency) SUM - decode({type},'Sales Order',{amount},-{amount}) reffid - GROUP That decode in there is basically saying if this line is a SO, consider amount to be postive, otherwise (if it's a PO) consider it negative,…
-
record.setLineItemValue('item', 'class', 'j', 'setclass') you need to give the internal id of the class you want to update to. So this should be something like record.setLineItemValue('item', 'class', 'j', 1) replace 1 by the actual id of the class
-
If I understand correctly, you mean that each of your lines on the SO you're working on has a corresponding line in the resultset? Which, I further guess, is because your script returns the current SO with an added join on item for class. Well, you could have added a custom do not store value field to your SOs and opened…
-
nlapiRedirectURL() only works on true submits. So if you call in on sume custom button, it won't get you anywhere. In this case, you can do plain javascript window.location() or window.open(), though that may show the annoying "are you sure you want to leave this page" popup. The best thing might be to add a true Submit…
-
You must create the field with scripting in beforeLoad. Then you can use the APIs to add/subtract values dynamically. See the documentation for form.getSubList().addField() and nlapiInsertLineItemOption() EDIT: Forgot to say, you might be able to get this to work simply by using the Soucring filters on the custom field…
-
Yes you can. nlapiRequestURL()
-
I believe this is Defect #183656
-
Web Orders still not triggering any scripts for us. I didn't see the Defect for that get resolved either.
-
Nope, that's pretty much it. It's not exactly simple, but that's how you need to do it. Create your field with scripting, control its values, and add another script to synch the value of he script-created field with an actual custom field (cause the scripted field doesn't save anywhere).