starlingMark Green Ribbon

I totally agree - the transition was not easy for me either. With that said, some of the new functionality available in 2 is worth the price of admission. You also come to prefer the explicit setting of parameters on functions. How many times have you had to lookup the proper sequence of parameters for nlapiSendEmail :D

karenn Agreed - not being able to set field group widths can be a pit of a pain if you are trying to make something "pixel perfect". But it sounds like this got you close enough!

dev0001 You may find https://system.na3.netsuite.com/app/...407991781.html helpful as it details the beforeLoad event in SS2. Indeed you will need to use scriptContext.newRecord. To get the type use scriptContext.newRecord.type. For the ID use scriptContext.newRecord.id. As an aside, there is no need to load the record…

Hey garysb, The {countdetail} field is a summary according to the records browser - that makes this field a subrecord. You'll need to load the subrecord, populate the inventory detail sublist (serial/lot number, quantity, bin), commit the line on the subrecord, and finally save the inventory count. Hope that helps.

You could probably add the field with a User Event. Downside is that you cannot choose where the column is displayed - it will be last.

vkwanengage, You should not have to declare the log module explicitly - it is always available. I wonder if you remove the declaration at the beginning of your function if the log function will work again. I know it sounds silly, but it may be worth a try.

The only option that comes to my mind is to using scripting. Add a custom "Category" field on the sublist, populate it based on the options that you would like it restricted to, and then have that field toggle the real field (which you would hide).

Have you considered having the field not store the value but populate it with a saved search? Details can be found in the NS help file here: https://system.na3.netsuite.com/app/help/helpcenter.nl?fid=section_N2830711.html

Unfortunately no - you will have to manually add the values you want.

Hi ssilveri777, I would highly recommend that you do not manipulate the DOM. This is unreliable in the long term, as NS can change how they structure UI elements at any time and blow up your code. Which field, exactly, are you trying to change the available options for? Perhaps a screenshot would help my slow brain.

Hi jmacdonald, I've come across this request before. A couple of other thoughts for you: 1.) Web services would probably handle such a request more robustly. 2.) Is there any way to grab the external URL of the file and instead ask the other side to perform a GET? 3.) Middleware - something like a small node app that can…

Hi pcutler, Per the help on What Are User Event Scripts?: User event scripts cannot be executed by other user event scripts or by workflows with a Context of User Event Script. This leads me to believe that workflows should trigger user event scripts, as long as the workflow is not running on a user-event-style trigger.…

Have you tried making the field text/long text and just setting the value to the anchor tag?

I've actually hit my head on this again, but found another solution. For those that come after me, here's an example. If I call currentRecord.getValue({ fieldId: myField }) under the following circumstances, here is what happens: myField = 'custrecord_myfield'worksmyField = 'custrecord_' + 'myfield'worksfieldName =…

You found my weakness - it is a select field.

Thanks pcutler. This would almost work here, but not quite. I was hoping to dynamically populate this field by script, which I can't do with a true custom field.

Thought I had this figured out by using form.insertField, but that did not work.

What event type are you firing your UE on? I've seen issues where a system-created record did not fire before load triggers properly.

Yup, saving the search will always present a title. Saving the search, in this particular use case, is not a good option though.

Very helpful - thank you!

Yup - the ${modules}, ${modulesJsDoc} and ${moduleParameters} all populate properly. Just not ${date} and ${author}. I've also tried removing these two variables from the commented section at the top, but this does not change the behaviour.

Eric, I have been tinkering with this. These are excellent. One question/issue - I can't seem to get the variables to populate. For instance, ${year} and ${author} don't populate with the proper values. They just show up as text. Any thoughts?

Just to add a bit more strangeness to the whole affair - if I put ${date} and ${author} in the ss_2_0_header file, it works properly.

Frédéric, Thanks very much for the reply - I'll give that a shot here later today. I have not filed a defect. I don't have the patience.

I am creating the new file as you describe. I typically have a folder already setup and will click on New -> SuiteScript File. Then I will select my type from the dialog menu. The proper template is sourced, but the ${date} and ${author} don't populate - they just show up as text.

david.smith Thanks for the suggestion. This returns a value of -1 for the line count. However, isn't this snippet trying to get the number of lines on the inventoryassinment sublist on the assembly build record instead of the inventory detail subrecord?

ssilveri77 The getSublistSubrecord method is only for getting a subrecord from a sublist field. In this instance I need the one from the body field. In either case, I can retrieve the subrecord - the real issue is when I call getLineCount.

Bumping my own thread back up to the top a year later. I was now able to successfully save a Work Order (with inventory detail) and create a linked Assembly Build (with inventory detail). However, if I transform a one-line SO (with inventory detail) into an Item Fulfillment and try to save it, I get the same error as…

Darren to the rescue! This is indeed in a Suitelet. No equivalent in SS1 at this point - that is my task now. Off to re-write some code.

For the record, when the script is re-written in SS1 it works.