So, the answer to this was that NS didn't like reading that parameter as a number. I changed it to: so_id.toString() and it worked just fine. That is very frustrating, and I didn't see it anywhere in the documentation.

Also got this confusing response from support (after they helped me determine the 'fix'): Support Case #: 2618341. Hi Alex, Thank you for taking my call. As discussed, the transactionID parameter under relatedRecords options needs to be string for it to work. We have tested this on your end and it was successful. With…

Thanks for the response Olivier Gagnon NC - glad to see I'm not the only stumped one. But, also interesting to note that you have examples of it indeed working. I opened a case with NS last week, and there's been some back and forth so hopefully I'm close to a resolution on this one, figured I'd reach out here anyway.…

Do you get an error in your browser console, or does it just fail silently? Can you post your entire script contents for us to view?

Sigh...of course it is.

I'm sure you've thought of this already if you are to the point where you are considering scripting, but can you just use a saved search with a date field as the available filter?

david.smith - I thought the "daysagoxxx" were deprecated, are there similar ones you'd recommend using in their place?

If you run a saved item search, you can make one of your criteria filters "Inventory Location" and set it to location B (you can also set it up as an Available Filter that will let you choose the location dynamically at run-time). Then, in your results tab, add the "Location Available" column. You should then only see…

Can you post your Suitelet code? My guess is the error is coming from there?

I would check first to confirm that both 'start' and 'end' are in fact numeric type. Just a hunch.

girieshg - My responses were based on 2.0's general lack of ready-ness, not from any REST-based perspective. It's unclear how far in the future 1.0 would be deprecated, but considering the number of scripts that clients (including third-party NetSuite Partners) already have written, my guess is that it will likely remain…

I would not. I've been playing around with it a lot lately and it still feels buggy to me. In fact, I literally JUST got off the phone with support who admitted to a bug/defect that I found with logging a boolean false value. So while it seems ready-ish and worth playing with for non-essential projects, I wouldn't take big…

Glad to hear it, JacksonP

I was playing around with this today. Do you want to share your code, maybe we can figure it out?

Yeah that's what I was afraid of; the call to .confirm() returns a promise object, hence why you chain with .then(). Since those operations are asynchronous, the function will complete (returning whatever you tell it to) before your success function actually fires. I'm not sure how best to get around this, but perhaps you…

I think your main function doesn't return anything so that may be the problem? You may need to reference a global variable and return that from your function, otherwise it just ends with your call to dialog.confirm, etc - I'm not sure what the actual return value of that is.

FWIW, here is my code, and it works for me (deployed to Sales Order, client script): /** * @NApiVersion 2.x * @NScriptType ClientScript * @NModuleScope SameAccount */ define(['N/ui/message', 'N/ui/dialog'], /** * @param {message} message */ function(message, dialog) { /** * Function to be executed after page is…

Good stuff, thanks everybody!

Olivier - how could I forget?! That is actually on my blog roll also, somehow I missed it when looking at my list for the post. Cheers :)

Hey sson - glad you like the group idea. I highly recommend the NS Professionals Slack Group as well: http://netsuiteprofessionals.com/wp-login.php?action=slack-invitation

Great idea. I've joined, happy for another place to communicate directly with NS Professionals.

Right on carl.billings - that is our goal. to increase the number of approachable, friendly places where people can go for useful tips.

FWIW Slack is working nicely for me as well (I already used it) and I can't see the 10,000 cap being an issue.

Hey there - yes, advanced PDF template for saved searches cannot handle summary columns at the moment. If you can't figure out a way to make your search work without summary columns, then you'll need to approach the problem with another tool, likely with scripting. Also, depending on your advanced PDF chops, you can have…

jokell - I don't use the Advanced PDF for pick tickets because it doesn't work for kits - no bin numbers show for components. So, I haven't run into this. I would imagine, though, that you should be able to use "kitmemberof" or a similar type of field to differentiate - however given the Advanced PDF track record, I won't…

jokell yeah, I just applied everything to the pick ticket instead of the packing slip. Your main source transaction type will be sales order, not item fulfillment.

Thanks dmashburn3 - drinking a pint right now as I type, while at work. It helps. david.smith - I am plenty comfortable with scripting myself, but I didn't see a (non-custom-record-based) solution for this one. If you have tricks you're willing to share, I'm open to hearing them. Generally if I can't figure it out, then a…

I feel for you jokell - I was in this exact spot a few months ago. Super frustrating. The bottom line after all my research, discussions with other admins/devs, and multiple NS support cases, is that while there is no native bin number output on pick tickets when using Advanced PDF Forms (I know, it's ridiculous), there IS…

Mine is basically as follows: if (type == 'create' || type == 'edit') { var count = nlapiGetLineItemCount('item'); for (var i = 1; i <= count; i++) { var bins = ""; nlapiSelectLineItem('item', i); var item = nlapiGetCurrentLineItemValue('item', 'item'); var itemType = nlapiGetCurrentLineItemValue('item', 'itemtype');…

FWIW, my response from Support: [TABLE="align: center, border: 0, cellpadding: 0, cellspacing: 0"] [TR] [TD="colspan: 2"] [COLOR=#000000][FONT=Verdana]Support Case #: 2506699.[/FONT][/COLOR] Hi Alex, How are you doing? I have further information on our case. For the Advanced template, I have tested all other ways like…