Robbie, the BFO parser will only work on valid XHTML but with some BFO peculiarities (self closing tags won't parse e.g. <br />), so run your XML through a validator. All attributes need quotes, etc. http://en.wikipedia.org/wiki/XHTML

Your .getValue doesn't reference a summary: This causes my seachresults[0].getValue('itemid') to be blank (or null) but your column does: columns[0] = new nlobjSearchColumn("itemid",null,"group"); And that is why you have null value (I think). Maybe try .getValue('itemid', null, 'group'). Also, I can't stop staring at your…

Exclusion type searches require a summary criteria. Here is a post where I ask how to query some cases that don't have a particular criteria. https://usergroup.netsuite.com/users/forum/platform-areas/reporting/34626-saved-search-for-case-system-notes-criteria-to-exclude-cases If you modify your search with a summary…

Ah, SWE. We are on it, too. For now. Interested to hear how you make out with this one.

Irrespective of any answers on here, will you make sure you keep the rest of us up on your findings? I know there are a bunch of us that would like some sort of automated testing. Maybe not as strict as how Salesforce does it but something would be nice.

I've seen that error when having an invalid nlapiSendEmail parameter. Do the prospect and customers have differing permissions in their roles? I assume so from the error. Do a role difference and see if there is some permission concerning communication, maybe? That's just the first thing that comes to mind.

You might want to open a ticket with NS on this one.

Try 'entity'. That's a valid internal id for nlapiLoadRecord and I think entity encompasses partners as well. You might be getting a different error than the one you are looking for. Try enclosing the script block in a try catch and log the error and message. That author error is throwing me. 

Yeah I just did a quick check using our barely customized customer and partner center roles. Lists>Track Messages is set on View for customer role and None for Partner. I would imagine that nlapiLogExecution is similar API'wise to nlapiSendEmail. Maybe.

Sam, have you tried just using the Outgoing from Support Rep field to start an email thread? You can use a default template there every time for both internal and customer facing emails. These are set up in Setup, Company, System Email Templates and can be formatted to your needs.

I wasn't referring to the Script Performance Monitor, there was another monitor that was specific to scheduled script queues. So I guess it was a queue monitor.

This monitor will particularly useful for those with multiple scheduled script queues as you can easily pick which queue is under (or over) utilized. It will make system performance tuning easier.

Yes, but this monitor was an expanded view of the queues and more akin to the Script Monitor bundle released a while back. With pretty graphs and metrics.

Actually, I heard back from NetSuite and the Script Queue Monitor is scheduled to be released in late June.

Totally would but it is so hard to actually search for something on that site.

Also, don't you want to stringify retObj instead of the result set (rs), or am I reading this wrong?

Turns out the it is in the receiving side. If I run a new request soon after the last then it is much quicker. This is not a vital process so we can live with the initial connection delay.

It's Dec 11 at my work. Coaxis. We should be putting out email blasts at some point. For some reason I had totally forgotten that function. Even though I just now remembered I have a scheduled script running to attach cases that were created in our legacy CRM to issues. Apparently I have reached the limit with my NS…

Eh, what's life without a little hacky risk ;)

You could hack it in view mode by creating an inline HTML field and using jQuery to set the CSS of the button text to red (Inspect element in view mode to get the id). jQuery is already loaded in NetSUite.

I am pretty sure when they changed this they made it so they are pumping out HTML, which means they have to escape HTML to do it properly, which means rich text field cannot be printed with this process. Or at least I haven't been able to figure out how to do it yet. I think they did it so they can escape & and such from…

I am happy to report back that version 3.5.8 has fixed the issue and I can now replicate the complete process in script that is done using the bundle buttons. They also unlocked the script files so debugging is possible now as well as so hacking a new process together is much easier now.

I have been waiting until I was done to make a post on how to do the whole thing, but I have been able to create a document from the transaction we are on, merge another document, add them both to an agreement and create a signer and a cc to send it all out. I can then sign it as my other user and send it back to EchoSign.…

Ok, so I heard back form Celigo and the mysterious parameter that needs to be sent is &senderid=empInternalID This makes sense seeing as how I need to call the Suitelet server side so user credentials are not kept. Learn something new everyday :)

I really think there is a restriction with workflows and suitelet other code. Does anyone know of any such restrictions? Here is the restriction. It's a 'duh' moment for me: Additionally, nlapiRequestURL calls from the server do not include the current user's session information. This means you can only use this API to…

What I am ending up doing is taking the advanced printing layout code and translating it to the server side workflow action script that I have for this process and just using nlapiXMLToPDF. It's a PITA but that's where I am at with it.

All right. This is super irritating. I can now get a custom field to go to more than one page using &lt;p page-break-inside="auto"&gt; but I can't get a rich text field to display in, you know, a rich format. Defect #263819 - Advanced Printing > Custom Transaction Body Field > Rich Text field > Getting the html code when…

Ok, I have opened up tickets with both NS and Adobe (escalated to Celigo). So far NS told me to get with echosign support because of the fact that the Suitelet is hiddden. But really, I think this is an issue with some sort of sandboxing of workflow action scripts. The funny thing is that I have replicated the code for…

I just have a rich text field that we use on proposals to send an SOW to our customers. If you use the regular PDF layouts you can't have custom field span multiple pages. You can use nlapiXMLToPDF and have the field span across pages, but if you try to even print out a rich text field using advanced printing it escapes…

I'm worndering if there is a restriction on workflow action scripts with calling suitelets? Anyone know?