3942203 Newbie

I wrote the thing specifically with the NetSuite WSDL in mind. So far so good in the simple apps I've been testing it with :)

Jeff, In the NetSuite Help Center, check out SuiteFlex > SuiteTalk > Platform Guide > Getting Started > Setting Your Web Services Preferences. In there pay attention to Use Conditional Defaults on Add and Use Conditional Defaults on Update. When these are on the item descriptions should fill in properly.

Yes this is more complex than I first realized. It can be done, but the solution I've thought of would require you to script your proposals and validate whether it matched this criteria each time it was saved. You would then store the result in a checkbox field and search your proposals based on the criteria of the…

In your saved search check the "Use Expressions" box. Some new columns will appear in the Criteria tab. The one you're looking for is And/Or. Change the value to Or on the first criteria row and this should get you what you're looking for. :)

I'm not really sure what your goal here is to be quite honest, but let me explore something for a bit. If you were to change your thought process to be more along the lines of how many orders per particular stage are late, you could do something like this: [LIST] [*]Store a date for each order of the completion date of…

We are being haunted by this same problem. We were able to get Issue #110570 filed 31 days ago on it but nothing really seems to have been accomplished as of yet.

If you were to script an afterSubmit deployment that took advantage of the nlapiSendEmail function you may be able to get that to work. I have not tested this at all yet, but conceptually it could work. Our company will be looking to incorporate similar functionality in the near future. If you make any progress on this or…

Yea, it seems ridiculous to even have a dropdown per line when they all are required to have the same value before you save. This would streamline our processes quite a bit if we could fulfill from multiple locations on the same item fulfillment record.

Is there an integration option with UPS WorldShip? If feasible, has anyone implemented an efficient and reliable export/import process? It would be nice to open a NetSuite Customer record and directly trigger UPS WorldShip to create a shipping label (auto populate the customer name and address). Are there other options to…

Scheduled saved search emails. I'm seeing the same behavior.

Yea the id being passed into nlapiLookupField was null, which caused the cryptic error. It was bad on me for not checking the value, but the error message isn't quite helpful.

I'm getting the same error in a script that isn't even using nlapiSearchRecord = Case 855756 var serviceId = nlapiGetNewRecord().getId(); var author = 33; var salesRep = nlapiGetFieldValue('custrecord53'); var subject = "New RA (" + nlapiGetFieldValue('name') + ") Created for " + nlapiLookupField('customer',…

Lots of cheers coming from me on this as well. A big thank you!

Thanks for the explanation Michelle, I'm trying to get my hands on whatever version of the Release Notes are available at this moment. If my neighbor used NetSuite and was using 2009.1 I would ask him to print his Release Notes for me. It's that kind of thing, I just need access to the document which isn't secret or…

We just got the general overview sneak peak via email. Still waiting on more detailed docs however.

Yea this helps. For now I just created one folder with my project name and moved all of my files into it. Not "ideal" I suppose but quite manageable. And by the way, thanks for the plugin NetSuite. Works well.

John O., What you observed is by design. This will minimize the chances of accidental file collisions. I can see why you don't like it because it forces you to re-organize your existing scripts, but we believe long term this works for the better. Of course, having said that, we welcome user feedback and if the majority of…

I downloaded and installed a fresh copy of Eclipse today to try this out. The Aptana and SuiteScript plugins installed successfully. Entering login information worked just fine. Adding a project with all of my existing js files worked well. Updating and uploading a new file, however, didn't work as expected. I keep all of…

I just wanted to add my vote for a new version number for every release - even maintenance ones.

Mini, Thank you very much for you followup. It really helps us plan out our upgrade. John

Can't agree with you more. Although the beta account setup isn't perfect, I'm confident it has made my life a lot easier for when our live account does get upgraded.

If you have access to a v2007.0 account (beta or not) look for SuiteScript information within the help. More specifically: 1) Click on help, a window will open up 2) On the left, expand the "Scripting and Web Services" folder 3) There is a SuiteScript folder in there with all sorts of good information I recommend reading…

It's pretty common practice to automatically update a single html page every so often (once a minute, whatever) so that each time someone visits the page it doesn't have to requery the databases causing slowdowns and opening up DoS attacks.

Excellent. Glad to hear it's working Elie :)

I'd likely need to see what's going on in action at this point :( Have you opened a case with support?

Is it possible that you're actually dealing with a different field? Try deploying a client script in Testing mode so this only alerts you: function fieldChanged(type, name) { alert("Field changed: " + type + ", " + name); } Then change the value of the field you're to disable and make sure the field's name is what you're…

The last thing I can think of is if you had more than one script deployed to these record types that shared a function name. As the js files get loaded one defined function would clobber the other. Does this sound possible?

Are you using the function in a client script? It is only available in that context. If you are in a User Event or Suitelet context then get the field object using getField() or as the return value from nlobjSublist.addField() and call nlobjField.setDisplayType('disabled')

Are your deployments in Released mode and deployed to the right roles? I know I'm grasping at straws here...

FYI I've had some success setting the button to disabled instead of removing it at times.