Well I have an idea, but I'm not sure if it will work. You need the saved search list view to show a column containing links to associated sales orders. If the sourced field isn't working, you could try making a normal list/record field of Sales Order type, Customize the Form so that users cannot edit it, and then use an…

I don't understand much of what you want to do, but if you want to get the Saved Search to result in showing both the different records with same name 'B', then the Search criteria would need to be based on the relationship between SO's name and custom records like B and C, etc. that are related to it. You can filter the…

Don't indicate an Event type at all in the deployment - let it be whatever it wants. This has to be done in a Client script, or in a beforeLoad script that generates javascript into the page, OR in a custom field on the record view, rendered as Inline HTML (but that's tricky and you have to be careful with your single and…

Oh wait - looks like Brett got it. That bit of code near the top lets you filter the event type as Create OR edit (both :) )

Perhaps, but our company has hundreds of thousands of records and I think it would only take a couple seconds even then. You might look into SuiteFlow workflows too. I'm not sure if they can easily do what you need but they are able to react to things like the user changing a field BEFORE the record submits. For what…

Faster: User Event on submit record, nlapiSearchRecord on that record type, Filter on exact text match (force both operands to lowercase and trim the ends just in case). If the number of results is more than 0, then that email address already exists. Because you are filtering on that exact match, the search will be very…

Did you put in the comment tags for custom entity fields? <!-- <nlcustentity_myfield> --> I'm not sure if that is what you're supposed to do, since I've only built one or two HTML Online Forms so far, but when fields weren't showing up, it was first because I had left those tags out, and secondly because I didn't include…

I hope someone can help you - I have only made 2 of those forms so I don't know very much.

You're welcome. Glad I could help.

First make sure your User Event script is Deployed without any Event restrictions such as 'create' or 'edit', which will cause it only to execute on those types of User Events. Next, look in your code and make sure that the block of code you want to execute is not contained in an if/then block where the condition is that…

Maybe use javascript. You can even load jQuery into HTML Online Forms. That's how we show/hide different "pages" of a form when the user clicks next/previous buttons. It's all javascripted.

smurphy that sounds like a good idea. Either that or client-side script

Can you give a little more detail on what you are trying to do and what happens instead? If you show how you're attempting to access the fields and from what record type, that will be very helpful. If I'm not mistaken, the data structure might be different for custom fields in custom record types than it is for custom…

Not sure. I'm assuming you mean something similar to the confirm() javascript function. If there's no built-in way, you could override the event handler(s) for the submit button or roll your own using client side script. Hopefully there's a built-in way, because the other way I suggested requires a disproportionate amount…

It's not hard. Just write a SuiteScript to do it. The task of splitting the copying of info between two record types or even two records of the same type calls for some SuiteScript, because that's the only automatable way that also gives you that kind of control. nlapiCreateRecord, nlapiSubmitRecord, nlapiGetFieldValue and…

Often, a client side SuiteScript will die without explanation and without showing up in the Execution Logs. However, you can find nlapiExecutionLog calls in the HTTP transactions if you have your browser Console open at the time. Try opening one of those and check the Post or Parameters within for nlapiLogExecution stuff.…

So then how do you get the manual sorting? There's no way to sort them manually in the sublist when viewing the parent record.

You could create a second field which is the formula field, and have the formula truncate the text from the first field, and just always refer to the second one. There might be a more elegant way though.

I need to be able to do something similar in a Suitelet. The Saved Search interface has this kind of drag-to-reorder feature on its sublists for Criteria and Results - How do we get that behavior on our Suitelet forms?

Probably right, sklett. I don't know much yet, but it seems like formulas act on one record at a time BUT can use aggregation functions in their expressions (like MAX, SUM, COUNT, etc.), so.... maybe? Then again that's a formula field in a search. I haven't tried it on a record before.

Ah, nope. Tried the default field value (formula) approach, and all the SQL aggregation functions are missing from the list. Sounds like User Event populating a field is the way to go.

Make sure all the fields you need to work with are accessible by the script, and not just by you through the NetSuite UI. Sometimes nothing's wrong with your code, and it's just a Search or list view missing some result columns or some fields not having permissions or Public set the way you need. So it's worth checking…

I was hoping I could get it working because it's a lot of work to implement my own sequence ordering number system (extra field and lots of scripting!)

Same here, only mine is happening without any code, in an SSP Application. [Error processing dynamic tag getCartURL() : Unknown method getCartURL()] I don't make that call anywhere, but it shows up anyway.

You might have to indicate start position and occurrence params on REGEXP_SUBSTR function call

Anybody figure this out yet?

Sometimes empty fields come in as a blank/empty string instead of as a null. You could test for that, too.

I'm stumped, but then I didn't know it was possible to use SUM/MAX in a saved search formula

slarsen - those filters on the deployment Status screen always catch me off guard, and half the time are NOT what I had them set to before I re-entered the page, so yeah, definitely check there before re-configuring anything.

nlapiSetCurrentLineItemValue will trigger a fieldChanged event. I dont know anything about Sales Order records, but I can tell you a trick I use to avoid the infinite loop: create a global var. Name it suppressFieldChanged or something like that. var suppressFieldChanged = false; within the fieldChanged event handler,…