Issue Number 252175 Type Defect Severity S1 - Issue Status Closed - As Designed Release Target Case 1688136 Defect 252175 - Web service Error (FedEx) Abstract: Fedex Real-Time Rate > Getting "Could not calculate cost for the selected Realtime rate. The rate for this service is not available for the specified source and…

Mine seems to be working again! Any explanation?? Was this a Fedex issue, or Netsuite?

Let's just say it is an HTML table built based on results of a search, looping through and adding rows and columns.

Great idea - dumb question: How can I save that xml to a file (nlobjfile)?

I am using: I get an error when I add the <pbr/> element: Notice (SuiteScript) Error Parsing XML: ignored nlapiXMLToPDF(xml);

I am not sure if this addresses the question at hand, or if I was not as clear as I should be. I cannot see the last 3 pages of some random reports. Are you suggesting that the TD was splitting across multiple pages? How do I create a page break using BFO in Netsuite?

Awesome Glad it worked!

Wow, interesting. We've accomplished similar tasks through the use of a custom entity field instead of the approach you've taken. Writing and saving searches per customer per user might be a bit taxing and overkill. Also, you are stuck with trying to figure out how to make filters available (good question, regardless) in…

SuiteFlow is never really my first choice - unless in a situation where I try it and hit a wall... then I just turn to User Event scripts always. This is a pretty straightforward action I am performing, though, so it might be possible. I need to create a copy of the current item record, change a few field values, and save.…

Can I ask what it is you are trying to do? I noticed some Printed Picking Ticket information in the code you posted. We have issues related to this field. . . it seems it is set and unset at random, and there is no good way to get at it to see what the status of the printing is at any point in time. We have multiple…

I am not sure about totalcostestimate, but apparently the "proper" way to set orderstatus is by loading the record and then setting the field and saving the record. Thus, instead of calling: nlapiSubmitField(recordType, recordId, 'orderstatus', 'A'); I replaced that with a function to set the status via the record: var…

Also, hate to beat the dead horse here, but there is definitely a lack of communucation/documentation in regards to this. Because, yes, I think I recall seeing a number of times that you only direct list editable fields are set using nlapiSubmitField, however, I don't know of any one place in the documentation that…

YES! Different field (orderStatus), but same issue. NETSUITE?!?! Any explanation? There must have been some release last night that triggered this... This can't be too good. We've got a script running on every single sales order that is returning these errors. Please help.

Thanks for the response, James. Here's what we would like to accomplish, and after looking at it further just now, I came up with a solution to the problem. We want the quantity to never be shown/told to the receivers, as they are sometimes lazy when it comes to counting and will just take whatever the invoice/packing…

Thanks, Olivier!

Thanks, works! I recall reading somewhere in the Help documentation that it is recommended to look for (searchresults && searchresults != null).... or maybe it was only (!searchresults) for the opposite case?

Will this work if you set the recipient as an internal id (say, of an employee - in your example, that would be -5) and in order to email the customer you simply CC them. So, any replies would be captured in NS, or no? For example: nlapiSendEmail( -5, -5, 'subject', 'email body' , 'customer@netsuite.com', null,records );…

Olivier, A JE? Can you explain?

Olivier, Can you clarify your edit? What are the submitted fields? Only that one that was edited? Or, all fields in the view? Thanks!

Ok, Olivier, I see. So, can you elaborate on the pain involved in working with xedit? Basically, I have a few custom fields that drive the item record fields. Based on their values, I update various other / multiple fields on the item record. Currently, I take all fields in a user event script and apply my changes to the…

JMU, Thanks for the reply. I agree 100% in theory with what you are saying, but let me clarify: We have a totally separate service department that deals with tickets and invoices for service-related labor, and then we have a self contained supplies branch that aren't totally different entities but were treated as such for…

After opening a case with Netsuite and troubleshooting my code (which was copied from the Help Topic on the Pricing Sublist), they responded: Hello Elie, Here is the code from the reference I sent you. var record = nlapiCreateRecord('inventoryitem'); record.setFieldValue('itemid', '124'); record.setFieldValue('department',…

That is a great idea, and I have already done that! It hit me late yesterday; I guess great minds think alike. . . ;) I created a custom field (Document Number) and unchecked store value - set the formula to a CASE statement that looks up the division and adds the necessary suffix. This way, I can pull up all existing…

Nice! How do we get them into our account before 2012.1 - - I can't wait the two weeks!! Thanks for the heads-up though, Evan!

Sure. We have a variation of the script running on a massive number of lines, as we are moving tons of SKUs between warehouses. Basically, you will need to pull up each line of the PO and add them line by line to the transfer order.

I have an open case with Netsuite regarding this, but it is related to this topic, so someone might have an idea for us: We have an order that was somehow set to Pending Approval after it was fully billed and fulfilled. So, it says: "Pending Approval" When we try to approve the order, or cancel or anything - we get the…

Has this ever been resolved? I feel as if I still cannot accomplish certain validation on the line level in the Recalc function? Can you access nlapiGetCurrentLineItemValue in Recalc?

Same issue here.

Solved! I contacted support regarding this issue. The location used by default is the location associated with the Employee record, not the preferred location on the item. The only time the preferred location for the item is used is when the line is added individually, but not when it is added through the Add Multiple…

Thanks, we actually opted with a saved search to alert the appropriate parties when necessary. . . But if things were to get out of hand then that would be the approach. Another idea was to have a separate listing, being a subset of the regular terms avaialable. We would then have that field populated with only the terms…