in your suitelet, if you create the list using the 'editor' type, I think that's close to what you want. This gives you input fields above the list that apply to the currently selected row when you click "Add/Edit", and also provides an "Insert" and a "Remove" button.

I've been able to get THAT behavior by building the sublist in a Suitelet form, from a search. I make the sublist of the 'editor' type but there might be another type that does what you want. The 'editor' type lets you inline-edit in a way, but nothing in a suitelet lets you re-order items by dragging. It does however let…

The list type is one of the parameters in the suitescript function call that creates the SubList object. I haven't tried it on Lists, just SubLists.

It's probably for security reasons, but I'm having a problem with my project too and the reason is that Roles are a record type that is purposely set to not be available to SuiteScript. I need to get a list of all the roles for my project though, so I will see if I can load a Saved Search into the Script. No need for…

Didn't work for me... Did it work for you?

Has anyone got this to work? I can't find documentation on this.

I always prototype from the console if I can. If I get an error then I go to the trouble of doing it in suiteScript and logging

That's right - the same suitelet can "call itself" and handle both GETs and POSTs. I usually just test for parameters in the request that can only mean it wants a PDF. If they're absent, it responds with the form. If present, it responds with the PDF generation.

look up nlapiYieldScript and nlapiSetRecoveryPoint

Caching bug? Happens in NS a lot.

Just checking - do you use the Custom Record Type's scriptid or its internalid? It may be that either one will work, I don't know. I always use the scriptid in the nlapiCreateRecord call, and that works for me. So you might have a Custom Record Type with scriptid of customrecord511 and an internalid of 670

If your account is special :) then you can have 5 queues for scheduled scripts, and assign which one to use in the deployments

one caveat: You have to pass the script id and deploy=1 in AJAX requests and possibly in postbacks, along with all your other request params

You know what I do? I use the Suitelet like a Hypertext preprocessor and have it generate everything client-side : HTML, JavaScript, CSS, etc. according to what I need. You can use the client-side HTML forms to post back to the Suitelet, and then the server-side Suitescript in the Suitelet can analyze the Request object.…

using this approach I can do pretty much whatever I want. It gets a little HTTPCeptionish when I started having the page make AJAX calls to itself, including a flag in the HTTP get params to tell it which server-side behavior I wanted - i.e., which action I wanted to execute... again for design sanity you might separate…

I don't know if this will help, but it might be worth a try: When working with groups and package or kit items, I find that they almost always have to source in their component items. This only happens if the transaction record is created or loaded in dynamic mode. If you're working with a sublist in dynamic mode, it is…

When I look at the record object after doing a line edit client-side, then it overwrites that line item with a bunch of undefined fields, EXCEPT the one designated by the setLineItemValue() call. Maybe you have to explicitly set ALL the fields that you want to exist on that line item, even if they didn't change from their…

I would recommend that you use a User Event script to clean up the corrupted fields on the beforeSubmit event - then you won't have to mass update more than once, because all future instances of the field being populated will have the corrupted strings removed or fixed.

Looks like this has been added to NetSuite's API

Use the internal ID of an employee record, not the email address.

Were you using email.send (equivalent to nlapiSendEmail with notifyOnBounce set to true) or email.sendBulk (equivalent to nlapiSendEmail with notifyOnBounce set to false)? NetSuite sends emails on its own sweet time when and if it feels like it, unless you use nlapiSendEmail with notifyOnBounce set to true, or use…

No, the button just would need to send the script the parent ID somehow. I have done this by using Formula defaults on an Inline HTML field, where the parameter parts of the URL to the suitelet used curly brace field references.

Of course also a button could just be on a client script function that does nlapiGetFieldValue() on the parent ID and activates the rest of your process using that value.

Maybe we're both missing some little configuration setting?

Oh how did you fix it? Or did they fix it for you?

I wish I could help but I'm new to PDF layouts. If all else fails though, you could go to a large amount of trouble and re-write the whole thing as a suitelet that uses BFO-syntax nlapiXMLToPDF(). But that's a project by itself. We had to do that for one of our printouts because we couldn't get the regular print forms to…

That's a good thing to check on - sometimes the actual amount is not rounded, it's only shown rounded, in things like that. But if you're sure the field being used for calculations, etc. is being rounded then... well, does anyone know how to change that?

I'm still a beginner at some NetSuite record and field types.

I heard NetSuite will be overhauling their UI this year - maybe the currency and decimal fields will get an upgrade too if we're lucky?

I wish I knew more about those fields and records, but it looks like one way to get this to work would be to create a custom field that is not Currency type, to appear on the line items, and which simply uses a formula {name of field with the numbers you want in it}. Then it wouldn't pre-round your numbers before…