Without running this on my end, I'd guess that one issue is that you are trying to divide by a string/text field instead of a number (TO_CHAR returns text). If you remove the divisor and run it, do you still get an error?

Sounds like you want to use Grouped results - on the Summary Type column in the results tab, you may want Maximum on your Date result, and Group on your Email result. Just a stab at it, if you could post a screenshot of your saved search I may be able to help more.

Also wondering if this is available now? Seems to be strange that this wouldn't be exposed after 7 years but yet, here we sit...

I haven't worked much with foreign currencies, sorry @j,j

I believe this is due to the fact that you're not storing the value - fields without "Store Value" checked cannot be used in saved searches.

I see, my apologies - so I think the problem is likely that you're trying to access an item field within a transaction column field formula. The scope is going to be fields available to you on the transaction, so to get to item fields you will need to join. Something like {item.custitem106} is probably what you need.

On the setup of the Transaction Item Options in NetSuite, is the box checked for the options to be applied to Purchase transaction? In the list, there would be a "Y" in the "Purchase" column.

Ah yeah correct, as carl.billings said, workflows limit you to only using / referencing main/body-level fields. For transaction line / column fields, you likely need to leverage a script.

Hi - for that I believe that you want to check the box on the custom record definition page marked: "Allow Child Record Editing". I tested this on one of my custom records and it seems to be what you're referring to.

Yes, I would use a workflow. Should be fairly easy to set up, if you've done basic workflows before.

I see...unfortunately I have never done this in a template, however I wonder if you can use the method described here: https://netsuite.custhelp.com/app/answers/detail/a_id/13622/. It may look something like this: <%=REGEXP_REPLACE(${record.???}, '[-%]', '')%> No idea if that will work, but may be worth a shot.

I would use REGEXP_REPLACE and leverage regular expressions: REGEXP_REPLACE('test-te%st-', '[-%]', '') // returns "testtest" You can also do nested REPLACE statements as such: REPLACE(REPLACE('test-te%st-', '%', ''), '-', '')

What about printing them from this page? /app/accounting/print/printbarcodes.nl

They announced that this is something you can control in 2017.1 release notes, so it's coming soon mushrush.

Almost 10 years later and this is still unavailable to filter by for sourcing a custom field based on Partner records. Any chance anyone has successfully done this another way without the need to maintain two separate lists (ugh)?

Bednar I appreciate the response. Unfortunately part of the problem is that I need to process an item record 3 times - and each time, the item record has the same internal id - so if the script has to yield after processing the item once or twice, when it picks back up it will skip the ones it didn't process. BUT, perhaps…

Thanks all - khultquist I'm not actually looping inside of the script; my saved search that drives the creation of custom records within the scheduled script simple groups by Item and Inventory Location. Here's the script: function debug(s) { nlapiLogExecution('DEBUG', 'debug', s); } /** * @param {String} type Context…

getLineItemText should get you what you are looking for

Cheers and welcome to NetSuite! Your JS experience will come quite in handy, as you've likely already realized.

For field names at the column / line level, I recommend using the SuiteScript Records Browser: https://system.netsuite.com/help/helpcenter/en_US/srbrowser/Browser2016_1/script/record/salesorder.html Sounds like what I would do if I were you is import the custom file data as a custom record into NetSuite and then script…

qnguyen - I haven't used it, but I stumbled across this in a past life: http://www.walkme.com/products/walkme-for-netsuite/ Sounds like it may be relevant / a potential solution for you.

Just remembered also another option for finding field IDs is adding "&xml=T" to the end of your sales order URL - this will show you the XML data for the SO and should break down all field IDs.

Does your search contain grouped results? I've found that when that's the case, result.getId() doesn't return anything, so I have to explicitly include the grouped internal ID field in the results of the search. Not sure about getRecordType(), but it's possible that it is suffering the same fate - IF you are grouping.

Hi dorath, Can you post your code here so that we can evaluate and hopefully get you an answer?

Here is the (simplified) code I used to do it. It's a scheduled script, running every 15 minutes: function KW_autoBillSalesOrders(type) { var search = nlapiLoadSearch('salesorder','customsearch_kw_salespendingbilling'); // search that contains all orders you want to have billed var results = search.runSearch();…

Yep, I've accomplished this with a script. Might be possible with workflows, but a script would be simpler, I think.

I believe he is suggesting for you to comment out the 3rd line inside of your for loop.

Glad you figured it out, jmessersmith - I'll admit I have had to do an nlapiLoadRecord call like that within afterSubmit functions before, so I'm not too surprised. Just sucks that it's required here. I think you're right in your hunch about the CC info as well, though I haven't tested and so cannot be certain. Cheers!

Hmm, I'm not certain then (sorry). Two thoughts to try: - maybe, crazily, nlapiGetOldRecord would work? - I notice you referred to 'orderstatus' once, and 'status' elsewhere - any chance 'orderstatus' would be available after submit?

I think it may be related to what this line in the JSDoc is referencing: * @returns {String} The string value of a field on the <strong>current</strong> record, or returns null if the field does not exist on the record or the field is restricted. As such, the "current" record in that context is null. You may want to access…